You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 4894c4a
Browse filesBrowse the repository at this point in the historyBrowse files
feat(release): release on merge to the trunk, not on a tag
Implements the approved publishing policy (.github-config#17) in the
shared workflows:
- release-check runs on the trunk only, reads the version from the
merged manifest, and reports release=false when that version already
has a GitHub release, so a push that keeps the version publishes
nothing. The new manifest.py release command refuses prerelease
versions, a Helm chart that disagrees with the manifest, and git
dependencies, so stable pins released versions.
- publish creates the tag and the GitHub release last, on the released
commit, with a token from the release GitHub App, the only actor the
release-tags-create ruleset lets create a v* tag.
- crates, docker and publish run in the release environment, which a
bbot-leads member approves. crates.io uses trusted publishing and
skips a version already published. docker drops the dev tag; dev
images go to GHCR.
- The tag subcommand and release.sh, which cut tags by hand, are gone.
0 commit comments