Skip to content
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

Merged

Conversation

jcgruenhage
Copy link
Contributor

[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":

taskwarrior on  get-rid-of-old-ring via △ v3.30.2 via 🦀 v1.80.1 
❯ cargo update google-cloud-auth
    Updating crates.io index
     Locking 3 packages to latest compatible versions
    Removing base64 v0.13.1
    Updating google-cloud-auth v0.13.0 -> v0.13.2 (latest: v0.16.0)
    Updating jsonwebtoken v8.3.0 -> v9.3.0
    Updating pem v1.1.1 -> v3.0.4
    Removing ring v0.16.20
    Removing spin v0.5.2
    Removing untrusted v0.7.1
    Removing winapi v0.3.9
    Removing winapi-i686-pc-windows-gnu v0.4.0
    Removing winapi-x86_64-pc-windows-gnu v0.4.0
note: pass `--verbose` to see 90 unchanged dependencies behind latest

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 broad cargo 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 run cargo 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.

[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.
@jcgruenhage
Copy link
Contributor Author

Ah, oh, I see. MSRV is 1.70.0 which is not supported for these updated deps anymore...

@djmitche
Copy link
Collaborator

djmitche commented Aug 9, 2024

I'm happy to bump the MSRV, given a reason. What version is required?

@jcgruenhage
Copy link
Contributor Author

It would be 1.73.0

@djmitche
Copy link
Collaborator

djmitche commented Aug 9, 2024

That sounds fine. cargo xtask msrv should be able to update that.

@jcgruenhage
Copy link
Contributor Author

jcgruenhage commented Aug 9, 2024

I'll package cargo xtask for chimera linux later then and go ahead and do that :D

@djmitche
Copy link
Collaborator

djmitche commented Aug 9, 2024

It should just run within the repo where you're making the PR

@jcgruenhage
Copy link
Contributor Author

Indeed, somehow I don't need cargo-xtask installed.

Still, it doesn't do it:

    Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.12s
     Running `target/debug/xtask msrv`
Error: xtask: unknown xtask

@jcgruenhage
Copy link
Contributor Author

My short dig seems to point to the xtask being lost when taskchampion got moved out of the taskwarrior repo?

@djmitche
Copy link
Collaborator

djmitche commented Aug 9, 2024

#3592

@djmitche djmitche merged commit 0f96fd3 into GothenburgBitFactory:develop Aug 10, 2024
15 checks passed
@jcgruenhage jcgruenhage deleted the get-rid-of-old-ring branch August 12, 2024 09:22
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