Skip to content

Conversation

@patricklx
Copy link
Collaborator

@patricklx patricklx commented Oct 6, 2025

the token was there to support a flow with no/mininimal changes to release-plan. release plan would do its npm release. create tag & git release. the git tag would then trigger the workflow to do the chrome/firefox release. to support this flow a PAT token was required. as otherwise a git tag would not trigger a new workflow.

anyway, this will not work with latest release-plan

Description

Screenshots

the token was there to support a flow with no/mininimal changes to release-plan.
release plan would do its npm release. create tag & git release.
the git tag would then trigger the workflow to do the chrome/firefox release.
to support this flow a PAT token was required. as otherwise a git tag would not trigger a new workflow
@patricklx patricklx requested a review from mansona October 6, 2025 07:55
@patricklx patricklx changed the title update publish remove token for checkout update npm publish remove token for checkout Oct 6, 2025
@patricklx patricklx changed the title update npm publish remove token for checkout update npm publish: remove token for checkout Oct 6, 2025
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