Repository navigation
fix(ci): align example and capability fixture dependency metadata - #1053
Merged
Merged
Conversation
intel352
changed the title
⏱ Benchmark Results✅ No significant performance regressions detected. benchstat comparison (baseline → PR)
|
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.
Align example and capability-fixture module metadata after the dependency bumps merged into main. Root miniredis is now v2.39.0, while example/go.sum retained v2.38.0. The eight capability fixtures also retained older x/net, genproto/rpc and protobuf requirements; native Go 1.26.5
go build -mod=readonlyrejected all eight before capability assertions could run.This changes 17 metadata files: example/go.sum and go.mod/go.sum in the eight existing capability fixtures. The example checksum replacements and every added fixture checksum already exist in current root go.sum. Each fixture updates exactly three existing indirect versions to current root requirements; its other 32 indirect entries, direct Workflow requirement, module identity, Go 1.26.5 directive, local replacement and application/test source remain fixed. Existing checksum records remain retained. The readonly build helper, root dependencies, compiler floor, policy guards and locked migration plan remain unchanged. All 3,510 other tracked files are conserved.
Validation: independent source reviews report zero findings; complete before/after catalogs, current-root checksum joins and
git diff --checkpass. The previous exact-head CI proves example tidy/build/lint/config success and identifies the eight real readonly fixture failures. Fresh Linux CI on the updated head must prove the fixture builds and whole root Go tests; declaration alignment alone does not prove the selected graph or an empty fixture tidy diff. Prior attempts remain recorded.Task 21's five-file policy adoption stays separately scoped in #1052, whose genuine full harness and canonical guard path pass. This prerequisite retains main's known EVENT_NAME fixture failure until that adoption; no fixture waiver, merge/release authority or Compute deployment acceptance is claimed.