The six opentelemetry crates came from a git dependency on upstream's fork (ae66e97), so every clean build fetched from upstream's repository. They're now vendored at that commit under vendor/opentelemetry-rust and patched in with [patch.crates-io], like hickory and sieve-rs. VENDORED.md says what the copy is and how to update it.
This is 1cb9af1 from the merge branch, applied to main. The two Cargo.toml conflicts were nearby lines only (main keeps chrono and the sieve-rs note); only the opentelemetry change is applied.
Checked:
every vendored src/ file is identical to cargo's git checkout of ae66e97 (the proto submodule is left out by cargo package and isn't used at build time)
no build.rs, no hidden Unicode, no AI-addressed text (the hits are OpenTelemetry's GenAI attribute docs)
no AGENTS.md or CLAUDE.md copied from the upstream repo
cargo build --locked --offline passes; Cargo.lock has no opentelemetry entry with a git source
fork checks pass, including context-check (the Docker build context and cook stage include the new paths)
The six opentelemetry crates came from a git dependency on upstream's fork (ae66e97), so every clean build fetched from upstream's repository. They're now vendored at that commit under vendor/opentelemetry-rust and patched in with [patch.crates-io], like hickory and sieve-rs. VENDORED.md says what the copy is and how to update it.
This is 1cb9af1 from the merge branch, applied to main. The two Cargo.toml conflicts were nearby lines only (main keeps chrono and the sieve-rs note); only the opentelemetry change is applied.
Checked:
- every vendored src/ file is identical to cargo's git checkout of ae66e97 (the proto submodule is left out by cargo package and isn't used at build time)
- no build.rs, no hidden Unicode, no AI-addressed text (the hits are OpenTelemetry's GenAI attribute docs)
- no AGENTS.md or CLAUDE.md copied from the upstream repo
- `cargo build --locked --offline` passes; Cargo.lock has no opentelemetry entry with a git source
- fork checks pass, including context-check (the Docker build context and cook stage include the new paths)
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The six opentelemetry crates came from a git dependency on upstream's fork (ae66e97), so every clean build fetched from upstream's repository. They're now vendored at that commit under vendor/opentelemetry-rust and patched in with [patch.crates-io], like hickory and sieve-rs. VENDORED.md says what the copy is and how to update it.
This is
1cb9af1from the merge branch, applied to main. The two Cargo.toml conflicts were nearby lines only (main keeps chrono and the sieve-rs note); only the opentelemetry change is applied.Checked:
cargo build --locked --offlinepasses; Cargo.lock has no opentelemetry entry with a git source