Skip to content

fix(ci): stop committing package.json/package-lock.json version bumps back to the repo #145

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
athal7 merged 1 commit into from
Aug 10, 2026
Merged

fix(ci): stop committing package.json/package-lock.json version bumps back to the repo #145

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 9 additions & 12 deletions .releaserc.cjs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,19 +19,16 @@ module.exports = {
// Generate release notes
'@semantic-release/release-notes-generator',

// Update version in package.json and publish to npm with provenance
// Publish to npm with provenance. package.json's committed version
// stays a placeholder (0.0.0-development) — semantic-release sets
// the real version only in this ephemeral CI checkout before
// `npm publish`, and never commits it back to the repo. No PR, no
// committed version file, ever; the npm registry and git tags are
// the only sources of truth for the release version.
['@semantic-release/npm', { provenance: true }],

// Commit the version changes
[
'@semantic-release/git',
{
assets: ['package.json', 'package-lock.json'],
message: 'chore(release): ${nextRelease.version} [skip ci]\n\n${nextRelease.notes}'
}
],

// Create GitHub release

// Create GitHub release directly from HEAD's tree (no version-bump
// commit precedes it)
'@semantic-release/github'
]
};