Pin exact drivers-github-tools versions ahead of v4

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Works as Designed
    • Priority: Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: GitHub Tools
    • None
    • Hide

      DRIVERS-3633:
      If none of your client repos use drivers-github-tools, close this ticket as "Fix Not Needed."

      Summary of necessary driver changes

      •  Update any workflow referencing mongodb-labs/drivers-github-tools/...@v3 (or another floating major-version tag) to pin an exact vX.Y.Z tag or its commit SHA instead; floating tags will not exist for v4+. See the ticket description for an example.

      Commits for syncing spec/prose tests
      (and/or refer to an existing language POC if needed)

      •  Not applicable; this is a CI pin change in each driver's own workflow files, not a spec or prose-test change.

      Context for other referenced/linked tickets

      •  DRIVERS-3601 added the unified release workflow (semver tagging, GitHub Releases) in drivers-github-tools that this migration follows from. No other driver-specific tickets are linked yet — each team should file its own follow-up (or comment here) once it's identified and updated its pin.
      Show
      DRIVERS-3633 : If none of your client repos use drivers-github-tools , close this ticket as "Fix Not Needed." Summary of necessary driver changes  Update any workflow referencing mongodb-labs/drivers-github-tools/...@v3 (or another floating major-version tag) to pin an exact vX.Y.Z tag or its commit SHA instead; floating tags will not exist for v4 +. See the ticket description for an example. Commits for syncing spec/prose tests (and/or refer to an existing language POC if needed)  Not applicable; this is a CI pin change in each driver's own workflow files, not a spec or prose-test change. Context for other referenced/linked tickets   DRIVERS-3601 added the unified release workflow (semver tagging, GitHub Releases) in drivers-github-tools that this migration follows from. No other driver-specific tickets are linked yet — each team should file its own follow-up (or comment here) once it's identified and updated its pin.
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      This ticket was split from DRIVERS-3633, please see that ticket for a detailed description.

            Assignee:
            Unassigned
            Reporter:
            TPM Jira Automations Bot
            None
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: