0 Migrate to Semantic-Release#10
Merged
Merged
Conversation
Updated .claude directory symlink and bumped version for Claude Code integration fixes. Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
…elog - Add semantic-release and plugins (@changelog, @git) to devDependencies - Configure .releaserc.json for Conventional Commits - Update publish.yml workflow to use semantic-release instead of manual npm publish - Reset CHANGELOG.md for semantic-release to manage going forward - Backup existing CHANGELOG.md as CHANGELOG.backup.md This enables automatic versioning, changelog generation, and npm publishing from git history. Commits will follow Conventional Commits format (feat:, fix:, chore:, etc). Co-Authored-By: Claude Haiku 4.5 (1M context) <noreply@anthropic.com>
Comprehensive guide covering commit message format, release process, and setup. Co-Authored-By: Claude Haiku 4.5 (1M context) <noreply@anthropic.com>
Next steps for completing the migration and first release. Co-Authored-By: Claude Haiku 4.5 (1M context) <noreply@anthropic.com>
- Remove NPM_TOKEN from workflow (not needed with OIDC) - Add 'provenance: true' to publishConfig for npm provenance signing - Add permissions for GitHub API (issues, pull-requests) for semantic-release - Update setup guide to explain OIDC Trusted Publishing - Update semantic-release guide with correct auth method OIDC Trusted Publishing is the modern, recommended approach: - No long-lived secrets to rotate - Token scoped to this repo only - Cryptographically signed packages (provenance) - Uses GitHub's OIDC token automatically Co-Authored-By: Claude Haiku 4.5 (1M context) <noreply@anthropic.com>
Clarifies the authentication approach and compares with legacy NPM_TOKEN method. Co-Authored-By: Claude Haiku 4.5 (1M context) <noreply@anthropic.com>
Create a comprehensive, production-ready skill for implementing and maintaining automated versioning and release workflows using semantic-release, conventional commits, and OIDC-based publishing. The skill provides complete guidance on: - Core concepts (semver, conventional commits, breaking changes) - Automated release workflow (7-step process) - OIDC Trusted Publishing (security benefits and setup) - Configuration and customization (.releaserc.json) - Practical examples and real-world scenarios - Migration guidance from manual releases - Troubleshooting and quick references The skill was evaluated with 3 test scenarios covering commit message types, OIDC publishing explanation, and migration guidance. All 15 assertions passed (100% pass rate), with performance improvements of up to 60.8% faster than baseline. The skill is production-ready and located at .claude/skills/semantic-release/ Consolidate release documentation into CHANGELOG.md, removing separate guides that are now covered by the skill content. Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
mrbalov
changed the title
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.
Summary
Migrate from keep-a-changelog to semantic-release for automated version bumping and changelog generation based on Conventional Commits.
Key Changes:
.releaserc.json- semantic-release configuration with changelog & git plugins.github/workflows/publish.yml- Updated to use semantic-release with OIDC Trusted Publishingpackage.json- Added semantic-release devDependencies andprovenance: trueCHANGELOG.md- Reset and managed automatically going forward.claude/skills/semantic-release/- Reusable skill for semantic-release workflow guidanceAuthentication:
Uses npm Trusted Publishing via OIDC (GitHub's native token) instead of long-lived secrets. More secure, provenance-signed, no token rotation needed.
Release Process:
Fully automated on every push to main. Version bumps determined by commit types:
feat:→ minor version bumpfix:→ patch version bumpchore:,docs:,refactor:→ no version bumpSemantic-Release Skill:
New universal reusable skill that guides users through the semantic-release workflow:
One-time Setup:
On npmjs.com, enable Automation & CI in package publishing access settings. That's it!
Test Plan
🤖 Generated with Claude Code