chore(deps): bump tracing-subscriber from 0.3.22 to 0.3.23 in /robot-repo-automaton#2
Merged
hyperpolymath merged 1 commit intoMar 21, 2026
Conversation
Bumps [tracing-subscriber](https://github.com/tokio-rs/tracing) from 0.3.22 to 0.3.23. - [Release notes](https://github.com/tokio-rs/tracing/releases) - [Commits](tokio-rs/tracing@tracing-subscriber-0.3.22...tracing-subscriber-0.3.23) --- updated-dependencies: - dependency-name: tracing-subscriber dependency-version: 0.3.23 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
dependabot
Bot
added
dependencies
hyperpolymath
approved these changes
Mar 21, 2026
hyperpolymath
deleted the
dependabot/cargo/robot-repo-automaton/tracing-subscriber-0.3.23
branch
hyperpolymath
added a commit
that referenced
this pull request
Jun 21, 2026
Items #2 (clippy sweep) and #1 (close the CI gap) from the follow-up list, as one PR — the lint fixes and the gate that enforces them belong together so CI is self-consistent. ## Why The only Rust CI was CodeQL in build-mode `none` (**buildless**) — nothing compiled or tested `robot-repo-automaton` / `shared-context` / `dashboard`. That's exactly how the non-compiling content-match path reached `main` before #299 fixed it. This closes that gap. ## The gate — `.github/workflows/rust.yml` Per-crate matrix (modeled on `e2e.yml`: SHA-pinned checkout, `permissions: contents: read`, SPDX header): - `cargo build --all-targets` - `cargo test` - `cargo clippy --all-targets -- -D warnings` *(blocking)* - `cargo fmt --check` *(informational, `continue-on-error`)* — there's ~180 hunks of **pre-existing** formatting drift; gating it would mean a giant reformat that buries this change, so it's surfaced but not yet enforced. A dedicated `cargo fmt` pass can flip it to blocking later. ## Clippy fixes (to make the gate green) | File | Finding | Fix | |---|---|---| | `fixer.rs` | `.replace("hyperpolymath", "hyperpolymath")` | no-op — removed | | `registry_guard.rs` | manual `splitn(2, '/')` | `split_once('/')` | | `exclusion_registry.rs` | `from_str` shadows `FromStr` | rename inherent `from_str` → `parse` (matches `Catalog::parse`; 2 internal call sites) | | `exclusion_registry.rs` | `.ok()` + `if let Some` | `if let Ok(..)` | | `hypatia.rs`, `main.rs` | `&PathBuf` arg | `&Path` | | `Cargo.toml` ×2 | `toml = "1.1.2+spec-1.1.0"` | drop ignored `+spec` build-metadata (resolution-neutral; silences cargo warning) | | `benches/fleet_benchmarks.rs` | deprecated `criterion::black_box` | import `std::hint::black_box` (one import swap covers all call sites) | ## Verification All three crates: **clippy `-D warnings` clean**, build clean. Tests: **101** (robot-repo-automaton) + **84** (shared-context) pass. Locally simulated the full matrix (build + test + clippy) green per crate; `rust.yml` parses as valid YAML. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01RozeeLxpJsd3WWFngaZWz3 --- _Generated by [Claude Code](https://claude.ai/code/session_01RozeeLxpJsd3WWFngaZWz3)_ --------- Co-authored-by: Claude <noreply@anthropic.com>
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.
Rebasing might not happen immediately, so don't worry if this takes some time.
Note: if you make any changes to this PR yourself, they will take precedence over the rebase.
Bumps tracing-subscriber from 0.3.22 to 0.3.23.
Release notes
Sourced from tracing-subscriber's releases.
Commits
54ede4dchore: prepare tracing-subscriber 0.3.23 (#3490)37558d5subscriber: allow ansi sanitization to be disabled (#3484)efc690fcore: add missing const (#3449)0c32367core: Use const initializers instead ofonce_cell9feb241docs: add arcswap reload crate to related (#3442)2d55f6fchore: prepare tracing 0.1.44 (#3439)10a9e83chore: prepare tracing-core 0.1.36 (#3440)ee82cf9tracing: fix record_all panic (#3432)9978c36chore: prepare tracing-mock 0.1.0-beta.3 (#3429)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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@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)