Closed ca-scribner closed 3 months ago
Thank you for reporting us your feedback!
The internal ticket has been created: https://warthogs.atlassian.net/browse/KF-5567.
This message was autogenerated
All PRs are now merged, we can close this issue.
Context
There have been a number of bugfixes and other changes to
ops
recently. As part of the Charmed Kubeflow 1.9 release, we should bumpops
to the most recent working version at time of release.While doing this task, it likely makes sense to bump other packages as well. For example, this task could be completed by ensuring
ops
is unpinned inrequirements.in
and then merging the most recent Renovate PR for every repoAs part of this task, should we pin
ops<3
or leave it unpinned?What needs to get done
ops
version in all charmed kubeflow charms is bumped to the most recent working version (ideally the most recent version, but if there's a blocker we can pin it lower and file issues)Definition of Done
see above