Skip to content

fix: add @semantic-release/npm plugin to update package.json version#42

Draft
Copilot wants to merge 2 commits into
mainfrom
copilot/fix-semantic-release-versioning
Draft

fix: add @semantic-release/npm plugin to update package.json version#42
Copilot wants to merge 2 commits into
mainfrom
copilot/fix-semantic-release-versioning

Conversation

Copy link
Copy Markdown
Contributor

Copilot AI commented Dec 3, 2025

Semantic-release was not updating package.json with new version numbers during releases.

Changes

  • Added @semantic-release/npm plugin to .releaserc.json plugins array
  • Configured with npmPublish: false since package is private
  • Positioned before @semantic-release/git to ensure version updates before commit
[
  "@semantic-release/npm",
  {
    "npmPublish": false
  }
]

The npm plugin's prepare step updates package.json version, which the git plugin then commits alongside CHANGELOG.md and pnpm-lock.yaml.

Original prompt

This section details on the original issue you should resolve

<issue_title>semantic release issue</issue_title>
<issue_description>semantic release not updating package.json with new version number</issue_description>

Comments on the Issue (you are @copilot in this section)


💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

Co-authored-by: DanStuartDept <87612831+DanStuartDept@users.noreply.github.com>
Copilot AI changed the title [WIP] Fix semantic release not updating package.json version fix: add @semantic-release/npm plugin to update package.json version Dec 3, 2025
Copilot AI requested a review from DanStuartDept December 3, 2025 12:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

semantic release issue

2 participants