Draft
Conversation
Deploying midscene with
|
| Latest commit: |
37ff9d1
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://dfe3c09b.midscene.pages.dev |
| Branch Preview URL: | https://codex-automate-chrome-web-st.midscene.pages.dev |
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
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.
Summary
This change adds automated Chrome Web Store publishing for the Midscene Chrome extension as part of the existing stable release workflow, while keeping GitHub Release generation intact if the store publish step fails.
What Changed
scripts/publish-chrome-extension.shhelper that:.github/workflows/release.ymlso the mainreleasejob still produces the GitHub Release and packaged extension artifact firstpublish_chrome_web_storejobCONTRIBUTING.mdWhy
The current release workflow already produces the packaged extension zip as a release asset. This change closes the last manual gap for stable releases, but still preserves a reliable manual fallback path when Chrome Web Store publishing fails.
Impact
alpha,beta, andrcreleases continue to skip Chrome Web Store publicationCHROME_WEB_STORE_PUBLISHER_IDCHROME_WEB_STORE_CLIENT_IDCHROME_WEB_STORE_CLIENT_SECRETCHROME_WEB_STORE_REFRESH_TOKENValidation
bash -n scripts/publish-chrome-extension.shbash scripts/publish-chrome-extension.sh --helppnpm run lint