Repository navigation
chore(deps): lock file maintenance - #115
Conversation
fdd3e15 to
5f46df2
Compare
5f46df2 to
170bd07
Compare
![forkline[bot]](https://github.githubassets.com/images/gravatars/gravatar-user-420.png){kind=avatar}
The lock file maintenance introduced k8s-openapi 0.29.0 as a second version alongside 0.28.0. This caused a build failure because k8s-openapi 0.29.0 requires a v1_* feature to be enabled, but none was enabled for it. The issue occurred because kube-leader-election 0.44.0 has a dependency on k8s-openapi >=0.27, which allowed cargo to resolve it to 0.29.0. However, kube 4.2.0 requires k8s-openapi ^0.28.0, creating a version mismatch. This fix removes k8s-openapi 0.29.0 from the lock file and consolidates all dependencies to use k8s-openapi 0.28.0 with the v1_35 feature enabled. Fixes CI failure: None of the v1_* features are enabled on the k8s-openapi crate.
|
✅ Fix pushed: SummarySuccessfully fixed the CI failure on PR #115. Root Cause: The lock file maintenance introduced The Fix: Removed Changes:
The fix has been committed and pushed to the |
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
This PR contains the following updates:
🔧 This Pull Request updates lock files to use the latest dependency versions.
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.