Using this action:
uses: Klemensas/chrome-extension-upload-action@$VERSION
with:
refresh-token: 'xxxxxxxxxxxxxxxxxxxxxx'
client-id: 'xxxxxxxxxxxxx'
client-secret: 'xxxxxxxxxxxx'
file-name: './extension.zip'
app-id: 'xzc12xzc21cx23'
publish: true
The workflow should check some sort of test before build. Upon successful build, creates a new version using semantic-release. If version is bumped, then publishes the extension to chrome web store.