npm Community Forum (Archive)

The npm community forum has been discontinued.

To discuss usage of npm, visit the GitHub Support Community.

npm cli: Update banner links to non-existent github release

What I Wanted to Do

I ran npm install and got a notification that a new version was available:

   │                                                               │
   │       New minor version of npm available! 6.1.0 → 6.2.0       │
   │   Changelog: https://github.com/npm/npm/releases/tag/v6.2.0   │
   │               Run npm install -g npm to update!               │
   │                                                               │
   ╰───────────────────────────────────────────────────────────────╯

I copy/pasted the changelog link into my browser to see what’s new, but got a 404.

What Happened Instead

https://github.com/npm/npm/releases/tag/v6.2.0 is a 404

Reproduction Steps

  1. Run npm install with npm 6.1.0
  2. Wait for the notification of 6.2.0 being available to appear
  3. Paste the link into a browser

Details

Platform Info

$ npm --versions
{ npm: '6.1.0',
  ares: '1.14.0',
  cldr: '33.0',
  http_parser: '2.8.0',
  icu: '61.1',
  modules: '64',
  napi: '3',
  nghttp2: '1.32.0',
  node: '10.4.1',
  openssl: '1.1.0h',
  tz: '2018c',
  unicode: '10.0',
  uv: '1.20.3',
  v8: '6.7.288.45-node.7',
  zlib: '1.2.11' }
$ node -p process.platform
darwin


This was already fixed in f0a372b :heavy_check_mark: , and the fix was released in v6.2.0. The correct changelog URL is:


I am pretty sure this link evaluated in npm@6.1.0 and can’t be fixed already.
Though it is possible to make fake 6.2.0 release at original repo to point out to new one.


But people with 6.1.0 installed still receives broken link in their console.
I’d suggest to temporally unfreeze original repo to create fake 6.2.0 release there.


However, what about next releases? When the next version comes out, users of 6.1.0 will have a broken link again. We need to find a better solution, if such exists.


I think this is just gonna have to be this way. Only a couple of releases actually display things this way (6.0.0, 6.0.1, and 6.1.0), and once users upgrade from there, they’ll never see this bug again.

The nature of npm update processes is that we’re kinda stuck with this kind of thing until everyone’s done updating from those versions :upside_down_face:.