Migrate to use OIDC

[lfarrel6]

Why

Node SDK publishing should be restricted to OIDC tokens from this repo

How

• Split up release workflow into changeset and publish steps
• Remove references to access tokens
• Add OIDC permissions to workflow

[changeset-bot]

⚠️ No Changeset found

Latest commit: c4cf2a9

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	sinon@​9.2.4 ⏵ 9.0.2	+1
	husky@​7.0.4 ⏵ 7.0.2
	chai-as-promised@​7.1.2 ⏵ 7.1.1	+1
	uuid@​8.3.2 ⏵ 8.1.0
	nyc@​17.1.0 ⏵ 17.0.0				-4
	asn1js@​3.0.6 ⏵ 3.0.5
	sinon-chai@​3.7.0 ⏵ 3.5.0
	chai@​4.5.0 ⏵ 4.4.1	+1
	msgpackr@​1.11.4 ⏵ 1.10.1	+1			+4
	lint-staged@​11.2.6 ⏵ 11.1.2				-6
	typescript@​5.8.3 ⏵ 5.3.3	+1		+1
	@​changesets/​cli@​2.29.4 ⏵ 2.29.7				+2

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		License policy violation: npm chai-as-promised under WTFPL License: WTFPL - the applicable license policy does not allow this license (4) (npm metadata) License: WTFPL - the applicable license policy does not allow this license (4) (package/LICENSE.txt) License: WTFPL - the applicable license policy does not allow this license (4) (package/package.json) From: package-lock.json → npm/chai-as-promised@7.1.1 ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/chai-as-promised@7.1.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		License policy violation: npm typescript under CC-BY-4.0 License: CC-BY-4.0 - the applicable license policy does not allow this license (4) (package/ThirdPartyNoticeText.txt) License: LicenseRef-W3C-Community-Final-Specification-Agreement - the applicable license policy does not allow this license (4) (package/ThirdPartyNoticeText.txt) License: MIT-Khronos-old - the applicable license policy does not allow this license (4) (package/ThirdPartyNoticeText.txt) From: package-lock.json → npm/typescript@5.3.3 ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/typescript@5.3.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report