ci: migrate Chrome publishing to API v2 and update release tooling - #96
Merged
Merged
Conversation
Deploying headerly with
|
| Latest commit: |
bd42ef3
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://9ad08702.headerly.pages.dev |
| Branch Preview URL: | https://chore-chrome-publish-api-v2.headerly.pages.dev |
aiktb
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Chrome publishing currently uses legacy v1.1 OAuth credentials. Switch the release workflow to Chrome Web Store API v2 with service account authentication, and ignore local
.env.submitcredentials. Update pnpm to 12.4.2 and synchronize its package-manager lockfile.Before merging, add repository secrets
CHROME_PUBLISHER_ID,CHROME_SERVICE_ACCOUNT_CLIENT_EMAIL, andCHROME_SERVICE_ACCOUNT_PRIVATE_KEY(a multiline PEM key). Keep the existingCHROME_EXTENSION_IDand other store/release credentials. The workflow no longer usesCHROME_CLIENT_ID,CHROME_CLIENT_SECRET, orCHROME_REFRESH_TOKEN.Upgrade
googleapis/release-please-actionfrom v4 to v5.Validation:
pnpm run lint:fixandpnpm run typecheckpassed. Local API v2 authentication and extension access were verified withwxt submit status; no upload or publish was performed.