Skip to content

[BUG] After npm publish, npm pack cannot find the package #9043

@regseb

Description

@regseb

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 playwright-ghost@v0.17.0.
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

  1. In a GitHub Actions.
  2. npm publish
  3. npm pack foo@v1.2.3

Environment

  • npm: 11.6.2
  • Node.js: v24.12.0
  • OS Name: Ubuntu 24.04.3 LTS
  • System Model Name: GitHub Actions
  • npm config:

Metadata

Metadata

Assignees

No one assigned

    Labels

    Bugthing that needs fixingNeeds Triageneeds review for next steps

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions