Repository navigation
build(deps): bump tracing-opentelemetry from 0.28.0 to 0.34.0 - #16
Open
dependabot[bot] wants to merge 2 commits into
Open
dependabot[bot] wants to merge 2 commits into
dependabot[bot] wants to merge 2 commits into
Conversation
dependabot
Bot
added
dependencies
zylvex-tech
added a commit
that referenced
this pull request
Oct 22, 2026
… verified one The P3 backlog item claimed "5 are failing and 6 are green major-version bumps". The "5 failing" figure was carried forward from an earlier session and happened to be right, but the "6 green major-version bumps" figure was not re-derived and did not match the current state. Re-queried every open Dependabot PR head SHA individually: failing (5): #7, #8 (mixed), #12, #14, #17 green (10): #9, #10, #11, #13, #15, #16, #18, #19, #20, #21 Of the 10 green, 8 cross a major version or a semver-0.x minor (which is breaking under 0.x rules): #9 tauri-action 0->1, #10 tree-sitter-rust 0.23.3->0.24.2, #11 opentelemetry-otlp 0.28.0->0.33.1, #13 actions/checkout 4->7, #15 axum 0.7.9->0.8.9, #16 tracing-opentelemetry 0.28.0->0.34.0, #18 react, #19 framer-motion 11.18.2->14.3.0. The item now states the verified split with PR numbers and version deltas instead of an unsourced ratio. The limitations section is narrowed to match: check status was verified per SHA, PR contents were not reviewed.
Gar-gar22
pushed a commit
to Gar-gar22/zylcode
that referenced
this pull request
Oct 23, 2026
… advisory register Read-only audit of the merge outcome of PR zylvex-tech#23 (router egress spy) and PR zylvex-tech#24 (lru 0.12.5 -> 0.18.5, tokio 1.54.0 -> 1.54.1). Evidence was gathered per-SHA through the GitHub REST API and by running cargo audit against main's own lockfile; no repository file was modified during collection. Findings recorded in docs/governance/POST_MERGE_AUDIT_2026-10-22.md: - CI on the final main commit is green: run #120 (CI) and zylvex-tech#16 (Coverage) both success; 840 tests pass on each of ubuntu-22.04, windows-latest and macos-latest with 0 failures; 0 Clippy lints; all 13 steps pass. - The intermediate merge commit 184e178 carried a FAILING macOS job: router::tests::d1_vector_cache_cross_prompt_contamination_guard read 8 instead of 5 network-egress events. 184e178 and f0c729b have byte-identical trees, so that failure is flakiness rather than a regression - and it is the exact defect PR zylvex-tech#23 fixes. The same test passes on main's head. - RUSTSEC-2026-0002, RUSTSEC-2026-0253 and the yanked tokio release are all resolved. 0 vulnerabilities; 3 informational warnings remain (glib, proc-macro-error, unsafe-libyaml), each documented with dependency path, severity, fixed version and remediation. - main has NO branch protection and no ruleset (HTTP 404 on the protection endpoint, empty rulesets list). A recommended configuration keyed to the four real check names is included. Two corrections to previously published claims: - PHASE2_VERIFICATION_REPORT.md section 6 labels 80.63% as "lines". That is the Regions figure; the gated Lines figure on main's head is 80.53% (40,133 / 7,815). Both clear the 78% floor. Corrected in the new report; the original is left as the historical record. - ACCEPTED_ADVISORIES.md claimed lru's pop() "is not on a path ZylCode calls". It is: crates/zylcode-core/src/router/cache.rs:61 calls guard.pop(&key). The row is now moot, but the claim was false when written and is corrected rather than quietly dropped. The advisory register is updated from five advisories to three, and the stale "5 accepted advisories" comment in ci.yml is corrected to three with a revision note. Comment-only change to ci.yml; the retracted-claims guard and secret scan are unaffected (both verified locally, exit 0).
dependabot
Bot
force-pushed
the
dependabot/cargo/tracing-opentelemetry-0.34.0
branch
from
October 23, 2026 14:55
4aef627 to
46412cb
Compare
Bumps [tracing-opentelemetry](https://github.com/tokio-rs/tracing-opentelemetry) from 0.28.0 to 0.34.0. - [Release notes](https://github.com/tokio-rs/tracing-opentelemetry/releases) - [Changelog](https://github.com/tokio-rs/tracing-opentelemetry/blob/v0.1.x/CHANGELOG.md) - [Commits](https://github.com/tokio-rs/tracing-opentelemetry/commits) --- updated-dependencies: - dependency-name: tracing-opentelemetry dependency-version: 0.34.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/cargo/tracing-opentelemetry-0.34.0
branch
from
October 25, 2026 07:32
46412cb to
35a256f
Compare
Gar-gar22
approved these changes
Oct 25, 2026
Gar-gar22
approved these changes
Oct 25, 2026
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
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 tracing-opentelemetry from 0.28.0 to 0.34.0.
Release notes
Sourced from tracing-opentelemetry's releases.
... (truncated)
Changelog
Sourced from tracing-opentelemetry's changelog.
... (truncated)
Commits