Skip to content

chore(deps): bump bytes from 1.11.0 to 1.11.1 in the cargo group across 1 directory#5

Merged
hyperpolymath merged 2 commits into
mainfrom
dependabot/cargo/cargo-f6ecf5c85a
Feb 18, 2026
Merged

chore(deps): bump bytes from 1.11.0 to 1.11.1 in the cargo group across 1 directory#5
hyperpolymath merged 2 commits into
mainfrom
dependabot/cargo/cargo-f6ecf5c85a

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Feb 3, 2026

Copy link
Copy Markdown
Contributor

Bumps the cargo group with 1 update in the / directory: bytes.

Updates bytes from 1.11.0 to 1.11.1

Release notes

Sourced from bytes's releases.

Bytes v1.11.1

1.11.1 (February 3rd, 2026)

  • Fix integer overflow in BytesMut::reserve
Changelog

Sourced from bytes's changelog.

1.11.1 (February 3rd, 2026)

  • Fix integer overflow in BytesMut::reserve
Commits

Dependabot compatibility score

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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will 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 version will 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
    You can disable automated security fix PRs for this repo from the Security Alerts page.

Bumps the cargo group with 1 update in the / directory: [bytes](https://github.com/tokio-rs/bytes).


Updates `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
  dependency-group: cargo
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file rust Pull requests that update rust code labels Feb 3, 2026
@dependabot @github

dependabot Bot commented on behalf of github Feb 8, 2026

Copy link
Copy Markdown
Contributor Author

Dependabot couldn't access the repository. Because of this, Dependabot cannot update this pull request.

1 similar comment
@dependabot @github

dependabot Bot commented on behalf of github Feb 10, 2026

Copy link
Copy Markdown
Contributor Author

Dependabot couldn't access the repository. Because of this, Dependabot cannot update this pull request.

Signed-off-by: Jonathan D.A. Jewell <6759885+hyperpolymath@users.noreply.github.com>
@hyperpolymath hyperpolymath merged commit 62ce32d into main Feb 18, 2026
4 of 17 checks passed
@hyperpolymath hyperpolymath deleted the dependabot/cargo/cargo-f6ecf5c85a branch February 18, 2026 20:19
hyperpolymath added a commit that referenced this pull request Apr 20, 2026
…ss 1 directory (#5)

Bumps the cargo group with 1 update in the / directory:
[bytes](https://github.com/tokio-rs/bytes).

Updates `bytes` from 1.11.0 to 1.11.1
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/tokio-rs/bytes/releases">bytes's
releases</a>.</em></p>
<blockquote>
<h2>Bytes v1.11.1</h2>
<h1>1.11.1 (February 3rd, 2026)</h1>
<ul>
<li>Fix integer overflow in <code>BytesMut::reserve</code></li>
</ul>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/tokio-rs/bytes/blob/master/CHANGELOG.md">bytes's
changelog</a>.</em></p>
<blockquote>
<h1>1.11.1 (February 3rd, 2026)</h1>
<ul>
<li>Fix integer overflow in <code>BytesMut::reserve</code></li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/tokio-rs/bytes/commit/417dccdeff249e0c011327de7d92e0d6fbe7cc43"><code>417dccd</code></a>
Release bytes v1.11.1 (<a
href="https://redirect.github.com/tokio-rs/bytes/issues/820">#820</a>)</li>
<li><a
href="https://github.com/tokio-rs/bytes/commit/d0293b0e35838123c51ca5dfdf468ecafee4398f"><code>d0293b0</code></a>
Merge commit from fork</li>
<li>See full diff in <a
href="https://github.com/tokio-rs/bytes/compare/v1.11.0...v1.11.1">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=bytes&package-manager=cargo&previous-version=1.11.0&new-version=1.11.1)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

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-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore <dependency name> major version` will 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 version` will 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
You can disable automated security fix PRs for this repo from the
[Security Alerts
page](https://github.com/hyperpolymath/echidna/network/alerts).

</details>

Signed-off-by: dependabot[bot] <support@github.com>
Signed-off-by: Jonathan D.A. Jewell <6759885+hyperpolymath@users.noreply.github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Jonathan D.A. Jewell <6759885+hyperpolymath@users.noreply.github.com>
Repository owner deleted a comment from chatgpt-codex-connector Bot May 13, 2026
hyperpolymath pushed a commit that referenced this pull request May 26, 2026
Closes Audit-A new-doc gap #5: docs/handover/ has grown to 13 files
(L1/L2/L3 prompts, S4/S5 runbooks, suggest CLI, theorem metadata)
without a current map. This index groups them by type (prompt /
runbook / plan / state), notes pre-conditions, and cross-references
ROADMAP stage IDs to the handover artefact that drives each.

https://claude.ai/code/session_01YPqu7gti4azBach6ZvpRFJ
hyperpolymath added a commit that referenced this pull request Jun 4, 2026
)

## Summary

Closes the estate-onboarding blocker **D18** from the 2026-06-03 audit:
L3 → L1 hand-off requires Tier-1 green ≥7 days + all 4 waves
landed-or-deferred. As of today the gate is NOT satisfied — but
crucially, **no one had enumerated exactly why**, so L1 (Cap'n Proto)
and L2 (Chapel full integration) stayed parked on a vague signal.

This PR lands a precise checklist at `docs/handover/L3-GATE-PATH.adoc`
that walks the six L3 acceptance criteria and records the current status
of every sub-criterion.

## Summary table

| Criterion | Description | Status |
|---|---|---|
| 1 | Wave-1 (every-PR Tier-1) green ≥7 days | ⚠ UNKNOWN (data not
collected) |
| 2 | Wave-2 (nightly Tier-2) green ≥1 cycle | ⚠ UNVERIFIED |
| 3 | Wave-3 (weekly Tier-3) green ≥1 cycle | ⚠ UNVERIFIED |
| 4 | Wave-4 (quarterly Tier-4) executed or explicitly deferred | ⚠
owner choice |
| 5 | Tier-1 green ≥7 days on main (data) | ❌ TODO |
| 6a | `guix shell` local end-to-end | ❌ TODO |
| 6b | Dafny stub upgrade audit | ⚠ UNKNOWN |
| 6c | VeriSimDB live-record emission | ⚠ PARTIAL (gated on
`verisimdb#ghcr-publish.yml`) |

## Minimum sufficient path

1. Run `gh run list --workflow live-provers.yml --branch main --status
success --limit 14` and record the green window in `STATE.a2ml`. (Closes
1, 2, 5.)
2. Same query against `container-ci.yml` for Tier-3 weekly. (Closes 3.)
3. Owner decision on Wave-4: execute one quarterly run OR formally defer
with a STATE.a2ml note. (Closes 4.)
4. One dev-host run of `guix shell -m manifests/live-provers.scm -- just
test-live`. (Closes 6a.)
5. Audit `src/rust/provers/dafny.rs` against the deep-wiring bar used
for Coq/Lean4. (Closes 6b.)
6. (6c stays parked on `verisimdb#ghcr-publish.yml` — upstream-blocked,
not on this gate's critical path.)

Estimated effort: **one session** if gh tokens are available. Without gh
access, Criteria 1/2/3/5 cannot close — full stop.

## Test plan

- [x] Cross-references to other audit PRs (C12, C14, C15, B7) verified.
- [x] All file paths quoted exist on main
(`docs/handover/L3-LIVE-PROVER-CI-PROMPT.md`, `docs/handover/TODO.md`,
`STATE.a2ml`).
- [ ] Owner reviews and confirms the criterion list matches the actual
L3 → L1 gate expectation.

## Estate context

This PR is **#5 of 5** in the C12/C14/C15/B7/D18 critical-blocker pass
coming out of the echidna estate-scale audit.

- C12 PR (echidnabot manifest):
hyperpolymath/echidnabot#84
- C14 PR (cross-repo proof DAG design):
#217
- C15 PR (gitbot-fleet hypatia wiring):
hyperpolymath/gitbot-fleet#257
- B7 PR (HP backend correction):
#218

🤖 Generated with [Claude Code](https://claude.com/claude-code)

---------

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file rust Pull requests that update rust code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant