Clarify release workflow messaging and tooling - #32
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 0b5d375854
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| - Runtime and application integration use only the bundled static assets and the Rust crate. | ||
| - Version bump targets in `Makefile` currently use `npx commit-and-tag-version`. | ||
| - Release and publish validation otherwise run through Cargo and GitHub Actions. | ||
|
|
||
| If you are cutting a release locally, make sure Node.js with `npx` is available before using the `bump-*` targets. |
There was a problem hiding this comment.
bump-*
For maintainers cutting a release locally, this section still omits the step that actually starts the automation: pushing the generated v* tag. I checked .forgejo/workflows/release.yml:4-6, .github/workflows/release.yml:4-7, and .github/workflows/publish-crates.yml:4-6; all of them trigger on tag pushes, while make bump-* only creates the commit/tag locally. Following the README as written can therefore leave release creation and crates.io publishing idle until someone separately does git push --follow-tags (or equivalent).
Useful? React with 👍 / 👎.
0b5d375 to
405112f
Compare
1 participant
Closes #13.
Summary
npx commit-and-tag-version