Skip to content

Conversation

@GODrums
Copy link
Collaborator

@GODrums GODrums commented Apr 1, 2025

Motivation

Implements tasks 1-3 of #302.

Description

This PR adds a new Github Actions workflow to automate the publishing flow to extension stores (Chrome + Firefox).
It uses Actions provided by Browser Actions. The workflow starts directly after a successful run of the release workflow.

Setup

A general explanation for the tokens can be found here. The workflow requires multiple repository secrets to be set up:

# Extension ids
CHROME_EXTENSION_ID=""
FIREFOX_EXTENSION_ID=""
# Chrome Web Store secrets
# How to get them: https://github.com/PlasmoHQ/chrome-webstore-api/blob/main/token.md
# Or: https://github.com/fregante/chrome-webstore-upload-keys
OAUTH_CLIENT_ID=""
OAUTH_CLIENT_SECRET=""
OAUTH_REFRESH_TOKEN=""
# Firefox Add-On Store secrets
# How to get them: https://addons.mozilla.org/en-US/developers/addon/api/key/
AUTH_API_ISSUER=""
AUTH_API_SECRET=""

@GODrums GODrums marked this pull request as ready for review April 2, 2025 12:06
@GODrums GODrums requested a review from Step7750 April 2, 2025 12:06
@GODrums
Copy link
Collaborator Author

GODrums commented Apr 7, 2025

@Step7750
I reworked the publishing using the Github Actions by Browser Actions now. The workflow is now designed to run directly after the release workflow has succeeded and reuses its uploaded assets.

@GODrums GODrums requested a review from Step7750 April 7, 2025 11:34
Copy link
Member

@Step7750 Step7750 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've added the necessary secrets, so we should be good to go with merging this and trying it out.

@GODrums GODrums merged commit d2a35b3 into master Apr 11, 2025
2 checks passed
@GODrums GODrums deleted the action-extension-publishing-workflow branch April 11, 2025 10:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants