Skip to content

GAM 7.48.30, independent of GamGUI's pin - #76

Merged
goetchstone merged 1 commit into
mainfrom
gam/7.48.30
Oct 17, 2026
Merged

goetchstone merged 1 commit into
mainfrom
gam/7.48.30

Conversation

@goetchstone

Copy link
Copy Markdown
Owner

Bumps the vendored GAM from 7.48.28 to 7.48.30 with scripts/bump_gam.py: GitHub's build attestation verified, the SHA-256 pinned, GAM re-vendored, and the catalog and parity fixtures regenerated.

  • No behaviour change for this app: 7.48.29 handles one label-delete error; 7.48.30 fixes GAM's own version check (version checkrc is not showing the Version Check section in 7.48.29 (regression of #1897) GAM-team/GAM#2010), which this app never runs. GamCommands.txt is unchanged, so every cited grammar line holds.
  • GamGUI no longer holds this pin back (operator's call): gen_fixtures.py stamped the fixtures with GamGUI's EXPECTED_GAM_VERSION, which FixtureTests holds to our pin, so a bump here waited for GamGUI's. It now stamps the build the oracle actually ran (Vendor/gam7/VERSION, as the catalog already did). GamGUI still supplies the builders: the fixtures keep gamgui_commit 2f35285 (its 7.48.28), while gam_version says 7.48.30.
  • The GAM runbook, CLAUDE.md's pin line and the checksums comment say so.

Package suite green locally (653) and the app builds; CI's check_app.sh checks the embedded GAM runs at the pin. GamGUI's own bump (goetchstone/gamgui#53) is now separate.

🤖 Generated with Claude Code

bump_gam.py: build attestation verified, the SHA-256 pinned, GAM
re-vendored, catalog and fixtures regenerated against the same GamGUI
commit (2f35285); GamCommands.txt unchanged. gen_fixtures.py now stamps
the vendored build's version instead of GamGUI's EXPECTED_GAM_VERSION,
so a bump here no longer waits for GamGUI's.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@goetchstone
goetchstone merged commit c3e28b7 into main Oct 17, 2026
7 checks passed
@goetchstone
goetchstone deleted the gam/7.48.30 branch October 19, 2026 17:57
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