Use a release GitHub account for libmongocrypt releases

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Done
    • Priority: Unknown
    • None
    • Affects Version/s: None
    • Component/s: Release Automation
    • None
    • None
    • Not Needed
    • None
    • None
    • None
    • None
    • None
    • None

      Use Case

      Currently, individual engineers' GitHub tokens are used for (some?) releases, e.g. matt.broadstone's GitHub token is still be using for mongodb-client-encryption releases.

      The Rust team currently uses a shared GitHub account to publish their releases to crates.io. https://github.com/mongo-rust-driver

      We should consider repurposing that account or creating a new general drivers release account that could be used for these purposes.

      Dependencies

      • upstream and/or downstream requirements and timelines to bear in mind

      Unknowns

      • questions that need to be answered to determine implementation

      Acceptance Criteria

      Implementation Requirements
      • functional reqs, potential snafus to avoid, performance targets, etc
      Testing Requirements
      • unit test, spec test sync, etc
      Documentation Requirements
      • Document usage in release guide
      Follow Up Requirements
      • additional tickets to file, required releases, etc

            Assignee:
            Alexander Golin (Inactive)
            Reporter:
            Kaitlin Mahar
            None
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: