Skip to content

Update dependencies #1761

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

Merged
merged 1 commit into from
Jun 10, 2021
Merged

Update dependencies #1761

merged 1 commit into from
Jun 10, 2021

Conversation

jjlin
Copy link
Contributor

@jjlin jjlin commented Jun 9, 2021

Notably, update diesel to 1.4.7 and libsqlite3-sys to 0.22.2 to pick up
the fix for CVE-2021-20227 added in SQLite 3.34.1.

Notably, update `diesel` to 1.4.7 and `libsqlite3-sys` to 0.22.2 to pick up
the fix for CVE-2021-20227 added in SQLite 3.34.1.
@BlackDex
Copy link
Collaborator

BlackDex commented Jun 9, 2021

Isn't it maybe a good idea to update the rest of the packages also?
Like do an cargo update maybe and update all the other dependencies, maybe not handlebars right now, because that will take some other modifications i think.

@jjlin
Copy link
Contributor Author

jjlin commented Jun 9, 2021

I did run cargo update -- there are many other changes in Cargo.lock. I'm just calling out a notable change that would not have happened on its own with just cargo update.

@BlackDex
Copy link
Collaborator

BlackDex commented Jun 9, 2021

Isn't it then a good thing to also update the Cargo.toml to represent the same versions as are now in the Cargo.lock?

@jjlin
Copy link
Contributor Author

jjlin commented Jun 9, 2021

I wouldn't mind, but cargo update doesn't do that AFAIK (see e.g., rust-lang/rust#57443). I haven't looked into whether there are other tools that make that change in an automated way, but I'd rather not do it manually.

@dani-garcia
Copy link
Owner

I usually use cargo upgrade --dry-run (from cargo-edit) as an easy way to check for semver incompatible dependency updates, and for bumping the versions in the Cargo.toml. Not sure if it's good practice or not, simply something I've been doing myself

@dani-garcia dani-garcia merged commit cea7a30 into dani-garcia:main Jun 10, 2021
@BlackDex
Copy link
Collaborator

I usually use cargo upgrade --dry-run (from cargo-edit) as an easy way to check for semver incompatible dependency updates, and for bumping the versions in the Cargo.toml. Not sure if it's good practice or not, simply something I've been doing myself

I do the same indeed.

@jjlin
Copy link
Contributor Author

jjlin commented Jun 11, 2021

Ah, good to know. I'm personally okay with the default cargo update version selection behavior, and it looks like following that with cargo upgrade --to-lockfile would then update Cargo.toml to match what was updated in Cargo.lock.

Running cargo upgrade alone seems to actually downgrade a bunch of crates, presumably as a consequence of rocket v0.5.0-dev -> v0.4.7? Even adding --allow-prerelease doesn't seem to change this. So how are you guys getting this to work?

$ cargo upgrade --dry-run
    Updating 'https://github.com/rust-lang/crates.io-index' index
Starting dry run. Changes will not be saved.
vaultwarden:
    Upgrading lettre v0.10.0-rc.1 -> v0.10.0-alpha.5
    Upgrading regex v1.5.4 -> v1.4.3
    Upgrading yubico v0.10.0 -> v0.9.2
    Upgrading openssl v0.10.34 -> v0.10.32
    Upgrading cookie_store v0.15.0 -> v0.12.0
    Upgrading diesel v1.4.7 -> v1.4.5
    Upgrading handlebars v3.5.5 -> v3.5.2
    Upgrading idna v0.2.3 -> v0.2.1
    Upgrading syslog v4.0.1 -> v5.0.0
    Upgrading libsqlite3-sys v0.22.2 -> v0.20.1
    Upgrading serde v1.0.126 -> v1.0.123
    Upgrading rocket_contrib v0.5.0-dev -> v0.4.7
    Upgrading pico-args v0.4.1 -> v0.4.0
    Upgrading backtrace v0.3.59 -> v0.3.56
    Upgrading time v0.2.26 -> v0.2.25
    Upgrading reqwest v0.11.3 -> v0.11.0
    Upgrading tracing v0.1.26 -> v0.1.23
    Upgrading cookie v0.15.0 -> v0.14.3
    Upgrading paste v1.0.5 -> v1.0.4
    Upgrading url v2.2.2 -> v2.2.0
    Upgrading serde_json v1.0.64 -> v1.0.62
    Upgrading once_cell v1.7.2 -> v1.5.2
    Upgrading rocket v0.5.0-dev -> v0.4.7

@jjlin jjlin deleted the deps branch June 16, 2021 09:50
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.

3 participants