-
Notifications
You must be signed in to change notification settings - Fork 268
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bump versions and simplify dependencies #2294
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
At least in the workspace `Cargo.toml`, crates that should only ever be in `dev-dependencies` can have a `path` and no `version`. This makes referencing them easier, but I'd be fine with crates taking a local `path` as well.
hallipr
reviewed
Mar 6, 2025
What's breaking the MSRV builds is likely a change to rustc/cargo that check crates'
Running |
LarryOsterman
approved these changes
Mar 6, 2025
Only in the `rust - pullrequest` pipelines was it seemingly ignoring our `Cargo.lock` file and using newer versions of these crates that upgraded their MSRV. This explicitly adds the versions we had in our `Cargo.lock` file to see if that passes the PR builds. We may still want to pass `--locked` in both PR and CI builds; however, oddly, the CI builds are passing even after a manual run I just kicked off an hour or so ago.
The Cargo.lock file wasn't committed; still, don't know why it just started failing in PR but still not in CI builds.
We'll decide as part of Azure#2300. Kept it in `package` and `publish` to make sure we ship what we intended.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Azure.Core
The azure_core crate
Azure.Identity
The azure_identity crate
Cosmos
The azure_cosmos crate
Storage
Storage Service (Queues, Blobs, Files)
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.
At least in the workspace
Cargo.toml
, crates that should only ever be indev-dependencies
can have apath
and noversion
. This makes referencing them easier, but I'd be fine with crates taking a localpath
as well.