Repository navigation
chore: upgrade dependencies, jsii 5.9, npm trusted publishing - #279
Merged
Merged
Conversation
Bumps projen to 0.103, jsii to 5.9 (5.7 is end of life), and the rest of the dev deps. projen regenerated the workflows and tsconfig layout. Releases have been failing at the npm publish step since February: the NPM_TOKEN secret is a classic token from 2022 and npm revoked those in December 2025. Switch to trusted publishing (OIDC) instead of a token. Needs a trusted publisher configured on npmjs.com for this repo and release.yml before the next release can go out. Set packageManager explicitly to silence the projen deprecation.
This was referenced Sep 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Monthly upgrade workflow has been failing since April, so this is a manual run of
projen upgradeplus a few projenrc changes.packageManagerset explicitly (new projen deprecation warning).NPM_TOKENto trusted publishing (OIDC).The last two releases (after #276 and #277) failed at the npm publish step. The
NPM_TOKENsecret dates from 2022, i.e. a classic token, and npm revoked all classic tokens in December 2025, right after the v4.3.3 release went out. Rather than mint a new token that expires again, the release job now authenticates via OIDC. That needs a one time setup on npmjs.com: package settings -> Trusted Publisher -> GitHub Actions, orgjetbridge, repocdk-nextjs, workflowrelease.yml. Once that's in place the next push to main will publish 4.3.4.Build, tests and lint pass locally with node 24.