This issue has been created
There are 5 updates.
 
 
XWiki Platform / cid:jira-generated-image-avatar-09531b9e-709c-4db1-834f-557d7f725ea2 XWIKI-24828 Open

npm packages are published with the latest dist-tag even when released from a maintenance branch

 
View issue   ยท   Add comment
 

Issue created

 
cid:jira-generated-image-avatar-e1f44187-7ae3-4cf7-8538-7f0819b49ea4 Manuel Leduc created this issue on 08/Sep/26 11:30
 
Summary: npm packages are published with the latest dist-tag even when released from a maintenance branch
Issue Type: cid:jira-generated-image-avatar-09531b9e-709c-4db1-834f-557d7f725ea2 Bug
Affects Versions: 18.0.0
Assignee: Unassigned
Components: Node
Created: 08/Sep/26 11:30
Priority: cid:jira-generated-image-static-major-11de51c4-fefa-4355-a1ee-8ad4075c35ce Major
Reporter: Manuel Leduc
Description:

Symptom

Running npm install @xwiki/platform-api installs 18.4.5 (the Intermediate LTS, published on 2026-09-08) instead of 18.7.0 (published on 2026-08-31), because the latest dist-tag of the package points to 18.4.5. 44 of the published packages are in that state, while the ones that only exist on the newer branches are untouched, so latest is inconsistent from one package to another.

The same cause made latest point to the release candidate 18.7.0-rc-1 between 2026-08-24 and 2026-08-31.

Maven and Nexus are not affected: Maven resolves an artifact by version and not through a mutable pointer.

Cause

xwiki-platform-core/xwiki-platform-node/src/main/node/scripts/deploy.js publishes a release with pnpm r publish --registry <release registry> --access public --no-git-checks. No tag is passed, so npm writes its default dist-tag, latest, whatever the version being published. Since releases are not published in version order (a maintenance branch is released after a newer branch, and a release candidate before its final version), such a release moves latest backwards. The SNAPSHOT branch of the same script does pass -tag snapshot and is not affected.

Expected

latest always points to the newest released version, and never to a release candidate.

 
 

5 updates

 
cid:jira-generated-image-avatar-e1f44187-7ae3-4cf7-8538-7f0819b49ea4 Changes by Manuel Leduc on 08/Sep/26 11:30
 
Fix Version: 18.8.0-rc-1
Description: h2. Symptom Issue

Running {{npm install @xwiki/platform-api}} installs *18.4.5* (the Intermediate LTS, published on 2026-09-08) instead of *18.7.0* (published on 2026-08-31), because the {{latest}} dist-tag of the package points to 18.4.5. 44 of the published packages are in that state, while the ones that only exist on the newer Maintenance branches are untouched, so {{latest}} is inconsistent from one package to another.

The same cause made {{latest}} point to the release candidate {{18.7.0-rc-1}} between 2026-08-24 and 2026-08-31.

Maven and Nexus are not affected
publishing their packages on [https : Maven resolves an artifact by version and not through a mutable pointer.

h2. Cause

{{xwiki-platform-core
/ xwiki-platform-node / src/main/node/scripts/deploy www . js}} publishes a release with {{pnpm -r publish --registry <release registry> --access public --no-git-checks}} npmjs . No {{--tag}} is passed, so npm writes its default dist-tag, {{ com/] as latest }}, whatever the version being published. Since releases are not published in version order (a maintenance branch is released after a newer branch, and a release candidate before its final version), such a release moves {{latest}} backwards. The SNAPSHOT branch of the same script does pass {{--tag snapshot}} and is not affected.

h2. Expected

{{latest}} always points to the newest released version, and never to a release candidate
. or a maintenance release
Assignee: Manuel Leduc
Component: Node
Component: Development Issues only