Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Github Actions] Automatic publishing to AMO and Chrome Web Store #7

Open
5 tasks
Compile-Time opened this issue Jun 10, 2023 · 2 comments
Open
5 tasks

Comments

@Compile-Time
Copy link
Owner

Compile-Time commented Jun 10, 2023

Add a Github Action flow to publish release archives of the extension to AMO and Chrome Web Store.

TODO:

  • Check if the publishing can be automated for Firefox
  • Check if the publishing can be automated for Chrome
  • Implement automatic publishing for AMO
  • Implement automatic publishing for Chrome Web Store
  • Decide if the action should be run automatically after the release action.
@Compile-Time Compile-Time mentioned this issue Jun 10, 2023
3 tasks
@Compile-Time
Copy link
Owner Author

Compile-Time commented Jun 11, 2023

CLI Publishing for Firefox is possible with the web-ext tool and using the --use-submission-api flag. However, this will probably require a switch away from the NPM script build, since I assume that web-ext will build the extension and then publish it to AMO.

@Compile-Time
Copy link
Owner Author

Compile-Time commented Jun 11, 2023

Example for uploading a Chrome extension automatically: https://l-u-k-e.medium.com/continuously-deploying-a-chrome-extension-e95eeb7cca81

@Compile-Time Compile-Time changed the title Automatic publishing to AMO and Chrome Web Store with Github Actions [Github Actions] Automatic publishing to AMO and Chrome Web Store with Github Actions Jun 12, 2023
@Compile-Time Compile-Time changed the title [Github Actions] Automatic publishing to AMO and Chrome Web Store with Github Actions [Github Actions] Automatic publishing to AMO and Chrome Web Store Jun 12, 2023
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

No branches or pull requests

1 participant