Repository navigation
Adopt the v5.1.0 GNN upstream pin - #24
Merged
Merged
Conversation
Move gnn/upstream.json from v5.0.3 (8f293d9b) to v5.1.0 (75c834bd8519dc7b5adc4d24f16bf393cfd1ecdf) and keep the duplicated pin references in step: gnn/README.md, .github/GNN.md, docs/gates.md, the CANONICAL_PIN record in tests/test_gnn_conformance.py, and the README.md GNN documentation links, which now resolve at the v5.1.0 tag. Close asf-gnn-upstream-5-1-adoption in tasks.yaml and regenerate TODO.md with scripts/validate_roadmap.py --write-todo. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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.
Summary
gnn/upstream.jsonfromv5.0.3(8f293d9ba810e6eda5c09842d9c7ed9ffa5f92c1) tov5.1.0(75c834bd8519dc7b5adc4d24f16bf393cfd1ecdf, recorded 2026-11-16), matching the estate importer cutover.gnn/README.md,.github/GNN.md,docs/gates.md, and theCANONICAL_PINrecord intests/test_gnn_conformance.py.v5.1.0tag. Each path was checked to exist at75c834bd.asf-gnn-upstream-5-1-adoptionintasks.yamland regeneratesTODO.mdanddocs/todo/withscripts/validate_roadmap.py --write-todo.The scratch-checkout fixture in
tests/test_gnn_conformance.pybuilds its own stubv5.0.3tag and never reads the real pin, so it is left unchanged.Verification
The required
gnn conformance (local)check runs in GitVault's governed offline test runner against this exact head:uv sync --frozen --check --offline,scripts/validate_gnn_spec.py, andtests/test_gnn_conformance.pywith zero skips, using a v5.1.0 GNN checkout and a Python 3.12 parser environment. The standard gates (pytest with coverage ≥90, ruff check and format, mypy) also run offline. The local status is posted through GitVault once those pass.Overlap
Open PR #23 also edits
README.mdanddocs/gates.md(andsrc/gnn_conformance.py, which this PR does not touch). This PR's hunks are limited to the pin lines and the GNN doc links, so whichever lands second may need a trivial rebase.🤖 Generated with Claude Code