Uploaded image for project: 'Node.js Driver'
  1. Node.js Driver
  2. NODE-5383

Automate BSON release process

    • 2
    • Not Needed
    • 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?

      Use Case

      As a node engineer
      I want to reuse the new driver release workflow
      So that I can make BSON changes available swiftly and securely

      User Impact

      • None

      Dependencies

      • None

      Unknowns

      • None

      Acceptance Criteria

      Implementation Requirements

      • Duplicate the release workflow used for releasing from driver main
        • Ensure BSON is released with provenance enabled
      • Duplicate the release_notes workflow & scripts
      • Update the BSON PR template

      Testing Requirements

      • Manual verification
        • Use dry-run flag to test with manually kicked off release runs
        • Run a release_notes test against a release PR

      Documentation Requirements

      • Update release instructions if any salient details are different from the driver's steps

      Follow Up Requirements

      • None

            Assignee:
            neal.beeken@mongodb.com Neal Beeken
            Reporter:
            neal.beeken@mongodb.com Neal Beeken
            Durran Jordan
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: