Bump the cargo group across 1 directory with 4 updates#2270
Bump the cargo group across 1 directory with 4 updates#2270dependabot[bot] wants to merge 1 commit intomainfrom
Conversation
Bumps the cargo group with 4 updates in the / directory: [tracing-forest](https://github.com/QnnOkabayashi/tracing-forest), [zip](https://github.com/zip-rs/zip2), [http](https://github.com/hyperium/http) and [tower-http](https://github.com/tower-rs/tower-http). Updates `tracing-forest` from 0.1.6 to 0.2.0 - [Commits](https://github.com/QnnOkabayashi/tracing-forest/commits) Updates `zip` from 5.1.1 to 6.0.0 - [Release notes](https://github.com/zip-rs/zip2/releases) - [Changelog](https://github.com/zip-rs/zip2/blob/master/CHANGELOG.md) - [Commits](zip-rs/zip2@v5.1.1...v6.0.0) Updates `http` from 1.3.1 to 1.4.0 - [Release notes](https://github.com/hyperium/http/releases) - [Changelog](https://github.com/hyperium/http/blob/master/CHANGELOG.md) - [Commits](hyperium/http@v1.3.1...v1.4.0) Updates `tower-http` from 0.6.6 to 0.6.7 - [Release notes](https://github.com/tower-rs/tower-http/releases) - [Commits](tower-rs/tower-http@tower-http-0.6.6...tower-http-0.6.7) --- updated-dependencies: - dependency-name: tracing-forest dependency-version: 0.2.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: cargo - dependency-name: zip dependency-version: 6.0.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: cargo - dependency-name: http dependency-version: 1.4.0 dependency-type: indirect update-type: version-update:semver-minor dependency-group: cargo - dependency-name: tower-http dependency-version: 0.6.7 dependency-type: indirect update-type: version-update:semver-patch dependency-group: cargo ... Signed-off-by: dependabot[bot] <support@github.com>
|
I am leaving this to you Eliah Kagan (@EliahKagan) to look at, mainly because it says that it updates more than it actually does. What it does is fine, I think, it's just strange it doesn't seem to 'know' what it's doing. Otherwise I think the PR can be merged. |
There was a problem hiding this comment.
I think these changes are okay, though I'll have Dependabot recreate the PR to see if anything more is available since it was opened, and also to see if Dependabot manages to describe its changes more accurately.
It's slightly convenient that it's not really updating tracing-forest, since it does't seem to have any release notes, changelogs, version tags, or informaton about breaking changes in commit messages, so I don't know where to look to review the effect of breaking changes. But one can find the relevant range of commits, so there is this full diff.
One occurrence of tracing-forest is in the top-level Cargo.toml. This supports the tracing feature of gitoxide-core. It is at 1.5, with the associated resolved version in Cargo.lock consistent with it, at 1.6. Dependabot claims it's upgrading tracing-forest from 1.6 to 2.0, which I think it wants to do (or cargo recommends it to do) because 2.0 is already separately listed there. But it can't just upgrade that, because 2.0 doesn't satisfy 1.5 in Cargo.toml. Why it's not trying to upgrade 1.5 to 2.0--or even all the way to 3.0, which is the actual current version--I don't know. What version should we be using?
I think that kind of thing happens fairly often with Dependabot on this repository. This is one of a few reasons I'd be interested to try out Renovate as an alternative here, though I can't be sure that it would work better.
The other thing we're seeing here is that it wants to downgrade resolved versions of windows-sys in Cargo.toml. I believe that always happens anytime cargo update has been run with the effect of upgrading windows-sys or various closely related packages; for some reason, Dependabot or whatever version and configuration of cargo it is using regards the earlier versions to be preferable. Maybe this is so fewer separate versions can be used, I don't know. But it's a long-standing difference between the effect of Dependabot and the effect of running cargo update locally (even when just trying to update a single direct dependency).
See #1938 comments for an example with windows-targets. That's the best I could find. Incidentally, I find searching for information in GitHub comments discussions extremely hard lately. I think in principle GitHub includes this in search results, but in practice that seems often not to be the case. Is there some way to export the entire history of all public issues and PRs in a repository, along with all their comments, both regular and review comments, so that I can search them locally? (This would be useful for other reasons too: preserving valuable knowledge, providing context to a locally runnng LLM, etc.)
|
Dependabot (@dependabot) recreate |
|
Looks like these dependencies are updatable in another way, so this is no longer needed. |
Bumps the cargo group with 4 updates in the / directory: tracing-forest, zip, http and tower-http.
Updates
tracing-forestfrom 0.1.6 to 0.2.0Commits
Updates
zipfrom 5.1.1 to 6.0.0Release notes
Sourced from zip's releases.
Changelog
Sourced from zip's changelog.
Commits
abfc23dfeat: Upgrade [Extended]FileOptions::add_extra_data() data from Box<[u8]> to ...eb1b586docs: Update zip_writer documentation example (#431)26e6e08feat: Add by_index_with_options() for ignoring encryption (#439)165415dchore(deps): update nt-time requirement from 0.10.6 to 0.12.1 (#429)1d5d4edchore(deps): update lzma-rust2 requirement from 0.13 to 0.14 (#432)72cce40chore(deps): update nt-time requirement from 0.10.6 to 0.12.1 (#428)2ef4d3echore(deps): update nt-time requirement from 0.10.6 to 0.12.1 (#427)9cf28cbtest(ci): Fix:renamecan't be skipped5987cddtest(ci): Fix: need recursive rename74f8a3ctest(ci): Need to rename more files during fuzz runsUpdates
httpfrom 1.3.1 to 1.4.0Release notes
Sourced from http's releases.
Changelog
Sourced from http's changelog.
Commits
b9625d8v1.4.050b009crefactor(header): inline FNV hasher to reduce dependencies (#796)b370d36feat(uri): makeAuthority/PathAndQuery::from_staticconst (#786)0d74251chore(ci): update to actions/checkout@v5 (#800)a760767docs: remove unnecessary extern crate sentence (#799)fb1d457refactor(header): use better panic message in const HeaderName and HeaderValu...20dbd6efeat(status): Add 103 EARLY_HINTS status code (#758)e7a7337chore: bump MSRV to 1.571888e28tests: downgrade rand back to 0.8 for now918bbc3chore: minor improvement for docs (#790)Updates
tower-httpfrom 0.6.6 to 0.6.7Release notes
Sourced from tower-http's releases.
Commits
3bf1ba7v0.6.7723ca9afix(decompression): Suppress EOF errors caused by decompressing empty body (#...8ab9f82chore(ci): use newer cargo-public-api-crates job (#619)7cfdf76doc: Replace doc_auto_cfg with doc_cfg (#609)50beeafAdd support for custom status code in TimeoutLayer (#599)35740dedeps: Remove unnecessary dev-dependencies (#606)a7eefaeci: Re-enable ci on default branch (#605)12a5b33tests: Update to brotli 8 (#603)0195198ci: Update to actions/checkout v5 (#604)c757491examples: Update to axum 0.8 (#602)Dependabot 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