Local gates run Node 26 while the publish job runs Node 22: a web test can pass every gate and fail the publish #11
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/2389-npm-node26"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Tracker: #2389
Merge only after
git.swipelab.com/sx/toolchain:latestcarries Node 26.3.0 (SX request #2390, sx/toolchain#1, then the image rebuild). With the floor at 26.3, a publish on today's Node 22 image fails at start.The publish job's npm moves to 11.16.0, pinned at the registry tarball's sha256; its sha512 equals the registry's
dist.integrity. It runs on a Node floor of 26.3, the Node and npm the local gates run. The lock's source hash, the deploy contract test's fakes and README's Node requirement follow.npm 11.16.0's tarball keeps
package/bin/npm-cli.js, sodeploy_env.sh provisionholds unchanged. Provisioned that way it reports npm 11.16.0 on Node 26.3.0, and thenpm_nodeprobe fails on Node 22.23.2 with "below 26.3".Head:
8fa73e4c08