Skip to content

Conversation

@spikespaz
Copy link
Contributor

I noticed when trying to use [patch.crates-io] for local development that dependency version resolution was a bit broken, even when versions should be compatible.

Simply running cargo update evidently improves the situation.

@spikespaz spikespaz force-pushed the u/jacob/run-cargo-update branch 2 times, most recently from 960bfee to 2fdfafd Compare October 13, 2025 17:55
@spikespaz
Copy link
Contributor Author

I don't know how to fix WASM related problems

@ahl
Copy link
Collaborator

ahl commented Oct 13, 2025

I don't know how to fix WASM related problems

I'm on it.

spikespaz and others added 3 commits October 13, 2025 14:45
I noticed when trying to use `[patch.crates-io]` for local development
that dependency version resolution was a bit broken, even when versions
should be compatible.

Simply running `cargo update` evidently improves the situation.
@spikespaz spikespaz force-pushed the u/jacob/run-cargo-update branch from 65cf3f0 to ce9b0a1 Compare October 13, 2025 21:47
@spikespaz
Copy link
Contributor Author

I'm doing that because merge commits obfuscate the real changes. Forgive me for the noise.

@ahl
Copy link
Collaborator

ahl commented Oct 13, 2025

I'm doing that because merge commits obfuscate the real changes. Forgive me for the noise.

No problem; just more work for me.

@spikespaz
Copy link
Contributor Author

spikespaz commented Oct 13, 2025

git rebase origin/main is arguably less work than managing a nonlinear history.

@ahl ahl merged commit 1507827 into oxidecomputer:main Oct 14, 2025
9 checks passed
abus-sh pushed a commit to abus-sh/progenitor that referenced this pull request Dec 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants