Repository navigation
Conversation
…nch of its own release-keys.md said a production rehearsal runs on any branch; on main it would cancel main's run in flight, as both share a concurrency group. It now names when to rehearse (before a release whose build, stage 06 or suites changed since the last one) and gives the two commands. releases.md's first step asks for a passed rehearsal for a production release, and says a v0.* tag rehearses the jobs only a tag runs.
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Docs only:
docs/release-keys.mdanddocs/releases.md.release-keys.mdsaidgh workflow run distro.yml -f role=productionrehearses the whole flow "on any branch". On main it would cancel main's run in flight:concurrency: distro-${{ github.ref }}withcancel-in-progress: true. The paragraph now:signjob without its approval (no environment for a dispatch), and every suite on the signed media;releases.md's first step asks for a passed rehearsal for a production release. It also says av0.*tag rehearses the jobs only a tag runs (the draft, the source bundle): it builds a development release and drafts a pre-release that can be deleted.Why now: no production build has run since the software images landed, and #610 fixes a zones-suite failure that only a production medium would have shown, which a v1.0.0 tag would have met first.