Closed
Conversation
Bumps [bytes](https://github.com/tokio-rs/bytes) from 1.11.0 to 1.11.1. - [Release notes](https://github.com/tokio-rs/bytes/releases) - [Changelog](https://github.com/tokio-rs/bytes/blob/master/CHANGELOG.md) - [Commits](tokio-rs/bytes@v1.11.0...v1.11.1) --- updated-dependencies: - dependency-name: bytes dependency-version: 1.11.1 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
added
dependencies
Collaborator
|
I recommend first merging in the open PR #82 and I can open for you a PR after that updating all deps, not just this. FWIW not a big fan of dependabot in general, it are very noisy PRs. I usually recommend just manually updating all deps twice per week. That's why the command |
Collaborator
In light of recent alignments I will open a dependency update PR later today. Which brings in new rama improvements/simplifications as well |
GlenDC
added a commit
that referenced
this pull request
Feb 9, 2026
This replaces two security updates flagged by GitHub Dependabot: * #95 * #89 All dependencies were updated, including a significant Rama upgrade. The Rama update simplifies type erased error handling. OpaqueError is now intended only for edge cases where higher rank lifetime limitations require it. In most cases BoxError should be used, unless a strongly typed error is more appropriate. Error context traits now make it easy to attach structured fields to errors. This replaces manual string formatting and is both easier to use and lazier, as formatting is deferred until the error is actually displayed. This continues Rama’s incremental improvements driven by real world usage and feedback. Upcoming work includes a new Uri type and follow up improvements enabled by it.
Collaborator
|
Replaced by #99. |
GlenDC
added a commit
that referenced
this pull request
Feb 9, 2026
update dependencies and apply security fixes This replaces two security updates flagged by GitHub Dependabot: * #95 * #89 All dependencies were updated, including a significant Rama upgrade. The Rama update simplifies type erased error handling. OpaqueError is now intended only for edge cases where higher rank lifetime limitations require it. In most cases BoxError should be used, unless a strongly typed error is more appropriate. Error context traits now make it easy to attach structured fields to errors. This replaces manual string formatting and is both easier to use and lazier, as formatting is deferred until the error is actually displayed. This continues Rama’s incremental improvements driven by real world usage and feedback. Upcoming work includes a new Uri type and follow up improvements enabled by it.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Bumps bytes from 1.11.0 to 1.11.1.
Release notes
Sourced from bytes's releases.
Changelog
Sourced from bytes's changelog.
Commits
417dccdRelease bytes v1.11.1 (#820)d0293b0Merge commit from forkDependabot 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 this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.