🛠 Repo: npm releases not marked as latest

[Lightning00Blade]

Tooling Suggestion Checklist

• I have tried restarting my IDE and the issue persists.
• I have pulled the latest main branch of the repository.
• I have read and agree to Mocha's Code of Conduct and Contributing Guidelines
• I have searched for related issues and issues with the faq label, but none matched my issue.
• I want to provide a PR to resolve this

Overview

Starting 11.1.0 something changed so that the new releases are not marked as latest on the npm website - https://www.npmjs.com/package/mocha?activeTab=versions

This means that no automatic tool has pick up the version so that explains the lower numbers of downloads as well.
If this is by intention I didn't manage to find a place that disclose this Changelog or GitHub releases.

Additional Info

No response

[JoshuaKGoldberg]

Ah, good catch, thank you! I solved this for the latest one with:

npm dist-tag add mocha@11.2.2 latest

This should be added to MAINTAINERS.md under ## Mocha's Release Process. It's not noted there now.

cc @voxpelli - maybe there's a way to do this in the automated flow?

[Lightning00Blade]

I think I found when the issue may have been introduced - https://github.com/mochajs/mocha/pull/5216/files#diff-79e894bd12b1ec1a260f6afff87ddaa3e1579fbac8cb64e8fac8cc88e8a6197e
Two things seem off one is marking as prerelease in the config,
second is adding the --tag=next, which seems more likely.

[voxpelli]

Yes, the two release-please changes that configured us to be in prerelease mode needs to be removed, see 80da25a