Fix part of #6106: Add In-Depth Release Reference wiki page by Sandesh282 · Pull Request #6355 · oppia/oppia-android

Sandesh282 · 2026-08-13T04:06:38Z

Fixes part of #6106

Explanation

The Oppia Android release pipeline has been progressively automated, but the tooling for manual fallback — what a coordinator should do when a workflow fails mid-run — has lived nowhere accessible. This PR adds the In-Depth Release Reference wiki page, which is the manual fallback guide for every automated workflow in the release pipeline.

The page covers all 8 workflows in order: generate_changelog.yml, auto_release_alpha.yml, pull_latest_lesson_versions.yml, deploy_updated_changelog.yml, build_and_sign.yml, deploy_to_firebase.yml, deploy_to_play_console.yml, and update_rollout.yml. For each, it documents the normal trigger and purpose, then gives copy-pasteable bazel run commands a coordinator can run locally to replicate what the workflow does. Where a workflow has multiple failure modes (e.g. auto_release_alpha.yml can fail with "no commits", "no passing CI", or a dispatch failure), each case is addressed separately.

The page is cross-linked from the Release Playbook so that every automated step in the playbook has a direct path to its manual equivalent.

Essential Checklist

The PR title starts with "Fix #bugnum: " (If this PR fixes part of an issue, prefix the title with "Fix part of #bugnum: ...".)
The explanation section above starts with "Fixes #bugnum: " (If this PR fixes part of an issue, use instead: "Fixes part of #bugnum: ...".)
Any changes to scripts/assets files have their rationale included in the PR explanation.
The PR follows the style guide.
The PR does not contain any unnecessary code changes from Android Studio (reference).
The PR is made from a branch that's not called "develop" and is up-to-date with "develop".
The PR is assigned to the appropriate reviewers (reference).

Disclosure of LLM Usage

AI was used for code completion, drafting wiki content, and research.

coderabbitai · 2026-08-13T04:06:45Z

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 57129583-d133-41f5-ace2-3eb4c97f4a77

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

🔍 Trigger review

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands.}

github-actions · 2026-08-13T04:42:45Z

Coverage Report

Results

Coverage Analysis: SKIP ⏭️

This PR did not introduce any changes to Kotlin source or test files.

To learn more, visit the Oppia Android Code Coverage wiki page

oppiabot · 2026-08-20T10:55:52Z

Hi @Sandesh282, I'm going to mark this PR as stale because it hasn't had any updates for 7 days. If no further activity occurs within 7 days, it will be automatically closed so that others can take up the issue.
If you are still working on this PR, please make a follow-up commit within 3 days (and submit it for review, if applicable). Please also let us know if you are stuck so we can help you! If you're unsure how to reassign this PR to a reviewer, please make sure to review the wiki page that details the Guidance on submitting PRs.

…See-also footer

oppiabot · 2026-09-03T19:34:47Z

Hi @Sandesh282, I'm going to mark this PR as stale because it hasn't had any updates for 7 days. If no further activity occurs within 7 days, it will be automatically closed so that others can take up the issue.
If you are still working on this PR, please make a follow-up commit within 3 days (and submit it for review, if applicable). Please also let us know if you are stuck so we can help you! If you're unsure how to reassign this PR to a reviewer, please make sure to review the wiki page that details the Guidance on submitting PRs.

adhiamboperes

PTAL @Sandesh282.

adhiamboperes · 2026-09-07T02:19:32Z

+manually outside of its normal trigger. It is linked from the
+[Release Playbook](Release-Playbook.md).


Suggested change

manually outside of its normal trigger. It is linked from the

[Release Playbook](Release-Playbook.md).

manually outside of its normal trigger.

Not necessary?

adhiamboperes · 2026-09-07T02:20:48Z

