chore(deps): opencost, reloader and trivy-operator to current - #32
Merged
Conversation
Mirrors eks-gitops 46f9f8e. These three are dual-pinned, so mirror-check fails on either side moving alone. opencost 2.5.28 -> 2.5.29 reloader 2.2.14 -> 2.2.15 trivy-operator 0.34.0 -> 0.35.0 upstream.ref moves with them, from 614560a to 46f9f8e. That range also carries the operator chart's 0.6.3 -> 0.6.4 repoint, which kx does not follow and does not need to: it builds that chart from a sibling checkout, already declared as a gitops-only divergence. `mirror-check sync` re-pinned zero slices, which is the useful signal here — the versions written by hand already matched what eks-gitops pins, so the two sides agree by derivation rather than by assertion. Full check afterwards: 32 charts match, 12 declared divergences, 2 CRD installers answered. The render gate passes for all three slices, including the mount check the loki migration added, and the provenance and Renovate-coverage gates both stay green at 32 pins.
Running any gate script under scripts/ leaves a __pycache__ directory behind, and this repo did not ignore it. eks-gitops, landing-zone and eks-agent-platform all do. An untracked directory is not cosmetic here. Several checks in this org read `git status --porcelain` to decide whether a tree is clean before acting — landing-zone's e2e refuses to start against a dirty tree, and `gh pr create` warns on one — so running the repo's own verification makes the repo look modified to the next thing that asks. Surfaced by running the gates this branch's other commit reports on.
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.
Paired with eks-gitops#192 (merged as
46f9f8e). All three are dual-pinned, somirror-checkfails on either side moving alone.upstream.refmoves614560a→46f9f8e. That range also carries the operator chart's 0.6.3 → 0.6.4 repoint, which kx does not follow and does not need to — it builds that chart from a sibling checkout, already declared as agitops-onlydivergence.Verification
mirror-check syncre-pinned zero slices, which is the useful signal: the versions written by hand already matched what eks-gitops pins, so the two sides agree by derivation rather than by my assertion. Full check after:render-check.sh— OK for all three slices, including the per-container mount checkcheck-chart-deprecation.py— 32 pins, each with a provenance record, none deprecatedcheck-renovate-coverage.py— exit 0, all pins matched by a shipped regexUpstream-side verification (rendered old vs new against real values, plus a direct
crds/comparison for trivy-operator's appVersion minor) is in eks-gitops#192.