Skip to content

chore(deps): bump toml from 0.8.23 to 1.1.2+spec-1.1.0 in /bots/seambot - #33

Merged
hyperpolymath merged 1 commit into
mainfrom
dependabot/cargo/bots/seambot/toml-1.1.2spec-1.1.0
Apr 5, 2026
Merged

hyperpolymath merged 1 commit into
mainfrom
dependabot/cargo/bots/seambot/toml-1.1.2spec-1.1.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Apr 5, 2026 •

Copy link
Copy Markdown
Contributor

Bumps toml from 0.8.23 to 1.1.2+spec-1.1.0.

Commits

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file rust Pull requests that update rust code labels Apr 5, 2026
@dependabot
dependabot Bot requested a review from hyperpolymath as a code owner April 5, 2026 06:53
@dependabot dependabot Bot added the rust Pull requests that update rust code label Apr 5, 2026
@dependabot
dependabot Bot force-pushed the dependabot/cargo/bots/seambot/toml-1.1.2spec-1.1.0 branch from a2c2fdb to b20b085 Compare April 5, 2026 17:59
Bumps [toml](https://github.com/toml-rs/toml) from 0.8.23 to 1.1.2+spec-1.1.0.
- [Commits](toml-rs/toml@toml-v0.8.23...toml-v1.1.2)

---
updated-dependencies:
- dependency-name: toml
  dependency-version: 1.1.2+spec-1.1.0
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/cargo/bots/seambot/toml-1.1.2spec-1.1.0 branch from b20b085 to d02f0e9 Compare April 5, 2026 18:00
@hyperpolymath
hyperpolymath merged commit 42f4f6f into main Apr 5, 2026
16 of 21 checks passed
@hyperpolymath
hyperpolymath deleted the dependabot/cargo/bots/seambot/toml-1.1.2spec-1.1.0 branch April 5, 2026 18:01
Repository owner deleted a comment from chatgpt-codex-connector Bot May 13, 2026
hyperpolymath added a commit that referenced this pull request Oct 15, 2026
…ctions (#611)

## What this changes

Makes the review-thread loop a fleet capability instead of a by-hand
chore. Today's CodeRabbit estate sweep (2026-10-15) closed seven threads
manually: rsr-template-repo #240 (2), choreographic-types #33,
occupancy-types #13 (2), CompositionalDA.jl #11, odraz #19 — each needed
a fix, a reply on the thread, and a resolve.

- **TOKEN-ARCHITECTURE.adoc** — echidnabot's action table gains the two
stewardship endpoints: reply-to-review-thread (`POST
/repos/{owner}/{repo}/pulls/{pr}/comments/{id}/replies`) and
resolve-thread (GraphQL `resolveReviewThread`). Both are covered by its
existing `repo` scope; no new scopes requested.
- **BOT-OPERATIONS.adoc** — the metarule: match an unresolved thread to
a Hypatia finding or fleet fix, land the fix on the PR branch
(robot-repo-automaton), reply with the fix commit and reasoning, then
resolve. Threads whose findings are verified no-longer-valid close with
a skip-reason reply instead of silence.
- **Safety carve-out**: identity-class findings (HYP-S010, clade
identity coherence) are `auto_fixable: false` — the bot proposes and
replies; the owner rules on direction. The odraz #19 corollary is
recorded: a reviewer bot confidently aligned a uuid to template residue;
check which side is the residue before automating.

Pairs with hyperpolymath/standards#1270 (the rule declarations) and
hyperpolymath/hypatia#924 (the live bash detection).

Note: the commit is unsigned (the signing key's passphrase is
unavailable to the session); amend to sign if required.

Generated by Mistral Vibe.
Co-Authored-By: Mistral Vibe <vibe@mistral.ai>

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

* **Documentation**
* Clarified how review findings are matched to threads and how addressed
findings receive fix details before their threads are resolved.
* Documented that ambiguous matches leave threads unchanged, while
invalid findings receive an explanation and remain unresolved.
* Added guidance on owner approval for identity-related fixes, checking
alignment findings before automating fixes, and the permissions needed
for review-thread actions.
* Updated runtime guidance to list Deno as a secondary JavaScript
runtime and package manager.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Co-authored-by: Mistral Vibe <vibe@mistral.ai>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.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