Repository navigation
fix(deps): adopt released Core v0.19.4 across host modules - #1125
Closed
antoinetoussaint-byte wants to merge 1 commit into
Closed
antoinetoussaint-byte wants to merge 1 commit into
antoinetoussaint-byte wants to merge 1 commit into
Conversation
6 tasks
Contributor
Author
|
Obsolete — main's host modules already moved past core v0.19.4 (core v0.19.6+ / sdk-go 0.4.x). |
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.
The five host services still require Core v0.19.3, whose pruned dependency graph can select kube-openapi incompatible with stable client-go. The root agent, tools and module-authority qualification also retain Core v0.18.0. This moves those eight direct requirements to released Core v0.19.4 and its required module selections. No production Go, generated contract, authority decision, transport, service-agent pin or package version changes.
This is an owner dependency fix: it reuses Core’s existing graph correction and issuer Authority.ReadBack. It adds no replacement, vendor patch, copied verifier or alternate endpoint/identity mechanism. Root AGENTS.md and module/AGENTS.md now describe the actual independent modules, both graph guard conditions and the already-selected SDK v0.4.0.
Of nine tracked Go modules, eight select Core v0.19.4. The unchanged source-read SDK selects v0.2.33 transitively through its existing SDK but compiles no Core package in its build/test graph. This is deliberately not an all-module or completed-release claim.
Validation on the frozen 18-file patch (SHA256 b650a391925e94647c5ab63623aac4fdf6fe8486e11f55f208698d2d6863c7e1):
Every local verifier used Go 1.27.2, OS-enforced nonlocal network denial, denied Docker/Nix broker sockets, offline package settings and readonly verification. Dependency acquisition was separate. This does not establish DB-backed accounts acceptance, full Codefly release gates, Linux service images, a new vulnerability audit, live Kubernetes behavior, deployment or published-artifact adoption.
Overlap inspected before draft creation: #1124 requires a newer Core API for accounts; #1120 requires a newer Core API in accounts/gateway. Their owners were notified; integration must preserve those API requirements and recheck the resulting graph, never downgrade them to this floor. Older #1076 also changes dependency files from its historical base; #1027 removes telemetry and touches the guide. None is folded into this snapshot. #1123’s independently reviewed refusal-audit repair is disjoint and not included here. If main changes, re-evaluate the integrated scope before delivery.
Refs #1082. Draft only; no merge, tag, release or deployment requested by this publication.