Repository navigation
Conversation
Remove release-please, the Release PR, and the committed version bump. The release agent decides when to release and pushes the vX.Y.Z tag; release.yml stamps the tag version into the checkout before it builds, and requires the tagged commit to be on the default branch. The checked-in version is the placeholder 0.1.0.
Replace a draft left by an interrupted run instead of refusing; use python on the Windows leg; write LF newlines when stamping; drop release-please wording from lint docs and AGENTS.md; state the full bump rules.
Replace the inline CI polling script with a pinned wait-on-check action, drop the default-branch guard and the draft-retry logic, and describe the release as a pushed tag, the same for a maintainer and an agent.
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
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.
Summary
Stable releases start from a pushed
vX.Y.Ztag, the same for a maintainer and for an agent:git tag vX.Y.Z && git push origin vX.Y.Z. Whoever completes a requirement decides whether to release. There is no Release PR, release-please,CHANGELOG.md, version commit, or scheduled release job.0.1.0. Each job that builds runsscripts/stamp-version.pywith the tag version. The stamped files are not committed.lewagon/wait-on-check-actiononCI result.docs/release.mdandAGENTS.mddescribe the procedure and the bump rules.Verification
actionlintpasses.scripts/test-stamp-version.pypasses and runs in CI.1.2.3and building with--lockedgiveswright 1.2.3. The update, diagnostics_schema, and cli tests pass with the placeholder.Not verified
No real release has run on this topology. The first tag after merge is the production validation. The wait-on-check action has not run in this workflow yet.