Repository navigation
chore(deps): update mysql_common digest to 374c9d5 - #11881
renovate[bot] wants to merge 1 commit into
Conversation
t8y2
left a comment
There was a problem hiding this comment.
Thanks for the PR, but this one can't land as-is — closing for now, happy to re-land it once the pins can move together.
What breaks: the dev-dependency bump moves mysql_common from fork rev 47740d8 (v0.38.0) to 374c9d5 (v0.38.2) — a version bump, not a same-version digest refresh. Meanwhile mysql_async is pinned via [patch.crates-io] to the zipg/mysql_async fork, which itself pins mysql_common rev 47740d8 (0.38.0). After this PR the graph contains two copies of mysql_common, and the test code's 0.38.2 types no longer match mysql_async's 0.38.0 types — rust-test (workspace) and rust-fmt-clippy fail with E0277 (Arc<[mysql_common::packets::Column]>: From<Vec<mysql_async::Column>> unsatisfied) and E0308 mismatches.
How to unblock: the two pins must move in lockstep — either bump the mysql_async fork pin to a rev that uses mysql_common 374c9d5/0.38.2, or wait for upstream blackbeam/rust_mysql_common#186 to publish 0.38.2 and switch the whole graph to the crates.io release. Renovate will recreate this PR automatically once the dev-dep and the mysql_async fork pin agree.
Renovate Ignore NotificationBecause you closed this PR without merging, Renovate will ignore this update. You will not get PRs for the If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR. |
This PR contains the following updates:
47740d8→374c9d5Configuration
📅 Schedule: (in timezone Asia/Shanghai)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.