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
Release schedule for this submission: when available
Intended distrbution (AMO or Self-hosted): self-hosted (github release)
Remove or strike-out unchanged fields (description, add-on owner, etc.)
Remove or strike-out all badging options except "No badging"
Flag someone from the security team in a comment the created JIRA ticket to ask for a security
review.
Link the JIRA ticket here in a comment
Once the security review has finished and the add-on is released, you can edit the new GitHub
release. Update the release with a name (nimbus-devtools vVERSION) .
Open a new PR that updates update.json:
If the minimum required version of Firefox has not changed since the last release you can
replace the latest entry.
If the minimum required version of Firefox has changed since the last release you must add a
new entry to the list. This ensures that older versions of Firefox can update the addon.
Be sure to verify the add-on version: the web extension infrastructure modifies the last two
components of the version to include the build timestamp.
Welcome Release Captain ! ⛵️
Assign this issue to yourself
Check the v1.0.0 milestone
Check out the main branch:
git checkout mainCheck the following files have the expected version:
package.jsonweb-ext-config.jsonIf they don't, update them in a separate PR.
Create a tag for this release:
git tag release/vVERSION # e.g., release/v0.1.0 git push origin --tagsFill out the Mozilla Add On Review Request Intake Form:
Submit a review request for an updated add-on
Fill in the following fields:
https://github.com/mozilla-extensions/nimbus-devtools/tree/release/vVERSION
Remove or strike-out unchanged fields (description, add-on owner, etc.)
Remove or strike-out all badging options except "No badging"
Flag someone from the security team in a comment the created JIRA ticket to ask for a security
review.
Link the JIRA ticket here in a comment
Once the security review has finished and the add-on is released, you can edit the new GitHub
release. Update the release with a name (nimbus-devtools vVERSION) .
Open a new PR that updates
update.json:If the minimum required version of Firefox has not changed since the last release you can
replace the latest entry.
If the minimum required version of Firefox has changed since the last release you must add a
new entry to the list. This ensures that older versions of Firefox can update the addon.
Be sure to verify the add-on version: the web extension infrastructure modifies the last two
components of the version to include the build timestamp.
Create a milestone for the next release.
Close this issue and the milestone.