+1. [generate\_changelog.yml fails](#1-generate_changelogymlfails)
+2. [auto\_release\_alpha.yml fails](#2-auto_release_alphaymlfails)
+3. [pull\_latest\_lesson\_versions.yml fails](#3-pull_latest_lesson_versionsymlfails)
+4. [deploy\_updated\_changelog.yml fails](#4-deploy_updated_changelogymlfails)
+5. [build\_and\_sign.yml fails](#5-build_and_signymlfails)
+6. [deploy\_to\_firebase.yml fails](#6-deploy_to_firebaseymlfails)
+7. [deploy\_to\_play\_console.yml fails](#7-deploy_to_play_consoleymlfails)
+8. [update\_rollout.yml fails](#8-update_rolloutymlfails)


Same feedback as before: refer to workflows by their display names

adhiamboperes · 2026-09-07T02:26:19Z

+The workflow exits cleanly (no error). No action needed unless a release is urgent — in that
+case, manually dispatch the workflow or extend the commit search limit via `workflow_dispatch`
+inputs.


Please provide further isntructions to manually dispatch the workflow.

or extend the commit search limit via workflow_dispatch inputs.

How is this possible?

adhiamboperes · 2026-09-07T02:31:41Z

+**Case C — Workflow succeeded but `build_and_sign.yml` was not dispatched:**
+


Can you give an example of how this scenario might come about?

adhiamboperes · 2026-09-07T02:31:56Z

+Manually force-push the `latest-alpha` tag to the desired commit and then trigger
+`build_and_sign.yml`:


How can"Manually force-push the latest-alpha tag" be done?

adhiamboperes · 2026-09-07T02:38:06Z

+
+**Manual fallback:**
+
+1. Obtain `prod_server.key` from the repository secret (ask the infrastructure team).


It's best to ask the tech leads to perform this recovery, because the prod server key will likely not be distributed for security reasons.

adhiamboperes · 2026-09-07T02:39:52Z

+
+**What it does:** Downloads the latest lesson versions from the Oppia production server and
+opens a PR updating `config/lessons/*.textproto`.
+


Under what circumstance is the workflow likely to fail, such that one of the recovery steps isn't manual dispatch of the workflow?

adhiamboperes · 2026-09-07T02:43:48Z

+| Changelog missing | Ensure `config/changelogs/<version>.md` exists and is merged to `develop` |
+| Active edit session conflict | Wait ~5 minutes for the previous Play API session to expire, then retry |
+
+**Manual fallback — Play Console web UI:**


The section is missing info about how to manually freeze a bundle.

adhiamboperes · 2026-09-07T02:47:45Z

+   - `version`: e.g. `0.18`
+   - `flavor`: `alpha`, `beta`, or leave blank for the default changelog
+
+**Manual fallback — run script locally:**


I believe changelogs can be manually edited eithing Play Console.

oppiabot · 2026-09-07T02:51:11Z

Unassigning @adhiamboperes since the review is done.

oppiabot · 2026-09-07T02:51:14Z

Hi @Sandesh282, it looks like some changes were requested on this pull request by @adhiamboperes. PTAL. Thanks!

Add placeholder for In-Depth Release Reference wiki page

2e6ef68

Sandesh282 self-assigned this Aug 13, 2026

Sandesh282 changed the title ~~Fix part of #6106: Add placeholder for In-Depth Release Reference wiki page~~ Fix part of #6106: Add In-Depth Release Reference wiki page Aug 13, 2026

first writeup

fbfe905

oppiabot Bot added the stale Corresponds to items that haven't seen a recent update and may be automatically closed. label Aug 20, 2026

Sandesh282 removed the stale Corresponds to items that haven't seen a recent update and may be automatically closed. label Aug 22, 2026

Sandesh282 marked this pull request as ready for review August 23, 2026 16:59

Sandesh282 requested review from a team as code owners August 23, 2026 16:59

Sandesh282 requested a review from adhiamboperes August 23, 2026 16:59

Sandesh282 assigned adhiamboperes and unassigned Sandesh282 Aug 27, 2026

Style: remove backtick headings, fix download_lesson_list args, drop …

251663c

…See-also footer

oppiabot Bot added the stale Corresponds to items that haven't seen a recent update and may be automatically closed. label Sep 3, 2026

adhiamboperes removed the stale Corresponds to items that haven't seen a recent update and may be automatically closed. label Sep 4, 2026

adhiamboperes requested changes Sep 7, 2026

View reviewed changes

oppiabot Bot unassigned adhiamboperes Sep 7, 2026

oppiabot Bot assigned Sandesh282 Sep 7, 2026

		manually outside of its normal trigger. It is linked from the
		[Release Playbook](Release-Playbook.md).

	manually outside of its normal trigger. It is linked from the
	[Release Playbook](Release-Playbook.md).
	manually outside of its normal trigger.

		Case C — Workflow succeeded but `build_and_sign.yml` was not dispatched:

		Manually force-push the `latest-alpha` tag to the desired commit and then trigger
		`build_and_sign.yml`:


		Manual fallback:

		1. Obtain `prod_server.key` from the repository secret (ask the infrastructure team).


		What it does: Downloads the latest lesson versions from the Oppia production server and
		opens a PR updating `config/lessons/*.textproto`.

Uh oh!

Conversation

Sandesh282 commented Aug 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Explanation

Essential Checklist

Disclosure of LLM Usage

Uh oh!

coderabbitai Bot commented Aug 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Review skipped

Uh oh!

github-actions Bot commented Aug 13, 2026

Coverage Report

Results

Uh oh!

oppiabot Bot commented Aug 20, 2026

Uh oh!

oppiabot Bot commented Sep 3, 2026

Uh oh!

adhiamboperes left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

oppiabot Bot commented Sep 7, 2026

Uh oh!

oppiabot Bot commented Sep 7, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Sandesh282 commented Aug 13, 2026 •

edited

Loading

coderabbitai Bot commented Aug 13, 2026 •

edited

Loading