Skip to content

ci: add release-please automation#440

Open
klowdo wants to merge 2 commits intomainfrom
feat/release-please
Open

ci: add release-please automation#440
klowdo wants to merge 2 commits intomainfrom
feat/release-please

Conversation

@klowdo
Copy link
Collaborator

@klowdo klowdo commented Mar 4, 2026

Summary

  • Add release-please GitHub Action workflow triggered on push to main
  • Bootstrap manifest at v0.16.0 so release-please knows the current version
  • Use go release type with bump-minor-pre-major to keep pre-1.0 minor bumps

What happens after merge

  1. Release-please scans commits since v0.16.0 and opens a release PR (e.g., chore: release 0.17.0) with a generated CHANGELOG.md
  2. Future pushes to main update that PR automatically
  3. Merging the release PR creates a GitHub Release with the new tag

The ~50 unreleased commits since v0.16.0 will be included in the first changelog.

Test plan

  • Verify workflow runs after merge to main
  • Verify release-please opens a release PR within a few minutes
  • Inspect generated CHANGELOG.md for correct commit categorization

🤖 Generated with Claude Code

Set up release-please with Go release type to automate changelog
generation, version bumping, and GitHub Release creation.
Bootstrapped at v0.16.0.
@coveralls
Copy link

coveralls commented Mar 4, 2026

Coverage Status

coverage: 53.054% (-0.04%) from 53.091%
when pulling 9ca2643 on feat/release-please
into 0a9fd82 on main.

Add changelog-sections config for better categorization. After
release-please creates a release, append non-conventional commits
under "Other Changes" and new contributors from GitHub's generated
notes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants