chore: upgrade all dependencies to latest + migrate to npm Trusted Publishing#2
Merged
TimoBechtel merged 2 commits intoFeb 21, 2026
Conversation
… trusted publishing - Upgrade jest: ^26.6.3 → 30.2.0 - Upgrade ts-jest: ^26.5.6 → 29.4.6 - Upgrade typescript: ^4.2.4 → 5.9.3 - Upgrade @types/jest: ^26.0.23 → 30.0.0 - Upgrade microbundle: ^0.13.0 → 0.15.1 - Upgrade @semantic-release/changelog: ^5.0.1 → 6.0.3 - Upgrade @semantic-release/git: ^9.0.0 → 10.0.1 - Upgrade semantic-release: ^17.4.3 → 25.0.3 - Add @semantic-release/npm: 13.1.4 (was missing from devDependencies but used in .releaserc) - Update package.json repository field to HTTPS URL for npm provenance validation - Add tsconfig.json with skipLibCheck and strict settings - Update release workflow to use Node 20, actions/checkout@v4, actions/setup-node@v4 - Migrate release workflow to OIDC Trusted Publishing (remove NPM_TOKEN, add id-token: write) - Update test workflow to use Node 20, actions/checkout@v4, actions/setup-node@v4
Owner
|
@karsten-bot Tests failed. Make sure to use the latest node version in the workflows (22). use gh to see what went wrong and ask the codex coding agent to fix the issues. |
Contributor
Author
|
Found the issue. The workflows were using Node 20, but Fixed: Updated Changes:
|
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
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.
Summary
This PR covers two related improvements:
1. Dependency Upgrades
All dev dependencies have been upgraded to their latest versions:
jestts-jesttypescript@types/jestmicrobundle@semantic-release/changelog@semantic-release/gitsemantic-release@semantic-release/npmMigration notes:
@semantic-release/npmwas referenced in.releaserc.jsonbut not listed as a devDependency — now added at 13.1.4tsconfig.jsonwithskipLibCheck: trueandstrict: trueto fix TypeScript 5.x type-checking with transitive@types/nodeconflictsactions/checkout@v4,actions/setup-node@v4, Node.js 20 (required by semantic-release 25+)2. npm Trusted Publishing Migration
Migrated from token-based (
NPM_TOKEN) to OIDC Trusted Publishing for secure, tokenless npm releases.Changes to
.github/workflows/release.yml:id-token: writepermission for OIDC token generationNPM_TOKENfrom the release step environmentGITHUB_TOKENfor GitHub release/comment actionsChanges to
package.json:repositoryfield from SSH URL to HTTPS URL:npm Trusted Publisher Configuration Required
To complete the migration, a Trusted Publisher needs to be configured on npm:
Package settings URL: https://www.npmjs.com/package/css-vars-from-json/access
Trusted Publisher configuration:
TimoBechtelcss-vars-from-jsonrelease.ymlmainOnce configured, the
NPM_TOKENsecret can be removed from the repository.