You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Allow using race module using just portable_atomic, without critical_section and provide
better error messages on targets without atomic CAS instruction, #265.
util: Removed deprecated ServiceExt::ready_and method and ReadyAnd
future (#652)
retry: Breaking Changeretry::Policy::retry now accepts &mut Req and &mut Res instead of the previous mutable versions. This
increases the flexibility of the retry policy. To update, update your method signature to include mut for both parameters. (#584)
retry: Breaking Change Change Policy to accept &mut self (#681)
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually
The artifact failure details are included below:
File name: Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path examples/tower_client/Cargo.toml --package [email protected] --precise 0.6.1
error: package ID specification `[email protected]` did not match any packages
Did you mean one of these?
[email protected]
could we use commands to circumvent the lack of cargoUpdate or cargoFetch and tasks only being supported on self-hosted instances
I don't think so. Renovate fails before - when updating a dependency. In this case, we depend on tower 0.5.0, but axum depends on tower 0.4.3. Axum has updated their tower to the latest 0.x since, but renovate doesn't pick that up, since that update is a patch update (0.7.5 -> 0.7.7). Maybe there's another issue when multiple Cargo.tomls are involved(?).
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/cargo
branch
2 times, most recently
from
This PR contains the following updates:
1.4.1->1.5.01.4.1->1.5.01.19.0->1.20.20.4.13->0.5.00.4.13->0.5.00.5.2->0.6.0Release Notes
hyperium/hyper (hyper)
v1.5.0Compare Source
Bug Fixes
date_headereffective (#3718) (7de02373)Features
header_table_size()andmax_concurrent_streams()(4c84e8c1)ReadBufCursormethodsremaining()andput_slice()(#3700) (5a13041e)v1.4.1 (2024-07-09)
Bug Fixes
matklad/once_cell (once_cell)
v1.20.2Compare Source
portable_atomicfrom Cargo.lock if it is not, in fact, used: #267This is a work-around for this cargo bhttps://github.com/rust-lang/cargo/issues/108010801.
v1.20.1Compare Source
racemodule using justportable_atomic, withoutcritical_sectionand providebetter error messages on targets without atomic CAS instruction,
#265.
v1.20.0Compare Source
tower-rs/tower (tower)
v0.5.1: tower 0.5.1Compare Source
tower-layerdependency (#787)v0.5.0: tower 0.5.0Compare Source
Fixed
BoxServiceis nowSync(#702)Changed
ServiceExt::ready_andmethod andReadyAndfuture (#652)
retry::Policy::retrynow accepts&mut Reqand&mut Resinstead of the previous mutable versions. Thisincreases the flexibility of the retry policy. To update, update your method signature to include
mutfor both parameters. (#584)Reconnect::new(#755)Clonefor Change (#701)CloneforAsyncFilterLayer(#731)tower-rs/tower-http (tower-http)
v0.6.1: v0.6.1Compare Source
Fixed
New Contributors
v0.6.0: v0.6.0Compare Source
Changed:
bodymodule is disabled except forcatch-panic,decompression-*,fs, orlimitfeatures (BREAKING) (#477)tower0.5 (#503)Fixed
Configuration
📅 Schedule: Branch creation - "before 4am on Monday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.