Make 0.4.1-rc2 due to Cargo.lock issue post-merge for rc1 #391
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@mattjperez and @gvaradarajan - Sorry, we had a race condition on -rc1. I had to merge above #386, but that had a stale reference to 0.4.0 in the lock file:
So we need an -rc2, and this is that change, along with a run of
cargo update
to make sure that we have all dependencies correct.Meanwhile, I noticed that we have a
Cargo.lock
in the project template. @mattjperez and I discussed, and this doesn't make sense to me. We shouldn't be pinning the versions of things in a generated project - that's up to the project maintainer to manage theirCargo.lock
, and we aren't well positioned to create a good one for them. The one in the project template was also stale, referring to Micro-RDK 0.3.3: https://github.com/viamrobotics/micro-rdk/blob/main/templates/project/Cargo.lock#L1414.I've gone ahead and removed it here.