Validate dev release candidates#225
Merged
Merged
Conversation
coder13
marked this pull request as ready for review
July 14, 2026 02:51
Run CI on dev merge commits and document the reviewed dev-to-master promotion evidence and release blockers for issue #177.
coder13
force-pushed
the
agent/issue-177-dev-release-workflow
branch
from
July 14, 2026 02:51
c092edb to
df45bea
Compare
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.
Implements #177 after the verified baseline synchronization in #226: CI validates pushes to dev and master, with a guard test and current branch-flow/release-evidence documentation.\n\nThis PR must merge to dev; its resulting dev push CI is the release candidate before a reviewed dev-to-master promotion.