ci: add automated release workflow#10
Merged
Merged
Conversation
There was a problem hiding this comment.
Pull request overview
This PR introduces automated, tag-based Go module releases on the master branch using semantic-release, integrated into the existing GitHub Actions CI pipeline.
Changes:
- Adds a semantic-release configuration (
.releaserc.json) targetingmasterwith Conventional Commits analysis and GitHub Release publication. - Extends the CI workflow to run a gated
releasejob after tests and linting pass, granting onlycontents: writefor the release job. - Documents the release and versioning model in
docs/RELEASE.md.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
docs/RELEASE.md |
Documents the intended automated release model, required token, and local verification checks. |
.releaserc.json |
Configures semantic-release branch and plugins for commit analysis and GitHub release publishing. |
.github/workflows/ci.yml |
Adds a post-CI release job on pushes to master and removes tag-triggered CI runs. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| fetch-depth: 0 | ||
|
|
||
| - name: Release | ||
| uses: cycjimmy/semantic-release-action@v6 |
Comment on lines
+86
to
+89
| @semantic-release/commit-analyzer | ||
| @semantic-release/release-notes-generator | ||
| @semantic-release/github | ||
| conventional-changelog-conventionalcommits |
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.
Changed
master.contents: writepermission.docs/RELEASE.md.Risks
v1.7.3becausefix: improve ValidateToken invalid response handling (#8)is still newer than the latestv1.7.2tag.master, matching the current repository branch.Complexity
.releaserc.json, and release docs.Verification