Skip to content

Conversation

@rafaykh90
Copy link
Contributor

Release PR for v2.0.3

@rafaykh90 rafaykh90 requested a review from a team as a code owner November 26, 2025 20:46
@rafaykh90 rafaykh90 merged commit 3d81280 into master Nov 26, 2025
20 checks passed
@acalcutt
Copy link
Contributor

acalcutt commented Nov 26, 2025

unfortunately nobody has been able to update the npm token still, so this publish failed as well https://github.com/mapbox/node-pre-gyp/actions/runs/19718629196/job/56496603081

@rafaykh90
Copy link
Contributor Author

I have published v2.0.3 manually since I have publish permissions to the NPM registry. I don't maintain (or going to maintain) this repo or work with the NPM registry, so I have raised a ticket for the (mapbox) team to rotate the NPM token for the CI.

@rafaykh90 rafaykh90 deleted the v2.0.3 branch November 26, 2025 22:17
@acalcutt
Copy link
Contributor

Oh, nice. At least you were able to get it published. good to know. I look forward to someone responding from mapbox to update the repo npm token

@felixranesberger
Copy link

I have published v2.0.3 manually since I have publish permissions to the NPM registry. I don't maintain (or going to maintain) this repo or work with the NPM registry, so I have raised a ticket for the (mapbox) team to rotate the NPM token for the CI.

Why do you have publish rights? I checked out your profile and you don't seem to have an direct affiliation with the mapbox organisation on GitHub.

@cclauss
Copy link
Collaborator

cclauss commented Dec 3, 2025

Mapbox left this repo unmaintained for a long time, so a few of us "outsiders" were made maintainers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants