build: bump the context pin to current main - #476
Merged
Conversation
osvbng builds the pinned context, so three merged docs changes were invisible to a session working from this checkout: the corrected CI and FRR notes, the CGNAT audit queued as todo item 17, and the worker-model question opened as a design note with ADR 0006's conformance gaps recorded. Docs only, and the vpp pin does not move: it already sits at that repo's main.
BSpendlove
temporarily deployed
to
integration-rig
August 20, 2026 15:00 — with
GitHub Actions
Inactive
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.
osvbng builds the pinned context, not whatever that repo's main happens to be, so three merged docs changes are currently invisible to anyone working from this checkout.
What the pin picks up:
design/verification.mdno longer says the suites "run locally, and only locally" or that CI gates a PR on build and unit tests alone. It describes the three tiers that have been running since 17 August, and keeps the parts still true: a green PR run coverstests/ci-suites.txtrather than the catalog, and the hand-copied dataplane drop still decides what a pass proves.design/routing-frr-bridge.mdno longer namesConfigureBGPstyle calls as the configuration face. Those were removed so a routing instance change survives an osvbngd restart; declared config renderstemplates/frr/and applies it throughfrr-reload.py, and only the advertisement calls still drive vtysh directly.design/cgnat-worker-model.mdopens the worker-model question rather than settling it, and ADR 0006 gains a dated conformance section recording that it promises per-VRF allocator identity the code does not provide and leans on a deterministic mode that never programs a mapping.The vpp pin does not move: it already sits at that repo's main (
fb3580a4).Verification
Docs-only submodule bump, produced by
make bump-submodulesso the pins are staged the documented way. The diff is one line, the context gitlink, andgit statusshowed nothing else staged. Checked that no Go source, workflow or Makefile in this repo references acontext/design/orcontext/decisions/path, so nothing can dangle; the three merges only add files.Not verified: nothing was built or run, because no code or build input changes.