Skip to content

Update Rust crate tokio-stream to 0.1.18#428

Open
nextest-bot wants to merge 1 commit into
mainfrom
renovate/tokio-stream-0.x
Open

Update Rust crate tokio-stream to 0.1.18#428
nextest-bot wants to merge 1 commit into
mainfrom
renovate/tokio-stream-0.x

Conversation

@nextest-bot

@nextest-bot nextest-bot commented Jan 4, 2026

Copy link
Copy Markdown
Collaborator

This PR contains the following updates:

Package Type Update Change Pending
tokio-stream (source) dev-dependencies patch 0.1.170.1.18 0.1.19

Release Notes

tokio-rs/tokio (tokio-stream)

v0.1.18

Compare Source


Configuration

📅 Schedule: (in timezone America/Los_Angeles)

  • Branch creation
    • "after 8pm,before 6am"
  • Automerge
    • "after 8pm,before 6am"

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate.

@nextest-bot nextest-bot added the dependencies Dependency-related updates label Jan 4, 2026
@nextest-bot
nextest-bot force-pushed the renovate/tokio-stream-0.x branch 6 times, most recently from da0c1a1 to 3070ff9 Compare January 11, 2026 11:15
@nextest-bot
nextest-bot force-pushed the renovate/tokio-stream-0.x branch 6 times, most recently from a047c8b to 72065aa Compare January 19, 2026 05:22
@nextest-bot
nextest-bot force-pushed the renovate/tokio-stream-0.x branch 10 times, most recently from dd003a3 to 1218fb6 Compare January 27, 2026 05:05
@nextest-bot
nextest-bot force-pushed the renovate/tokio-stream-0.x branch 4 times, most recently from 7ee7b5e to faf937e Compare February 1, 2026 05:45
@nextest-bot
nextest-bot force-pushed the renovate/tokio-stream-0.x branch 3 times, most recently from e275a20 to c079406 Compare February 6, 2026 06:10
@nextest-bot
nextest-bot force-pushed the renovate/tokio-stream-0.x branch 8 times, most recently from d12c90d to c904d46 Compare March 2, 2026 05:23
@nextest-bot
nextest-bot force-pushed the renovate/tokio-stream-0.x branch 8 times, most recently from e654718 to ed4b420 Compare March 11, 2026 05:05
@nextest-bot
nextest-bot force-pushed the renovate/tokio-stream-0.x branch 9 times, most recently from fd14926 to 27eccb3 Compare March 19, 2026 11:33
@nextest-bot
nextest-bot force-pushed the renovate/tokio-stream-0.x branch 3 times, most recently from 4f389af to 2d4099c Compare March 21, 2026 05:40
@nextest-bot

Copy link
Copy Markdown
Collaborator Author

⚠️ Artifact update problem

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.toml
Artifact update for tokio-stream resolved to version 0.1.19, which is a pending version that has not yet passed the Minimum Release Age threshold.
Renovate was attempting to update to 0.1.18
This is (likely) not a bug in Renovate, but due to the way your project pins dependencies, _and_ how Renovate calls your package manager to update them.
Until Renovate supports specifying an exact update to your package manager (https://github.com/renovatebot/renovate/issues/41624), it is recommended to directly pin your dependencies (with `rangeStrategy=pin` for apps, or `rangeStrategy=widen` for libraries)
See also: https://docs.renovatebot.com/dependency-pinning/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Dependency-related updates

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant