[Bug?]: Version 4.13.0 is not available in `@yarnpkg/cli-dist`

[stof]

Self-service

• I'd be willing to implement a fix

Describe the bug

https://www.npmjs.com/package/@yarnpkg/cli-dist does not have the 4.13.0 version available.

The heroku nodejs buildpack relies on this @yarnpkg/cli-dist to install yarn when finding a package manager reference in the package.json.

To reproduce

npm install -g "@yarnpkg/cli-dist@4.13.0"

Environment

node.js 22.22.0

Additional context

No response

[arcanis]

Yeah, GH hasn't been in great shape this week ... still an ongoing incident impacting Actions:
https://www.githubstatus.com/

We currently have 67 queued actions ...

[stof]

Looking at https://github.com/yarnpkg/berry/actions/runs/22594501121, I think that the release process failed instead of being part of the queued jobs

[arcanis]

Probably a fluke on the npm/gh side; the 404 on @yarnpkg/fslib doesn't make a ton of sense. I'll see if I can republish that release without breaking its provenance.

[hamidrezahanafi]

@arcanis this is still not working

[JounQin]

Friendly @arcanis

[arcanis]

I re-ran the release but the same package still ended up with a 404 😔 I'll try changing the token, failing that I'll release from my laptop and skip provenance for this release

[JounQin]

I re-ran the release but the same package still ended up with a 404 😔 I'll try changing the token, failing that I'll release from my laptop and skip provenance for this release

@arcanis npm tokens will expired rapidly nowadays, it should be migrated to trusted publishing instead.

See also e18e/ecosystem-issues#201

[arcanis]

It'll take a bit of work as we currently release from multiple workflows, and npm only supports one iirc. At least for now it should be fixed with the temporary token.