Uh oh!
There was an error while loading. Please reload this page.
move binary dependency management to bingo - #471
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@## master #471 +/- ##
==========================================
+ Coverage 37.78% 37.86% +0.08%
==========================================
Files 57 57 Lines 4557 4563 +6 ==========================================
+ Hits 1722 1728 +6
Misses 2678 2678 Partials 157 157 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Signed-off-by: grokspawn <jordan@nimblewidget.com>
5186aea to
21782a2CompareUh oh!
There was an error while loading. Please reload this page.
Signed-off-by: grokspawn <jordan@nimblewidget.com>
grokspawn
commented
Jan 29, 2026
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: grokspawn, rashmigottipati The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
0f51e11
into
operator-framework:masterUh oh!
There was an error while loading. Please reload this page.
move the retrieval of binaries to bingo, because otherwise there is no version comparison here, and since the acquisition makes no version comparison, it's trivial to see version drift between the upstream and users' local environments, and there's no check to prevent this. Instead, a user would literally have to identify that some of the generated artifacts from
make manifestsshouldn't have been generated.This new approach will make the version checks explicit, tied to go version dependency management, and independent of user environments.