You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, after we have a release in the repo, extension-publish.yml runs. It adds the extension to the review queue, which upon approval, immediately publishes the new version publicly.
In the attempt to build a more robust beta-testing setup, we want to change this up a bit. It looks like this:
We are ready to release a new extension version
We create a repo release which runs extension-publish.yml
It adds to review queue and sets the publish-target to trustedTesters
We inform the tester group to review the new update
When they've deemed it all good, we click publish in the developer dashboard, which immediately makes it public
We should sync with Park about securing the gmail's of this particular group of volunteers from discord + likely a dedicated channel for feedback. Their emails need to be manually added within the developer dashboard.
The text was updated successfully, but these errors were encountered:
Currently, after we have a release in the repo, extension-publish.yml runs. It adds the extension to the review queue, which upon approval, immediately publishes the new version publicly.
In the attempt to build a more robust beta-testing setup, we want to change this up a bit. It looks like this:
extension-publish.yml
trustedTesters
We should sync with Park about securing the gmail's of this particular group of volunteers from discord + likely a dedicated channel for feedback. Their emails need to be manually added within the developer dashboard.
The text was updated successfully, but these errors were encountered: