-
Notifications
You must be signed in to change notification settings - Fork 4.3k
[BUG] After npm publish, npm pack cannot find the package #9043
Copy link
Copy link
Closed
Labels
Bugthing that needs fixingthing that needs fixingNeeds Triageneeds review for next stepsneeds review for next steps
Description
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
In my GitHub Action, I create the release of my project:
- publishes the release in npm;
- retrieves the package tarball;
- adds the tarball to the GitHub release.
Retrieving the tarball doesn't work:
npm error code ETARGET
npm error notarget No matching version found for [email protected].
npm error notarget In most cases you or one of your dependencies are requesting
npm error notarget a package version that doesn't exist.
I added a retry system (5 times every minute). But even after 5 minutes, the tarball is still not found.
At the time of the second attempt in GitHub Action, I ran npm pack on my computer: the tarball was downloaded. I think it's a cache issue in GitHub Action.
I have two other projects with the same problem: JFather and Metalint.
Expected Behavior
You can download the tarball after publishing a new version.
Steps To Reproduce
- In a GitHub Actions.
npm publishnpm pack [email protected]
Environment
- npm: 11.6.2
- Node.js: v24.12.0
- OS Name: Ubuntu 24.04.3 LTS
- System Model Name: GitHub Actions
- npm config:
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Bugthing that needs fixingthing that needs fixingNeeds Triageneeds review for next stepsneeds review for next steps