std/.github/RELEASE.md
Yoshiya Hinosawa a724d90685
docs: document the release flow (#4754)
Co-authored-by: Asher Gomez <ashersaupingomez@gmail.com>
2024-05-17 12:31:31 +09:00

969 B

This document describes the release flow of the Standard Library for the maintainers. If you're not a maintainer, you don't need to read this document.

The Release Flow

To cut a release, follow the below steps:

  1. Message the Slack #std and Discord #dev-std channels "🔒 std is locked".

  2. Trigger version_bump action with main branch selected.

  3. Wait for @denobot to create a release PR. Note: the tool automatically calculates the necessary version upgrades.

  4. Review PR, and update it if necessary.

  5. Land the PR.

  6. Tag the main branch with release-YYY-MM-DD (this step can be automated in the future):

    git tag release-YYYY.MM.DD
    git push origin release-YYYY.MM.DD
    
  7. Publish the tag from github UI (Re-check the tag is in correct form).

  8. Wait for workspace publish action to publish the new versions to JSR.

  9. Message the Slack #std and Discord #dev-std channels "🔓 std is unlocked <url_of_release>".