Repository navigation
Releases are failing聽#303
Description
Hey there 馃憢馃徎
Opening an issue to give the problem a bit more visibility. As highlighted by @chris48s in #302 (comment):
the release failed with
Access token expired or revokedThis is probably because of https://github.blog/changelog/2025-12-09-npm-classic-tokens-revoked-session-based-auth-and-cli-token-management-now-available/I do have access to set secrets on this repo, but I don't have permission to generate a new NPM token that will be able to publish these packages. However the guidance is to switch from tokens to trusted publishing https://github.blog/changelog/2025-12-09-npm-classic-tokens-revoked-session-based-auth-and-cli-token-management-now-available/#if-you-were-still-using-npm-classic-tokens as write tokens can now last for a max of 90 days.
@bourdakos1 it would be great if you could look into this, thanks in advance!
Activity
bourdakos1 commentedon Jan 17, 2026
Thanks, I鈥檒l try to get this set up today!
bourdakos1 commentedon Jan 17, 2026
Okay, all the packages should have OIDC set up with this repo, so I think the GitHub action just needs to be updated
bourdakos1 commentedon Jan 17, 2026
We seem to be ship shape again, however the action shows as failed for some reason
PyvesB commentedon Jan 19, 2026
Thanks for fixing this, @bourdakos1, the new release did get published as expected! 馃帀