Skip to content

docs: record upstream production upgrade and recovery - #11

Merged
harley merged 2 commits into
mainfrom
docs/upstream-upgrade-receipt
Sep 24, 2026
Merged

harley merged 2 commits into
mainfrom
docs/upstream-upgrade-receipt

Conversation

@harley

@harley harley commented Sep 24, 2026

Copy link
Copy Markdown

What does this PR do?

Record the verified 24 September production upgrade from v0.4.43 plus handoff backport to release 355006f, based on upstream e909e9c. Make the runbook current and link it from agent instructions.

Type of Change

  • Documentation update

Changes Made

Record image identities, CI, migration rehearsal, backups, cutover time, preserved data/configuration, UI/runtime/Lark connectivity and recovery limits. Explain private image transfer and Docker 29 manifest verification.

How to Test

Checked against production and recorded receipts. Whitespace check passed. Code tests were not rerun for this documentation-only change; release CI passed as linked in the receipt.

Risks

Rollback across 77 migrations requires a pre-upgrade database restore and reconciliation of later writes. Protected backups remain host-side; no credentials, dumps or internal screenshots are committed. No new inference or outbound-message test is claimed.

AI Disclosure

Codex prepared this record during the user-authorized upgrade.

@amazon-q-developer amazon-q-developer Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This PR documents a completed production upgrade from v0.4.43 to release 355006f. All changes are documentation records of verification steps, image identities, cutover procedures, and recovery requirements. No code defects found that block merge.


You can now have the agent implement changes and create commits directly on your pull request's source branch. Simply comment with /q followed by your request in natural language to ask the agent to make changes.

@harley
harley merged commit 572ee4c into main Sep 24, 2026
17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant