The Changelog link in the update toast shuold be updated

If I can’t make myself clear, I would like to say sorry and please forgive my poor English.

What I Wanted to Do

I want to see the right Changelog link in the update toast, it should be like https://github.com/npm/cli/releases/tag/v6.5.0

What Happened Instead

In the toast, it was https://github.com/npm/npm/releases/tag/v6.5.0:

Reproduction Steps

  1. Use any version of NPM before v6.5.0.
  2. Run any NPM command.

Details

Platform Info

$ npm --versions
{ 'XXXX': '1.0.0',
  npm: '6.0.0',
  ares: '1.14.0',
  cldr: '33.1',
  http_parser: '2.8.0',
  icu: '62.1',
  modules: '64',
  napi: '3',
  nghttp2: '1.34.0',
  node: '10.14.1',
  openssl: '1.1.0j',
  tz: '2018e',
  unicode: '11.0',
  uv: '1.23.2',
  v8: '6.8.275.32-node.36',
  zlib: '1.2.11' }
$ node -p process.platform
win32

Can you confirm what version of npm you are (or were) running? The code should be updated since v6.2.0 (commit), and the info you provided is weirdly conflicting

I thought I figured out what happend a bit. At that time I still used nodejs v10.14.0 (which includes npm v6.0.0 in it’s program folder), and npm v6.4.1 (which installed in my User folder). When npm v6.4.1 notified there was a new version, it somehow used the update-notifier component in npm v6.0.0, and finally output that notification in the image.
So why nodejs need to include a different version of npm itself? (In the newest version of nodejs, it includes npm v6.4.1)
This image can confirm what I said:
9961

And this(after updating nodejs and npm):

Moved to #support - this is a Windows pathing issue having to do with how windows upgrades work there. Please see https://www.npmjs.com/package/npm-windows-upgrade for upgrading npm on that platform after using the Node installer.

Thanks a lot, that worked fine.

1 Like

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.