Conversation
- Add semantic-release with conventional commits analyzer - Auto-bump version based on commit prefixes (feat: minor, fix: patch) - Auto-generate CHANGELOG.md entries - Auto-publish to npm and create GitHub releases - Remove redundant npm-publish workflow Commit prefix rules: - feat: → minor version bump (0.x.0) - fix:/perf:/refactor: → patch version bump (0.0.x) - BREAKING CHANGE: → major version bump (x.0.0) - docs:/style:/chore:/test:/ci: → no release Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> AI-Agent: Claude-Code/2.1.42 AI-Model: claude-opus-4-5-20251101
- Removed "Quick Start" section with CLI examples - Removed detailed Claude Code integration and architecture diagrams - Streamlined content to focus on core concepts and getting started guide links
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Caution Review failedThe pull request is closed. 📝 WalkthroughWalkthroughThe PR migrates the release process from a manual npm publish workflow to an automated semantic-release-based approach. It removes the standalone npm-publish workflow, updates the release workflow to trigger on push-to-main with semantic-release integration, adds semantic-release configuration, and includes corresponding dev dependencies. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~23 minutes Possibly related PRs
Suggested reviewers
✨ Finishing touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Pull request overview
This PR updates the project’s release automation to use semantic-release on merges to main, and trims/adjusts the README header/content.
Changes:
- Add
semantic-releaseand related release tooling todevDependencies. - Introduce
.releaserc.jsonsemantic-release configuration (changelog, git commits, npm + GitHub release). - Replace the previous “version bump detection + manual changelog” workflows by running
semantic-releaseon push tomain(and remove the old npm publish workflow).
Reviewed changes
Copilot reviewed 5 out of 6 changed files in this pull request and generated 5 comments.
Show a summary per file
| File | Description |
|---|---|
| package.json | Adds semantic-release and related plugins/preset packages to support automated releases. |
| README.md | Updates title formatting and removes large “Quick Start / integration” sections; minor whitespace changes. |
| .releaserc.json | Adds semantic-release configuration for commit analysis, release notes, changelog, npm/GitHub publishing, and git commits. |
| .github/workflows/release-on-merge.yml | Switches to a semantic-release driven workflow on push to main. |
| .github/workflows/npm-publish.yml | Removes the redundant workflow now that semantic-release publishes to npm. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| echo "changed=false" >> $GITHUB_OUTPUT | ||
| fi | ||
|
|
||
| release: |
There was a problem hiding this comment.
The @semantic-release/git plugin commit message includes [skip ci], but GitHub Actions doesn't skip workflows based on commit messages by default. This workflow will likely re-run on the release commit push to main (wasting CI minutes). Consider adding a job-level if: condition to skip when github.event.head_commit.message contains [skip ci] (or matches the release commit prefix).
| release: | |
| release: | |
| if: "!contains(github.event.head_commit.message, '[skip ci]')" |
| # Semantic Release: Auto-version and publish on merge to main | ||
| # Analyzes conventional commits to determine version bump: | ||
| # feat: → minor (0.x.0) | ||
| # fix:/perf:/refactor: → patch (0.0.x) | ||
| # BREAKING CHANGE: → major (x.0.0) | ||
|
|
||
| name: Release on PR Merge | ||
| name: Release |
There was a problem hiding this comment.
This PR is titled "readme" but it also introduces semantic-release configuration and replaces the release/publish GitHub Actions workflows. Please update the PR title/description to reflect the release automation changes so reviewers know to focus on CI/release behavior too.
| ## Why? | ||
|
|
||
| Your git history already contains the decisions, conventions, and gotchas that matter — git-mem extracts them and makes them available to Claude automatically. | ||
| Your git history already contains the decisions, conventions, and gotchas that matter — git-mem extracts them and makes them available to Claude automatically. |
There was a problem hiding this comment.
There is trailing whitespace at the end of this line, which is likely unintended and can cause noisy diffs in the future. Please remove the extra space at EOL.
| Your git history already contains the decisions, conventions, and gotchas that matter — git-mem extracts them and makes them available to Claude automatically. | |
| Your git history already contains the decisions, conventions, and gotchas that matter — git-mem extracts them and makes them available to Claude automatically. |
| Every **new** commit is automatically populated with the folowing metadata.. | ||
|
|
||
| - **AI-Agent:** Claude/Opus-4.5 | ||
| - **AI-Agent:** Claude/Opus-4.5 |
There was a problem hiding this comment.
There is trailing whitespace at the end of this list item, which is likely unintended and can cause noisy diffs in the future. Please remove the extra space at EOL.
| - **AI-Agent:** Claude/Opus-4.5 | |
| - **AI-Agent:** Claude/Opus-4.5 |
| persist-credentials: false | ||
|
|
There was a problem hiding this comment.
persist-credentials: false disables the default GitHub token git credential setup from actions/checkout. Since this workflow runs semantic-release with the @semantic-release/git plugin (committing and pushing CHANGELOG/package updates) and tags, the job will likely fail when it tries to git push unless you reconfigure the origin remote with an auth token (or remove persist-credentials: false).
| persist-credentials: false |
Summary by CodeRabbit