Bump the rust-dependencies group with 2 updates #52
Conversation
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
Bumps the rust-dependencies group with 2 updates: [thiserror](https://github.com/dtolnay/thiserror) and [anyhow](https://github.com/dtolnay/anyhow). Updates `thiserror` from 2.0.11 to 2.0.12 - [Release notes](https://github.com/dtolnay/thiserror/releases) - [Commits](dtolnay/thiserror@2.0.11...2.0.12) Updates `anyhow` from 1.0.96 to 1.0.97 - [Release notes](https://github.com/dtolnay/anyhow/releases) - [Commits](dtolnay/anyhow@1.0.96...1.0.97) --- updated-dependencies: - dependency-name: thiserror dependency-type: direct:production update-type: version-update:semver-patch dependency-group: rust-dependencies - dependency-name: anyhow dependency-type: direct:production update-type: version-update:semver-patch dependency-group: rust-dependencies ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
added
dependencies
| @@ -12,7 +12,7 @@ keywords.workspace = true | |||
| categories = ["command-line-utilities"] | |||
|
|
|||
| [dependencies] | |||
| anyhow = "1.0.96" | |||
| anyhow = "1.0.97" | |||
There was a problem hiding this comment.
Why would you do this? Does wl-clipboard-rs somehow hard-require some changes made in a patch release? Nor am I seeing this PR changing anything in the code that would introduce such a requirement?
There was a problem hiding this comment.
When I test the project before releasing, cargo will resolve the latest dependency versions. Therefore, I make my Cargo.toml reflect the versions that I tested against.
There was a problem hiding this comment.
- What you're describing is
Cargo.lock(also updated in this PR), whereasCargo.tomllists version requirements. See the docs. - If anything, the version you have tested against is 1.0.96 (or an older one), not 1.0.97 as bumped here.
There was a problem hiding this comment.
I primarily test right before tagging a new release. I also bump all dependencies before tagging a new release and testing it. However, it's easier to catch regressions when bumping versions one by one like this as they come out rather than all at once before release, because I am running the git code on my system, so there's more of a chance of me or someone else stumbling into a regression.
If I understand right, you want me to not bump at all, but I'm always bumping for the release, and given that, it's better to bump right away than wait until the release day.
Bumps the rust-dependencies group with 2 updates: thiserror and anyhow.
Updates
thiserrorfrom 2.0.11 to 2.0.12Release notes
Sourced from thiserror's releases.
Commits
95a5126Release 2.0.1276490f7Merge pull request #413 from dtolnay/elidablelifetime9f27b76Ignore elidable_lifetime_names pedantic clippy lintdaf2a6fResolve some elidable_lifetime_names pedantic clippy lint5f07160Point standard library links to stable6706a51Convert html links to intra-doc links2706873More precise gitignore patterns70bc20dRemove **/*.rs.bk from project-specific gitignoreUpdates
anyhowfrom 1.0.96 to 1.0.97Release notes
Sourced from anyhow's releases.
Commits
bfb89efRelease 1.0.97c7fca9bIgnore elidable_lifetime_names pedantic clippy lint427c0bbPoint standard library links to stableDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions