These are instructions for preparing a release branch for Android Components and starting the next Nightly development cycle.

[Release Management] Creating a new Beta release branch

This part is 100% covered by the Release Management team. The dev team should not perform these steps.

  1. Create a branch name with the format releases/[beta_version].0 off of the main branch (for example, releases/98.0) through the GitHub UI. [beta_version] should follow the Firefox Beta release number. See Firefox Release Calendar.
  2. Notify the dev team that they can start the new Nightly development cycle per the steps given in the next section ⬇️
  3. In Gecko.kt:
    • Set the channel to val channel = GeckoChannel.BETA.
     diff --git a/buildSrc/src/main/java/Gecko.kt b/buildSrc/src/main/java/Gecko.kt
     index 80b4113cae..bea6243f69 100644
     --- a/buildSrc/src/main/java/Gecko.kt
     +++ b/buildSrc/src/main/java/Gecko.kt
     @@ -14,7 +14,7 @@ object Gecko {
           * GeckoView channel
     -    val channel = GeckoChannel.NIGHTLY
     +    val channel = GeckoChannel.BETA
  4. Create a commit named Switch to GeckoView Beta for this change. This change can either be directly committed to the newly-created releases/[beta_version].0 branch or a pull request can be created against it and then merged. Once landed, it is expected that this will create busted builds. The next step should green it up.
  5. The Github Action will automatically bump the GeckoView version once the new Beta build is created and uploaded to Maven, as shown in #12547 for example.
  6. Once both of the above commits have landed, create a new AC release in Ship-It per normal practice.
  7. When the release automation completes, a new v[beta_version].0.0 release tag will be created in Github.
    • Following the template below, update the description with the release notes URL, commit range, and milestone like shown in v104.0.0 and click Update release when ready.
     * [Release notes](
     * [Commits](
     * [Milestone](

[Dev team] Starting the next Nightly development cycle

Please handle this part once Release Management gives you the go.

  1. Wait for greenlight coming from Release Management.
  2. Create a local development branch off of the main branch.
  3. Create a commit named Start [nightly_version].0.0 development cycle. In version.txt, bump the major number by 1. [nightly_version] should follow the Firefox Nightly release number. See Firefox Release Calendar.

     diff --git a/version.txt b/version.txt
     index be9ad8dac55..511c658edc3 100644
     --- a/version.txt
     +++ b/version.txt
     @@ -1 +1 @@
  4. Create a new Github Milestone with the following format [nightly_version].0.0 <insert an emoji> (for example, 99.0.0 🛎). Close the existing milestone and bump all the remaining opened issues to the next milestone or simply remove the tagged milestone depending on what is appropriate.
  5. Create a commit named Update changelog for [nightly_version].0.0 release that will update the following in
    • Add a new [nightly_version].0.0 (In Development) section for the next Nightly version of AC with the next commit and milestone numbers.
    • Update the [beta_version].0.0 section, change blob in the links to v[beta_version].0.0 and specifying the correct commit ranges.
     diff --git a/docs/ b/docs/
     index 895fa9d69f0..f62d9ea6efe 100644
     --- a/docs/
     +++ b/docs/
     @@ -4,20 +4,26 @@ title: Changelog
     permalink: /changelog/
     -# 98.0.0 (In Development)
     -* [Commits](
     -* [Milestone](
     +# 99.0.0 (In Development)
     +* [Commits](
     +* [Milestone](
     * [Dependencies](
     * [Gecko](
     * [Configuration](
     +# 98.0.0
     +* [Commits](
     +* [Milestone](
     +* [Dependencies](
     +* [Gecko](
     +* [Configuration](
  6. Create a pull request with these 2 commits and land.
    • If this is landed after the scheduled cron task that will build and bump AC automatically, trigger a manual AC build through the hook. At time of writing, the morning cron task is schedule to run at 14:30 UTC (9:30AM EST).
    • When the manual AC build is complete, trigger the hook to bump AC in Fenix.
  7. After an hour, follow up by checking if a new [nightly_version] AC build is available in nightly.maven/components. Fenix and Focus will automatically receive the Nightly AC bump.

See for an example.

After the release

  1. Verify that the links in the and new release are working.
  2. Verify that Fenix is receiving the latest [nightly_version] AC version in main.
  3. Send release message to the Matrix channel:
    **Android Components 0.17 Release (:ocean:)**
    Release notes: