Investigate release automation failure and release 2.5.1

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Done
    • Priority: Unknown
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • None
    • Go Drivers
    • 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

      The attempt to release 2.4.3 failed in the pre-release step, although it created a github tag with the correct artifacts (and is therefore officially published). The release was not created - so we need to manually create the release notes and announce the release. The SBOM also was not created.

      Definition of done

      1. Manually wrap up the 2.4.3 release so that it has release notes and is announced in the community forums and the go driver channel (might be automatic from the github release - confirm)
      2. Investigate why the release automation failed and try to determine whether it will affect the next minor release from main
        1. Fix the automation for the 2.5 release branch and main (if applicable)
        2. Release 2.5.1
           

      Pitfalls

      What should the implementer watch out for? What are the risks?

            Assignee:
            Matt Dale
            Reporter:
            Daria Pardue
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: