ci: add release-please workflow and bump action versions#30
Merged
Conversation
- Add release-please (googleapis/release-please-action@v5) on push to main; release-type `simple`, seeded at 0.1.4 via manifest, `bump-minor-pre-major` so pre-1.0 breaking changes stay in 0.x (no surprise 1.0.0) - Add release-please-config.json + .release-please-manifest.json - Bump actions/checkout v4 -> v7 (foundry-toolchain@v1 already latest major, 1.9.0)
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.
What
googleapis/release-please-action@v5, the latest) to automate versioning,CHANGELOG.md, git tags, and GitHub releases from Conventional Commits.actions/checkoutv4 → v7.foundry-rs/foundry-toolchain@v1is already the latest major (1.9.0), so it's unchanged.release-please configuration
pushtomain— matches this repo's release flow (feature branches →dev, thendev→mainto cut a release). The workflow activates once it reachesmainvia the nextdev → mainmerge.release-type: simple— this is a Foundry library with no package manifest; release-please tracks the version in the manifest +CHANGELOG.mdand tagsvX.Y.Z(matching the existingv0.1.4convention).0.1.4in.release-please-manifest.jsonso it continues from the current release rather than restarting.bump-minor-pre-major: true— pre-1.0, breaking changes bump the minor (e.g.0.1.4 → 0.2.0) instead of jumping to1.0.0. Remove this flag (or userelease-as: 1.0.0) when you're ready for a stable major.GITHUB_TOKEN. Caveat: the release PR it opens won't trigger CI runs — swap in a PAT secret if you want checks on release PRs.Files
.github/workflows/release-please.ymlrelease-please-config.json.release-please-manifest.json.github/workflows/test.yml(checkout v4 → v7)Notes / decisions to confirm
main(inferred from thedev → mainrelease history). If you'd rather release-please open its PRs ondev, change the trigger branch — one line.