Update peer dependency versions for driver V7

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Unknown
    • 7.0.0
    • Affects Version/s: None
    • Component/s: None
    • 2
    • 1
    • Not Needed
    • 🔵 Done
    • Hide

      Create a copy of the Kickoff Template with the issue key (NODE-XXX) in the filename and share a link to the new doc via this field.

      Show
      Create a copy of the Kickoff Template with the issue key (NODE-XXX) in the filename and share a link to the new doc via this field.
    • Needed
    • Hide

      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?

      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?
    • None
    • None
    • None
    • None
    • None
    • None

      Use Case

      As a driver engineer and user of the driver,
      I want to have an up-to-date version support specification,
      So that I stay ahead of any deprecations and can make use of improvements

      User Experience

      • n/a

      Dependencies

      • n/a

      Risks/Unknowns

      • n/a

      Acceptance Criteria

      Implementation Requirements

      • "@aws-sdk/credential-providers": "^3.806.0",
      • "gcp-metadata": "^7.0.1"
      • "kerberos": <no change in this ticket>
      • "mongodb-client-encryption": <no change in this ticket>
      • "snappy": "^7.3.2"
      • "socks": "^2.8.6"
      • zstd:
        • Remove support for zstd@1.x from the driver's package.json
        • Remove the zstd@1.x CI tasks
      • Update dependabot config to exclude any dependencies that are peer dependencies from the automatic update

      Testing Requirements

      • all tests pass.

      Documentation Requirements

      • Ensure there is a release note documenting the change

      Follow Up Requirements

      • Compat table updates will be done in NODE-7173
      • Finalization of peer dependency versions with pending major releases will happen in NODE-6997

            Assignee:
            Bailey Pearson
            Reporter:
            Bailey Pearson
            Sergey Zelenov
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: