Releases are failing

@chris48s

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 revoked This 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!

Thanks, I’ll try to get this set up today!

Okay, all the packages should have OIDC set up with this repo, so I think the GitHub action just needs to be updated

We seem to be ship shape again, however the action shows as failed for some reason

@bourdakos1

Thanks for fixing this, @bourdakos1, the new release did get published as expected! 🎉

Navigation Menu

Repository navigation

Releases are failing #303

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Releases are failing #303

Description

Activity

bourdakos1 commented on Jan 17, 2026

bourdakos1 commented on Jan 17, 2026

bourdakos1 commented on Jan 17, 2026

PyvesB commented on Jan 19, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions