Repository navigation
docs(risk-register): C-44 — defer pipeline-core 3.0.0 bump until cross-repo development is stable - #65
Merged
Conversation
…ntil cross-repo development is stable Records the standing constraint that the views-pipeline-core 2.x->3.x bump must not land until 3.0.0 is on PyPI AND the platform runs smoothly on development across all repos. development is green on the reproducible 2.3.0 pin; the unreleased-3.x-via-git-branch change is preserved on backup/pipeline-core-3.0.0-git-source and becomes a trivial reproducible pin once both gates clear. Tier 3. Header 43/23/20 -> 44/24/20. Cross-refs C-40, C-07, C-09. Co-Authored-By: Claude Opus 4.8 <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
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.
Registers C-44 (Tier 3): the views-pipeline-core 2.x→3.x bump must not land until 3.0.0 is on PyPI and the platform runs smoothly on
developmentacross all consumer repos.Context
developmentpinsviews-pipeline-core = ">=2.1.3,<3.0.0";poetry.lockresolves 2.3.0 (reproducible PyPI wheel); the merged input-integrity sprint (feat(delivery): FAO input-integrity invariants S0–S6 (#51) #64) is CI-green against it.78d238e) repoints the dep to pipeline-core's moving gitdevelopmentbranch — deliberately not landed: non-reproducible (moving branch), an unexercised major-version switch, and needs a full re-lock.backup/pipeline-core-3.0.0-git-source; it becomes a trivial reproducible pin once 3.0.0 ships and the cross-repo gate clears.Register-only change (no code). Cross-refs C-40, C-07, C-09.
🤖 Generated with Claude Code