⚙️ setup: add release build flow automation - #15
Merged
Merged
Conversation
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.
Add the same release configuration used by
wgtechlabs/clean-codingandwgtechlabs/clean-code-review. The workflow is byte-identical to both reference repositories and pinswgtechlabs/release-build-flow-actionat6df9cb42c24c296d902150d051a0b6be4422cccc.On pushes to
main, it plans the release without mutations, updates and stages.codex-plugin/plugin.json, then publishes the planned changelog, tag, and GitHub Release. Automatic synchronization of other package manifests is disabled. The README explains automation and points to the manifest for the current plugin version.Validation: YAML structure, pinned action input/output compatibility, shell syntax, README links, and diff whitespace checks passed. The version-update shell step ran in disposable Git repositories and staged only the expected manifest with its version changed. Existing deployment workflows are unchanged. The complete GitHub-hosted release has not been run; it activates after promotion to main.
This update is included in promotion #14. Clean Commit already has a v1.0.0 tag, so version planning continues that release history rather than using the no-tag 0.1.0 initial version.