Pin mockupdb to a released version instead of the master branch

XMLWordPrintableJSON

    • None
    • Python Drivers
    • Not 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

      Context

      pyproject.toml installs the mockupdb dependency group from git+https://github.com/mongodb-labs/mongo-mockup-db@master, a moving branch rather than a released version. Every environment that resolves this group re-fetches whatever commit is currently on master, so builds are not reproducible and a transient fetch failure against that branch can fail the mockupdb test tasks. mongo-mockup-db publishes releases to PyPI; the latest is 1.8.1.

      Definition of done

      • The mockupdb dependency group in pyproject.toml depends on a released version of mockupdb from PyPI instead of the master git ref.
      • The lockfile reflects the pinned version.
      • The mockupdb test tasks still pass against the released version.

      Pitfalls

      • Master may contain fixes or API changes not yet in the latest PyPI release (1.8.1, released 2021-10-15) — check whether any test in test/mockupdb/ relies on behavior only present past that tag before switching.
      • mockupdb is a `dependency-groups` entry gated behind --group mockupdb, not a default sync group — confirm the pin doesn't change that gating.

            Assignee:
            Steve Silvester
            Reporter:
            Steve Silvester
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: