-
Notifications
You must be signed in to change notification settings - Fork 1
Closed
Description
Description
As the extension maintainer we want to have a fully automated deploy to the Chrome Store.
Acceptance Criteria
- The extension build process is integrated in the CI pipeline (e.g. GitHub Actions)
-
The version number and metadata are updated as part of the workflow - A valid ZIP package is created for Chrome Web Store submission
- The workflow uses the Chrome Web Store API to authenticate and upload the new version
- OAuth credentials and other secrets are stored securely (e.g. GitHub Secrets)
- The deployment is triggered on new tag or release in the repository
- The process includes a step to publish the submitted version
- Deployment steps and configuration are documented
-
The workflow is successfully tested with a test extension or dry-run mode, if available
Metadata
Metadata
Assignees
Labels
No labels