Skip to content

SimpleRisk 20260820-001 Release - #140

Merged
WolfangAukang merged 24 commits into
updates.simplerisk.comfrom
updates-test.simplerisk.com
Aug 21, 2026
Merged

SimpleRisk 20260820-001 Release#140
WolfangAukang merged 24 commits into
updates.simplerisk.comfrom
updates-test.simplerisk.com

Conversation

@WolfangAukang

Copy link
Copy Markdown
Contributor

No description provided.

@WolfangAukang
WolfangAukang merged commit a657849 into updates.simplerisk.com Aug 21, 2026
1 check passed
jsokol added a commit that referenced this pull request Aug 22, 2026


#140 merged the updates-test.simplerisk.com branch into the prod feed, which
carried testing-channel truth into the production manifests. The VM hashes in
that merge are correct and are KEPT -- this reverts only the parts that describe
the prod channel.

What was wrong, and how each value was confirmed:

- 20260820-001 bundle_md5/bundle_sha256 pointed at the TESTING bundle
  (61c78cca...). The testing bundle for this version was rebuilt at 15:04 on
  2026-08-21 by the CHERRYPICK-ga-notes-testing merge, so it is different bytes
  from the GA bundle promoted at 14:41. Restored to 3e279416..., verified by
  downloading BOTH the prod S3 object and the simplerisk/code release asset --
  two independent artifacts that agree with each other.

- 20260519-001 bundle_md5/bundle_sha256 likewise. Restored to 7d7fb242...,
  verified by downloading the served prod S3 bundle.

- 20260519-001 next_release, and upgrade_path.xml, routed upgrades through
  20260709-001 and 20260811-001. Those are testing RCs that never shipped GA --
  simplerisk/code has no release for either, and 20260820-001 is the combined
  GA record for all three. Their bundles 403 on the prod channel, so a customer
  on 20260519-001 would have been sent to a bundle that is not there. Restored
  to the direct 20260519-001 -> 20260820-001 hop.

- The 20260811-001 / 20260709-001 release and extra_compatibility entries are
  removed for the same reason: they are not prod releases.

Caught by simplerisk/docker's image build, which verifies the bundle against
this feed and fails closed. Every docker master PR has been blocked since 20:49.

The prod feed has a single writer -- sync_code_repo.yml's update_feeds.sh, which
writes the real GA asset hashes. Merging the testing branch into it bypasses
that writer and silently replaces GA truth with RC truth.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.

2 participants