Publish of 0.25.1 to npm failed

[hopehadfield]

This is a followup on my comment for more exposure.

To reiterate, the logs from the most recent publish failure contain the error message oidc Failed token exchange request with body message: OIDC token exchange error - package not found. This means Trusted Publishing isn’t configured correctly (or doesn’t match) for this repo/workflow in the npm package settings.

It would be fantastic if the maintainers that have access to the npm settings could make this small configuration correction on their side so that a new release can be published in order to resolve numerous issues faced with the latest release (namely Node 24 support).

[hopehadfield]

@amaanq @maxbrunsfeld not sure if one of you has access to the package settings on npmjs.com + have time to take a look, but I believe this should be as quick as navigating to Trusted Publishers and confirming that there is one for Github Actions set up with the correct namespace/project, workflow filename (publish.yml), and environment name (npm as set here).

It appears that the publish workflow was recently switched from using npm Access Tokens to OIDC Trusted publishing, so this should close the loop on a successful transition there and prevent future releases from being blocked (particularly 0.25.1 which removes the blocker for Node 24 support).

Much appreciated!

[jonkoops]

@ObserverOfTime @nathansobo @amaanq @dundargoc @WillLillis FYI, this is still holding up people from doing their Node.js 24 upgrades (see upvotes on issue). If one of you has the proper access, could you take a look at @hopehadfield's suggestions here?

[erikmueller]

this is still holding up people from doing their Node.js 24 upgrades

FWIW it's also preventing people from adopting tree-sitter in a node 24 environment.