Skip to content

fix(ci): upgrade actions/setup-node to v4 for OIDC trusted publishing - #543

Merged
gund merged 1 commit into
masterfrom
fix/upgrade-setup-node-v5
Jul 17, 2026
Merged

gund merged 1 commit into
masterfrom
fix/upgrade-setup-node-v5

Conversation

@gund

@gund gund commented Jul 17, 2026

Copy link
Copy Markdown
Owner

Upgrade actions/setup-node from v3 to v4 and actions/checkout from v3 to v4.

actions/setup-node@v3 does not properly configure OIDC tokens for npm trusted publishing, causing 401 Unauthorized errors when @semantic-release/npm tries to authenticate with the npm registry.

actions/setup-node@v4 adds proper OIDC support for trusted publishing.

@gund
gund merged commit bfa1cbc into master Jul 17, 2026
12 checks passed
@gund
gund deleted the fix/upgrade-setup-node-v5 branch July 17, 2026 15:27
github-actions Bot pushed a commit that referenced this pull request Jul 17, 2026
# [11.0.0](v10.8.2...v11.0.0) (2026-07-17)

### Bug Fixes

* **build:** rename api-extractor golden files to .api.md extension ([#546](#546)) ([88e545e](88e545e))
* **ci:** add npm overrides to force @semantic-release/npm@10 ([#541](#541)) ([56cd1d1](56cd1d1))
* **ci:** add registry-url to setup-node for OIDC trusted publishing ([#540](#540)) ([c84a87f](c84a87f))
* **ci:** regenerate package-lock.json with complete esbuild binaries ([#545](#545)) ([449fb86](449fb86))
* **ci:** upgrade @semantic-release/npm to v13 for OIDC trusted publishing support ([#544](#544)) ([f0cd6d7](f0cd6d7))
* **ci:** upgrade actions/setup-node to v4 for OIDC trusted publishing ([#543](#543)) ([bfa1cbc](bfa1cbc))

* fix(io)!: remove ComponentFactoryResolver for Angular 22 compatibility ([2727318](2727318)), closes [#528](#528)

### BREAKING CHANGES

* IoService constructor no longer accepts ComponentFactoryResolver. This removes a public constructor dependency reflected in the public API golden.

This branch was previously deployed

1 inactive deployment
public-api — 2ff6a462 Deployed Jul 17, 2026 by gund via Check #71
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.

1 participant