feat: add semantic releases and contributor tracking - #1
Conversation
Use semantic-release to derive SemVer from Conventional Commits, generate changelogs, synchronize plugin metadata, and publish GitHub Releases after validated main merges. Record upstream and port contributors from public path history.
Pin the Conventional Commits preset to the major supported by semantic-release's changelog writer so release-note generation completes deterministically.
Validate semantic-release's actual changelog heading format during prepare so the manifest sync, release commit, and tag lifecycle fail closed on real generated output.
|
@codex review |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 1b306400dc
ℹ️ 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".
Remove direct-main release commits, make pnpm the sole package manager, verify the release PR's version and changelog before tagging, and accept linked semantic-release headings.
Put version and changelog preparation before pull-request merge and document the exact manifest update command.
|
🎉 This PR is included in version 1.0.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Details
What this PR does
How it works
Validation
Contributors
Release behavior
After this PR is accepted and merged, the Release workflow revalidates main, confirms the PR-recorded v1.0.0 assets, creates tag v1.0.0, and publishes the GitHub Release without bypassing branch protection.