-
-
Notifications
You must be signed in to change notification settings - Fork 312
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
Update google-cloud-auth to drop [email protected] #3591
Update google-cloud-auth to drop [email protected] #3591
Conversation
[email protected] doesn't build on ppc and risc-v, and updating google-cloud-auth pulls in a newer version of jsonwebtoken, which in turn depends on a newer version of ring that we depend on already either way.
Ah, oh, I see. MSRV is 1.70.0 which is not supported for these updated deps anymore... |
I'm happy to bump the MSRV, given a reason. What version is required? |
It would be 1.73.0 |
That sounds fine. |
I'll package cargo xtask for chimera linux later then and go ahead and do that :D |
It should just run within the repo where you're making the PR |
Indeed, somehow I don't need cargo-xtask installed. Still, it doesn't do it:
|
My short dig seems to point to the xtask being lost when taskchampion got moved out of the taskwarrior repo? |
[email protected] doesn't build on ppc and risc-v, and updating
google-cloud-auth pulls in a newer version of jsonwebtoken,
which in turn depends on a newer version of ring that we depend on
already either way.
Readable "diff":
Chimera Linux has been carrying a patch that contained the changes made by
cargo update
for a while. I've reduced that patch because I'm not sure whether a broadcargo update
is even wanted.In my opinion it would make sense to bump all dependencies to their latest compatible versions before each release using
cargo update
, and maybe even to runcargo upgrade --incompatible
every now and then to get the latest and greatest. That last one some times causes more work though, as it also includes breaking changes of dependencies.