[BUG] released npm package version not available even after some time

[paralin]

Is there an existing issue for this?

• I have searched the existing issues

This issue exists in the latest npm version

• I am using the latest npm

Current Behavior

https://github.com/aperturerobotics/pragmasevka/actions/runs/21372199825/job/61519375987#step:4:31

I published 1.0.5 of @aptre/pragmasevka a while ago (almost an hour) and it's not appearing at https://www.npmjs.com/package/@aptre/pragmasevka?activeTab=versions nor is it appearing when I try to npm install it (returns not found for that version). Same for 1.0.4 which I also released recently. Why?

Environment

  - npm: 11.7.0
  - Node.js: v25.4.0
  - OS Name: Ubuntu 24.04.3 LTS
  - System Model Name: GitHub Actions runner (ubuntu-24.04 image v20260119.4.1)
  - npm config: [default]

[danny-avila]

Same issue here.

• Publish command returned success: + @librechat/agents@3.1.2
• Sigstore provenance recorded: https://search.sigstore.dev/?logIndex=857180802
• Version not appearing on https://www.npmjs.com/package/@librechat/agents?activeTab=versions
• npm view @librechat/agents@3.1.2 returns not found

Published via GitHub Actions with OIDC trusted publishing ~30 mins ago.

[rexxars]

Edit: Eventually showed up, ~2 hours after the publish.

Yep, seeing same issue here.

• Publish command returned success: + @sanity/codegen@5.7.0
• Sigstore provenance recorded: https://search.sigstore.dev/?logIndex=857146266
• Version not appearing on https://www.npmjs.com/package/@sanity/codegen?activeTab=versions
• npm view @sanity/codegen@5.7.0 returns not found

Published via GitHub Actions with OIDC trusted publishing ~1 hour ago (2026-01-26T20:14:58Z).

[kchindam-infy]

After a successful npm publish, there can be a delay before the version is visible via npm view,npm install or npmjs.com due to registry replication. The version is now visible on the pacakage page and available via npm view/npm install

(
"dependencies": {
  "@aptre/pragmasevka": "^1.0.5"
}
Closing the issue as expected behaviour

[paralin]

@kchindam-infy It is a mistake for you to close this when multiple people are reporting 30-60 minute delays in seeing new versions, which is far longer than the usual 1 minute or so under normal conditions.