v2.0.1 did not properly release on npm
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.2k
- Forks
- 271
- Avg merge
- 23h 40m
- Merged PRs (30d)
- 2
Description
In https://github.com/mapbox/node-pre-gyp/pull/905 we tried to release v2.0.1, but it seems to have [failed](https://github.com/mapbox/node-pre-gyp/actions/runs/14929738686/job/41943208170) due to the NPM_TOKEN stored in the repo being expired, since the same error happened the last time we made a release in https://github.com/mapbox/node-pre-gyp/pull/888#issuecomment-2525291849 and that token had expired then.
We discussed who can update this, but it doesn't sounds like anyone has permission to do this.. In the past @mapsam suggested @bilindhajer could help last time, but I am not sure that is still true. (if either of you have any suggestions that would be helpful)
In https://github.com/mapbox/node-pre-gyp/pull/905#issuecomment-2869125170 I did offer to become a maintainer, so if someone wanted to give my npm account 'acalcutt' access to make a release, maybe I could help get that key updated. I have been making my own release at [npm](https://www.npmjs.com/package/@acalcutt/node-pre-gyp) and [git](http://github.com/acalcutt/node-pre-gyp) and would love to move away from having my own release.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the failed GitHub Actions run linked from PR 905 and compare it with the prior failure referenced in PR 888. Confirm the release workflow's NPM_TOKEN access and identify an authorized maintainer who can update the credential or release permissions. Done means v2.0.1 can be published through the repository's release process rather than a separate forked package.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, javascript
- Domain
- ci-cd, release
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 15/100