Remove references to next tag

[lukekarrys]

We don't currently a next tag, so we shouldn't have instructions to install from there.

Ref: npm/cli#3876

[npm-docs-robot]

👋 I'm your friendly documentation robot, and I'm going to build your pull request on our staging site so that you can review it. If you push up subsequent commits, I'll rebuild your staging area (and when this pull request is closed, I'll clean that staging area up).

I'll let you know when I'm done! 🤖

[npm-docs-robot]

👋 I've finished building this pull request on our staging site. 🤖

To see how it looks, visit: https://docs-staging.npmjs.com/43/

[ljharb]

Just curious; why did the practice of "publish as next, wait a week or two, promote it to latest" go away?

[MylesBorins]

@ljharb we now publish releases every week, so the "wait 2 weeks" thing doesn't really work anymore.

[ljharb]

I’m not sure why that’s the case - you could still have every new version bake as next for any length of time, less than a week or more than, before promoting it to latest.

[MylesBorins]

@ljharb we are working fast and shipping fixes as quickly as we can. The two week waiting period made sense when there was a monthly release cadence for npm.

As Node 16.x is about to go LTS all npm releases will have ~2 weeks in a current release before being promoted to inclusion in LTS, which is where the majority of npm traffic comes from.

If we move towards a longer cadence release cycle we will revisit this but for now there are no plans to change the release process / cadence

[ljharb]

I’m not asking for any changes.

Many people - as advised by npm for MANY years - run npm install -g npm locally and in CI, so I'd imagine there will be significant exposure to new npm versions before node ships them, and being able to update to npm 8 inside an LTS line is a rarity that likely won't be repeatable in future npm versions.