[PR #58] [MERGED] fix(release): add @semantic-release/npm plugin to update package.json version #76

New issue

Closed

opened 2026-03-03 15:57:39 +03:00 by kerem · 0 comments

kerem commented

2026-03-03 15:57:39 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/mrgoonie/winshot/pull/58
Author: @mrgoonie
Created: 12/24/2025
Status: ✅ Merged
Merged: 12/24/2025
Merged by: @mrgoonie

Base: dev ← Head: goon

📝 Commits (6)

2ddc6d5 Merge remote-tracking branch 'origin/main' into goon
66d6850 chore: merge origin/dev with conflict resolution
9e94f51 Merge pull request #57 from mrgoonie/dev
3527a61 chore(release): 1.4.0 [skip ci]
821fc58 chore: merge origin/main into goon
b30744e fix(release): add @semantic-release/npm plugin to update package.json version

📊 Changes

3 files changed (+14 additions, -1 deletions)

View changed files

📝 .releaserc.json (+6 -0)
📝 CHANGELOG.md (+7 -0)
📝 package.json (+1 -1)

📄 Description

Summary

Add @semantic-release/npm plugin with npmPublish: false to update package.json version during releases
Update package.json version to 1.4.0 (current release)

Problem

package.json was stuck at 1.2.0-beta.3 while releases went up to 1.4.0 because semantic-release was not configured to update package.json.

Fix

Added @semantic-release/npm plugin before @semantic-release/git to ensure version is updated before committing.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/mrgoonie/winshot/pull/58 **Author:** [@mrgoonie](https://github.com/mrgoonie) **Created:** 12/24/2025 **Status:** ✅ Merged **Merged:** 12/24/2025 **Merged by:** [@mrgoonie](https://github.com/mrgoonie) **Base:** `dev` ← **Head:** `goon` --- ### 📝 Commits (6) - [`2ddc6d5`](https://github.com/mrgoonie/winshot/commit/2ddc6d5c35ab1a03b8c67312ffde680c3a47c12a) Merge remote-tracking branch 'origin/main' into goon - [`66d6850`](https://github.com/mrgoonie/winshot/commit/66d68504d400659321f8e5f45bfe52fe29333d9b) chore: merge origin/dev with conflict resolution - [`9e94f51`](https://github.com/mrgoonie/winshot/commit/9e94f518facaeb23b43c1e8d961aa9a860610dcf) Merge pull request #57 from mrgoonie/dev - [`3527a61`](https://github.com/mrgoonie/winshot/commit/3527a61dc72433733c4c729a3963b1eb2f825eb2) chore(release): 1.4.0 [skip ci] - [`821fc58`](https://github.com/mrgoonie/winshot/commit/821fc58d27075fc522cfa58d218b157c6f05f368) chore: merge origin/main into goon - [`b30744e`](https://github.com/mrgoonie/winshot/commit/b30744e0ad5664eb9000973e5cebf4842729f8c4) fix(release): add @semantic-release/npm plugin to update package.json version ### 📊 Changes **3 files changed** (+14 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `.releaserc.json` (+6 -0) 📝 `CHANGELOG.md` (+7 -0) 📝 `package.json` (+1 -1) </details> ### 📄 Description ## Summary - Add `@semantic-release/npm` plugin with `npmPublish: false` to update package.json version during releases - Update package.json version to 1.4.0 (current release) ## Problem package.json was stuck at 1.2.0-beta.3 while releases went up to 1.4.0 because semantic-release was not configured to update package.json. ## Fix Added `@semantic-release/npm` plugin before `@semantic-release/git` to ensure version is updated before committing. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>