Skip to content

Conversation

@lloyd-cio
Copy link

@lloyd-cio lloyd-cio commented Nov 17, 2025

Note

Modernizes the release workflow to use OIDC with Node 20 and actions v4, publishes npm packages as public, adds repo metadata, and upgrades webpack in the browser package.

  • CI/CD (release workflow):
    • Migrate to actions/checkout@v4 and actions/setup-node@v4 with node-version: 20.
    • Configure OIDC: add environment: release and permissions (id-token: write, contents: read); install latest npm for OIDC.
    • NPM publish: remove token env usage and add --access public; GitHub Packages publish still uses GITHUB_TOKEN.
    • Grant contents: write to commit job.
  • Packages:
    • Add repository metadata to packages/core and packages/node package.json.
    • Bump webpack in packages/browser devDependencies to ^5.95.0 (tooling upgrades reflected in lockfile).

Written by Cursor Bugbot for commit 9a1188c. This will update automatically on new commits. Configure here.

@lloyd-cio
Copy link
Author

Going to circle back on this.
The changes needed to get this working are starting to snowball 🤔

@lloyd-cio lloyd-cio changed the title DX-809 update to use preferred OIDC for npm publish in github actions fix(auth): update to use preferred OIDC for npm publish in github actions Nov 19, 2025
@lloyd-cio lloyd-cio changed the title fix(auth): update to use preferred OIDC for npm publish in github actions DX-809 update to use preferred OIDC for npm publish in github actions Nov 19, 2025
@lloyd-cio lloyd-cio changed the title DX-809 update to use preferred OIDC for npm publish in github actions fix(auth): update to use preferred OIDC for npm publish in github actions Nov 19, 2025
@lloyd-cio lloyd-cio changed the title fix(auth): update to use preferred OIDC for npm publish in github actions DX-809 update to use preferred OIDC for npm publish in github actions Nov 19, 2025
@lloyd-cio lloyd-cio merged commit e7d9990 into main Dec 1, 2025
5 checks passed
@lloyd-cio lloyd-cio deleted the DX-809 branch December 1, 2025 16:55
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.

3 participants