-
-
Notifications
You must be signed in to change notification settings - Fork 33.7k
Closed
Labels
confirmed-bugIssues with confirmed bugs.Issues with confirmed bugs.v18.xIssues that can be reproduced on v18.x or PRs targeting the v18.x-staging branch.Issues that can be reproduced on v18.x or PRs targeting the v18.x-staging branch.
Description
Version
N/A
Platform
No response
Subsystem
No response
What steps will reproduce the bug?
- Look at https://nodejs.org/dist/index.tab - the version 18.20.5 is shown as available.
- Look at https://nodejs.org/dist/v18.20.5/ - only SHA hash files are there.
- Look at https://nodejs.org/dist/v18.20.4/ as a comparison - hashes and downloads are available.
How often does it reproduce? Is there a required condition?
It's consistent.
What is the expected behavior? Why is that the expected behavior?
I expect either the version to be removed from index.tab or the downloads to be available. It's messing up version managers like n and others that assume the index has the list of available releases.
What do you see instead?
Errors from version managers due to missing files (404).
Additional information
No response
gcagle3, bschaefleinhi, taniarascia, brittanyhuntzberry, mcg-copilot-ld and 31 morebuffcode and jay-motwani-trendarnested and avivkeller
Metadata
Metadata
Assignees
Labels
confirmed-bugIssues with confirmed bugs.Issues with confirmed bugs.v18.xIssues that can be reproduced on v18.x or PRs targeting the v18.x-staging branch.Issues that can be reproduced on v18.x or PRs targeting the v18.x-staging branch.
