ci: auto-generate and commit release artifacts before tagging#17
Merged
Conversation
Consolidate the release flow into a single ordered pipeline that runs on
push to main: resolve the next version, sync it into the manifests,
rebuild all agent artifacts (skills/, dist/, plugins/), validate and
smoke-test them, commit the regenerated files back to main only when they
changed, then tag that commit. The tag now always points at the commit
containing the freshly generated artifacts.
- Fold build-dist-on-pr-merge.yml into release.yml to remove the race
between artifact rebuild and tagging
- Include plugins/ in the auto-committed outputs (previously omitted)
- Relax verify-build.yml to a PR-only build/validate/smoke check and drop
the drift gate so contributors no longer build and commit generated files
- Tag the pushed HEAD via git directly to avoid the tag action targeting
the original GITHUB_SHA
- Document the loop-prevention layers ([skip ci] + GITHUB_TOKEN guard) and
the direct-push-to-main branch-protection assumption
# Conflicts: # .augment-plugin/marketplace.json
- Update version in plugin.json files to 1.1.3. - Improve marketplace install smoke test to handle missing Codex CLI gracefully.
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.
Consolidate the release flow into a single ordered pipeline that runs on
push to main: resolve the next version, sync it into the manifests,
rebuild all agent artifacts (skills/, dist/, plugins/), validate and
smoke-test them, commit the regenerated files back to main only when they
changed, then tag that commit. The tag now always points at the commit
containing the freshly generated artifacts.