npm: Hash-based Publishing Breaking Semver Convention

Open
#1,852 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
62/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
javascript, nodejs
Domain
ci-cd, release

Research direction

Locate the CI configuration containing the hash-based npm-publish-build job and read how it publishes packages on pushes and pull requests. Make the publishing workflow either remove that job or check whether a version already exists, then verify that unchanged commits do not create duplicate package versions.

Written by the indexing model from the issue text.

Description

For many years, NSS has followed semver with branch protection and reviews. Since December 2025, CI was changed to publish hash-versioned packages on every push and PR, creating new versions on each commit regardless of whether functionality has changed.

Suggested fix:

  • Remove the hash-based npm-publish-build job, or
  • Add a version-exists check to prevent duplicate publishes.
Dominant language
JavaScript
Stars
1.8k
Forks
308
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nodeSolidServer/node-solid-server

All issues in nodeSolidServer/node-solid-server

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.