fix(publish): report publishConfig.tag in publish and stage notices #10136

Open
ljharb opened 6:30pm on October 15, 2026 wants to merge 32 Ξ” into npm/cli latest from
publish-config-tag-notice

Pull Request Overview

  • Opened on October 15, 2026
  • Status Open
  • Commit count 1 with first commit October 15, 2026

Total Delta

32 Total Diff Delta

Open Days

Open 16 weekdays

Test Delta

24 Diff Delta in Test Files
Breakdown by Phase

How long has this pull request spent in each phase of its lifecycle?

Data pending calculation for pull request

Author avatar

fix(publish): report publishConfig.tag in publish and stage notices

A package's publishConfig can set tag, eg "publishConfig": { "tag": "next" }. npm publishes with it, since publishConfig is flattened into opts and the publish uses opts.defaultTag, but the "Publishing to … with tag …" notice, and the npm stage "has been staged with tag …" notice, printed defaultTag, which is read from the CLI config before publishConfig is applied. So npm publish said "with tag latest" while publishing to next.

Both notices now print opts.defaultTag, the tag actually used, with tests for npm publish and npm stage.

No comments have been left on this PR.