Skip to content

DOCSP-51349: Upgrade guide #127

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jul 25, 2025
Merged

Conversation

norareidy
Copy link
Collaborator

@norareidy norareidy commented Jul 25, 2025

Pull Request Info

PR Reviewing Guidelines

Note to reviewer: The breaking changes are the same as the Java sync changes, with a couple additions from the Kotlin Sync What's New page. I added PR comments where I made these updates.

JIRA - https://jira.mongodb.org/browse/DOCSP-51349

Staging Links

  • reference/upgrade
  • Self-Review Checklist

    • Is this free of any warnings or errors in the RST?
    • Did you run a spell-check?
    • Did you run a grammar-check?
    • Are all the links working?
    • Are the facets and meta keywords accurate?
    • Are the page titles greater than 20 characters long and SEO relevant?

    Copy link

    netlify bot commented Jul 25, 2025

    Deploy Preview for docs-kotlin-sync ready!

    Name Link
    🔨 Latest commit f6e6691
    🔍 Latest deploy log https://app.netlify.com/projects/docs-kotlin-sync/deploys/6883c1fc38b7f8000852d0d8
    😎 Deploy Preview https://deploy-preview-127--docs-kotlin-sync.netlify.app
    📱 Preview on mobile
    Toggle QR Code...

    QR Code

    Use your smartphone camera to open QR code link.

    To edit notification comments on pull requests, go to your Netlify project configuration.

    @docs-builder-bot
    Copy link

    docs-builder-bot commented Jul 25, 2025

    🔄 Deploy Preview for docs-kotlin-sync processing

    Item Details
    🔨 Latest Commit cf499f493c172191f6c765c5cf15696c1c0fdb51
    😎 Deploy Preview https://deploy-preview-127--docs-kotlin-sync.netlify.app
    🔍 Build Logs View Logs

    Comment on lines 74 to 78
    dependency versioning to match the versioning for the JVM drivers. Future versions of
    ``mongodb-crypt`` will be released alongside the driver and will share the same version number.
    You must upgrade your ``mongodb-crypt`` dependency to v5.2.0 when upgrading your driver for
    this release.
    Copy link
    Collaborator Author

    Choose a reason for hiding this comment

    The reason will be displayed to describe this comment to others. Learn more.

    Note to reviewer: additional breaking change from the Kotlin what's new page

    Comment on lines 87 to 89
    not include comma characters in the ``authMechanismProperties`` connection
    string value.
    Copy link
    Collaborator Author

    Choose a reason for hiding this comment

    The reason will be displayed to describe this comment to others. Learn more.

    Note to reviewer: additional breaking change from the Kotlin what's new page

    Copy link
    Collaborator

    @shuangela shuangela left a comment

    Choose a reason for hiding this comment

    The reason will be displayed to describe this comment to others. Learn more.

    good job, a few comments and questions to address

    changes between the current and upgrade versions. For example, if you
    are upgrading the driver from v5.0 to v5.5, address all breaking changes from
    the version after v5.0 including any listed for v5.5.
    Copy link
    Collaborator

    Choose a reason for hiding this comment

    The reason will be displayed to describe this comment to others. Learn more.

    Suggested change
    the version after v5.0 including any listed for v5.5.
    the versions after v5.0 including any listed for v5.5.

    - Revises the `mongodb-crypt <https://mvnrepository.com/artifact/org.mongodb/mongodb-crypt>`__
    dependency versioning to match the versioning for the JVM drivers. Future versions of
    ``mongodb-crypt`` will be released alongside the driver and will share the same version number.
    Copy link
    Collaborator

    Choose a reason for hiding this comment

    The reason will be displayed to describe this comment to others. Learn more.

    Suggested change
    ``mongodb-crypt`` will be released alongside the driver and will share the same version number.
    ``mongodb-crypt`` are released alongside the driver and share the same version number.

    This driver version introduces the following breaking changes:

    - When using the ``MONGODB-OIDC`` authentication mechanism, you must
    Copy link
    Collaborator

    Choose a reason for hiding this comment

    The reason will be displayed to describe this comment to others. Learn more.

    Suggested change
    - When using the ``MONGODB-OIDC`` authentication mechanism, you must
    - When using the ``MONGODB-OIDC`` authentication mechanism, you must

    what happens if you do?

    Copy link
    Collaborator Author

    @norareidy norareidy Jul 25, 2025

    Choose a reason for hiding this comment

    The reason will be displayed to describe this comment to others. Learn more.

    The only info about the consequences I can find is in the DRIVERS ticket, which says the driver "will parse connection strings ambiguously." I think it just would result in unexpected behavior due to how it's parsed? not sure if that's worth mentioning here, but I added a suggestion to pass the value in the MongoClientSettings instead

    Copy link
    Collaborator

    Choose a reason for hiding this comment

    The reason will be displayed to describe this comment to others. Learn more.

    ok, that works

    To view breaking changes for earlier driver versions, see the
    :github:`Release Notes <mongodb/mongo-java-driver/releases>` in the
    ``mongo-java-driver`` GitHub repository.
    Copy link
    Collaborator

    Choose a reason for hiding this comment

    The reason will be displayed to describe this comment to others. Learn more.

    Should this be changed to the link for release notes in the mongo kotlin driver repo instead?

    Copy link
    Collaborator Author

    Choose a reason for hiding this comment

    The reason will be displayed to describe this comment to others. Learn more.

    The Kotlin driver folder is in the mongo-java-driver repo, i don't think there are specific Kotlin release notes (unless I'm missing something)

    Copy link
    Collaborator

    Choose a reason for hiding this comment

    The reason will be displayed to describe this comment to others. Learn more.

    i see, thanks for checking in on that!

    This driver version introduces the following breaking changes:

    - When using the ``MONGODB-OIDC`` authentication mechanism, you must
    Copy link
    Collaborator

    Choose a reason for hiding this comment

    The reason will be displayed to describe this comment to others. Learn more.

    Suggested change
    - When using the ``MONGODB-OIDC`` authentication mechanism, you must
    - When using the ``MONGODB-OIDC`` authentication mechanism, you cannot


    You cannot use a 3.x version of the {+driver-short+} to connect to a
    MongoDB deployment running {+mdb-server+} v8.1. Starting in {+mdb-server+} v8.1,
    Copy link
    Collaborator

    Choose a reason for hiding this comment

    The reason will be displayed to describe this comment to others. Learn more.

    Suggested change
    MongoDB deployment running {+mdb-server+} v8.1. Starting in {+mdb-server+} v8.1,
    MongoDB deployment running {+mdb-server+} v8.1 or later. Starting in {+mdb-server+} v8.1,

    @norareidy norareidy requested a review from shuangela July 25, 2025 17:46
    Copy link
    Collaborator

    @shuangela shuangela left a comment

    Choose a reason for hiding this comment

    The reason will be displayed to describe this comment to others. Learn more.

    lgtm!

    @norareidy norareidy merged commit f337e8f into mongodb:comp-cov Jul 25, 2025
    5 of 6 checks passed
    @norareidy norareidy deleted the DOCSP-51349-upgrade branch July 25, 2025 18:10
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Labels
    None yet
    Projects
    None yet
    Development

    Successfully merging this pull request may close these issues.

    3 participants