since oidc removes the need for the token
for #958 

since oidc does not currently work for whoami
for #958 

BREAKING CHANGE: v25 of semantic-release is now expected
for #958 

This reverts commit 156b6c8.

...the oidc features are merged

...ions

... oidc

... specific

...publishing

...string

...gistry
for #958 

for #958 

...upported ci providers
for #958 

... required when not using OIDC
for #958 

for #958 

...m various registriess
the trusted publishing verification is incomplete, but this change wires the various options
together, at least
for #958 

...ealing functions
to improve readability
for #958 

...ge can succeed
this is the correct call, but details are still incomplete since the bearer token for the request
needs to be the OIDC token from the CI IdP
for #958 

...change request
for #958 

...shing vs access token use
since trusted publishing is now more required than it previously was:
https://github.blog/changelog/2025-09-29-strengthening-npm-security-important-changes-to-authentication-and-token-management/ 

...b actions
for both trusted publishing and provenance attestations
for #958 

...ctions
for #958 

...context of github actions
for #958 

...ipelines
for #958 

since that logic is now handled with the step to acquire the id-token
for #958 

for #958 

for #958 

...ing context
for #958 

...ithin GitLab Pipelines
for #958 

since stubbing `@actions/core` breaks in that version and i don't want figuring that out to delay
getting the trusted-publishing feature out
for #958 

...lishing from a sub-directory

...g in various contexts
for #958 

now that the ordering of checks and fallbacks have been settled
for #958 

@babblebey babblebey left a comment •

edited by hearts bot

Loading