GAM 7.48.00 (automated bump) - #14
Open
goetchstone wants to merge 1 commit into
Open
Conversation
Asset attested (gh attestation verify --repo GAM-team/GAM), pinned, vendored, catalog regenerated, mock + CLAUDE.md counts refreshed by scripts/bump_gam.py. ✅ offline suite green
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Automated bump of the vendored GAM, 7.47.02 → 7.48.00, produced by
scripts/bump_gam.pyin the weekly GAM release watch run.GAM-team/GAMbefore the pin was written.Opened by hand because the scheduled workflow could not: Settings → Actions → General → "Allow GitHub Actions to create and approve pull requests" is off, so the bot's
gh pr createis blocked by policy (the branch pushed fine). The branch is a clean descendant ofmain— only the 7 bump files differ.Before merge (human): skim GamUpdate.txt for 7.47.03→7.48.00, and run
scripts/acceptance.pyagainst a real tenant — CI cannot (it is the only true output-shape check). If the suite is ever red, the contract test likely caught a renamed/removed command we use.