Uploaded image for project: 'Compass '
  1. Compass
  2. COMPASS-8556

FY2025Q4 3rd Party Library Upgrades - Developer Tools

XMLWordPrintableJSON

    • Type: Icon: Epic Epic
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 1.45.1
    • Affects Version/s: None
    • Component/s: None
    • Developer Tools
    • Not Needed
    • Hide

      1. How does this change affect a user?
      2. Why would a user want to use this?
      3. What command or series of steps does the user follow to make this change?
      4. What is the expected result?
      5. Can this affect database performance? How?
      6. Is there a minimum or maximum setting for this change (if this is a configurable parameter)?
      7. How could the user break something by using this incorrectly?
      8. Is there an ideal setting or way of using this feature?
      9. Does this feature affect any other settings or parts of the product?
      10. Does this feature affect upgrade / downgrade compatibility?
      11. Does this replace some other thing that we should downplay / retire / remove?
      12. When are docs required? Iteratively throughout the project, at project close/feature release, or whenever the Docs team is able to prioritize after release?

      Show
      1. How does this change affect a user? 2. Why would a user want to use this? 3. What command or series of steps does the user follow to make this change? 4. What is the expected result? 5. Can this affect database performance? How? 6. Is there a minimum or maximum setting for this change (if this is a configurable parameter)? 7. How could the user break something by using this incorrectly? 8. Is there an ideal setting or way of using this feature? 9. Does this feature affect any other settings or parts of the product? 10. Does this feature affect upgrade / downgrade compatibility? 11. Does this replace some other thing that we should downplay / retire / remove? 12. When are docs required? Iteratively throughout the project, at project close/feature release, or whenever the Docs team is able to prioritize after release?
    • Done
    • FY2025Q4 3rd Party Library Upgrades - Developer Tools
    • Hide

      2024-12-10:
      Engineers: Basit Chonka, Paula Stachova, Daniel Echlin
      Currently working on the project: Basit Chonka

      Most of the work we planned for the project is finished - which was to focus on updating Cloud packages.

      • [In Progress] COMPASS-8611: This requires us to update LG dependencies on Compass side
      • [Not doing as part of this epic] CLOUDP-283884: We are not pritorizing this ticket because we are continuously working on CompassWeb and it will be eventually updated on the Cloud side.
      • [Assigned to Search Team] CLOUDP-283876: While working on this ticket we encountered blockers from Search Playground App. This app is nextjs based and fails to build on CI with version bump. This ticket has been assigned to their team.

       

      Show
      2024-12-10: Engineers: Basit Chonka, Paula Stachova, Daniel Echlin Currently working on the project: Basit Chonka Most of the work we planned for the project is finished - which was to focus on updating Cloud packages. [In Progress] COMPASS-8611 : This requires us to update LG dependencies on Compass side [Not doing as part of this epic] CLOUDP-283884: We are not pritorizing this ticket because we are continuously working on CompassWeb and it will be eventually updated on the Cloud side. [Assigned to Search Team] CLOUDP-283876: While working on this ticket we encountered blockers from Search Playground App. This app is nextjs based and fails to build on CI with version bump. This ticket has been assigned to their team.  

      Epic Summary

      Summary

      I have a 3rd Party Ticket, now what?

      There are currently 2 scripts to run that will create linked Jira tickets. After those scripts are run you should be able to schedule the work for the quarter. 

      Script location:

      /mms/scripts/library_upgrades.bash mms/scripts/python/src/mdbutils/language_upgrades.py 

      Fun Documentation: 

      Cloud Third Party Library Upgrade / Vulnerability Policy

      Generate child tickets via cool Dev Prod script:

            Assignee:
            basit.chonka@mongodb.com Basit Chonka
            Reporter:
            martin.bajana@mongodb.com Martin Bajana
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: