Skip to content

fix(release): add missing @semantic-release/npm plugin#198

Merged
fkakatie merged 1 commit intomainfrom
semantic-release-npm
Feb 3, 2026
Merged

fix(release): add missing @semantic-release/npm plugin#198
fkakatie merged 1 commit intomainfrom
semantic-release-npm

Conversation

@fkakatie
Copy link
Member

@fkakatie fkakatie commented Feb 3, 2026

Description

The semantic-release configuration was missing the npm plugin, which is responsible for updating package.json and package-lock.json with the new version number. This caused releases to only update CHANGELOG.md, leaving package.json stuck at version 2.8.4 and preventing dist/aem.js from being regenerated with the correct version.

Motivation and Context

This fix adds the npm plugin with npmPublish:false since this repo uses a custom publish script (publish.sh) instead of publishing directly to npm.

With this change, future releases will properly:

  • Update package.json version
  • Update package-lock.json
  • Regenerate dist/aem.js with correct version
  • Commit all changes to main
  • Trigger the downstream PR to aem-boilerplate with the latest code

How Has This Been Tested?

% npm run semantic-release -- --dry-run --no-ci

> @adobe/aem-lib@2.8.4 semantic-release
> semantic-release --dry-run --no-ci

[1:34:42 PM] [semantic-release] › ℹ  Running semantic-release version 25.0.2
[1:34:43 PM] [semantic-release] › ✔  Loaded plugin "verifyConditions" from "@semantic-release/changelog"
[1:34:43 PM] [semantic-release] › ✔  Loaded plugin "verifyConditions" from "@semantic-release/npm"
[1:34:43 PM] [semantic-release] › ✔  Loaded plugin "verifyConditions" from "@semantic-release/exec"
[1:34:43 PM] [semantic-release] › ✔  Loaded plugin "verifyConditions" from "@semantic-release/git"
[1:34:43 PM] [semantic-release] › ✔  Loaded plugin "verifyConditions" from "@semantic-release/github"
[1:34:43 PM] [semantic-release] › ✔  Loaded plugin "verifyConditions" from "@semantic-release/exec"
[1:34:43 PM] [semantic-release] › ✔  Loaded plugin "analyzeCommits" from "@semantic-release/commit-analyzer"
[1:34:43 PM] [semantic-release] › ✔  Loaded plugin "analyzeCommits" from "@semantic-release/exec"
[1:34:43 PM] [semantic-release] › ✔  Loaded plugin "analyzeCommits" from "@semantic-release/exec"
[1:34:43 PM] [semantic-release] › ✔  Loaded plugin "verifyRelease" from "@semantic-release/exec"
[1:34:43 PM] [semantic-release] › ✔  Loaded plugin "verifyRelease" from "@semantic-release/exec"
[1:34:43 PM] [semantic-release] › ✔  Loaded plugin "generateNotes" from "@semantic-release/release-notes-generator"
[1:34:43 PM] [semantic-release] › ✔  Loaded plugin "generateNotes" from "@semantic-release/exec"
[1:34:43 PM] [semantic-release] › ✔  Loaded plugin "generateNotes" from "@semantic-release/exec"
[1:34:43 PM] [semantic-release] › ✔  Loaded plugin "prepare" from "@semantic-release/changelog"
[1:34:43 PM] [semantic-release] › ✔  Loaded plugin "prepare" from "@semantic-release/npm"
[1:34:43 PM] [semantic-release] › ✔  Loaded plugin "prepare" from "@semantic-release/exec"
[1:34:43 PM] [semantic-release] › ✔  Loaded plugin "prepare" from "@semantic-release/git"
[1:34:43 PM] [semantic-release] › ✔  Loaded plugin "prepare" from "@semantic-release/exec"
[1:34:43 PM] [semantic-release] › ✔  Loaded plugin "publish" from "@semantic-release/npm"
[1:34:43 PM] [semantic-release] › ✔  Loaded plugin "publish" from "@semantic-release/exec"
[1:34:43 PM] [semantic-release] › ✔  Loaded plugin "publish" from "@semantic-release/github"
[1:34:43 PM] [semantic-release] › ✔  Loaded plugin "publish" from "@semantic-release/exec"
[1:34:43 PM] [semantic-release] › ✔  Loaded plugin "addChannel" from "@semantic-release/npm"
[1:34:43 PM] [semantic-release] › ✔  Loaded plugin "addChannel" from "@semantic-release/exec"
[1:34:43 PM] [semantic-release] › ✔  Loaded plugin "addChannel" from "@semantic-release/github"
[1:34:43 PM] [semantic-release] › ✔  Loaded plugin "addChannel" from "@semantic-release/exec"
[1:34:43 PM] [semantic-release] › ✔  Loaded plugin "success" from "@semantic-release/exec"
[1:34:43 PM] [semantic-release] › ✔  Loaded plugin "success" from "@semantic-release/github"
[1:34:43 PM] [semantic-release] › ✔  Loaded plugin "success" from "@semantic-release/exec"
[1:34:43 PM] [semantic-release] › ✔  Loaded plugin "fail" from "@semantic-release/exec"
[1:34:43 PM] [semantic-release] › ✔  Loaded plugin "fail" from "@semantic-release/github"
[1:34:43 PM] [semantic-release] › ✔  Loaded plugin "fail" from "@semantic-release/exec"
[1:34:46 PM] [semantic-release] › ℹ  This test run was triggered on the branch semantic-release-npm, while semantic-release is configured to only publish from main, therefore a new version won’t be published.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist

  • I have signed the Adobe Open Source CLA.
  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

The semantic-release configuration was missing the npm plugin, which is
responsible for updating package.json and package-lock.json with the new
version number. This caused releases to only update CHANGELOG.md, leaving
package.json stuck at version 2.8.4 and preventing dist/aem.js from being
regenerated with the correct version.

This fix adds the npm plugin with npmPublish:false since this repo uses
a custom publish script (publish.sh) instead of publishing directly to npm.

With this change, future releases will properly:
- Update package.json version
- Update package-lock.json
- Regenerate dist/aem.js with correct version
- Commit all changes to main
- Trigger the downstream PR to aem-boilerplate with the latest code
@fkakatie fkakatie requested review from kptdobe and trieloff February 3, 2026 21:46
@fkakatie fkakatie merged commit d2d3f08 into main Feb 3, 2026
4 checks passed
@fkakatie fkakatie deleted the semantic-release-npm branch February 3, 2026 21:53
@trieloff
Copy link
Contributor

trieloff commented Feb 3, 2026

🎉 This PR is included in version 2.10.6 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants