chore(deps): update Weaver to 0.26.1 and semconv to v1.44.0 - #1459
Merged
schickling-assistant merged 3 commits intoSep 28, 2026
Merged
Conversation
Supersedes #1245. agent-identity: dev3.direct.omp.3zf2n4b9 agent-persona: generalist agent-supervisor: unavailable agent-tool: OMP agent-tool-version: 18.3.1 agent-runtime: OMP 18.3.1 agent-model: anthropic/claude-opus-5-5 tooling-profile: dotfiles@7d890da
schickling-assistant
marked this pull request as ready for review
September 27, 2026 15:14
Contributor
Storybook Previews
Report historyPR 1459 · 2026-09-28 21:28 UTC
PR 1459 · 2026-09-28 19:48 UTC
PR 1459 · 2026-09-27 15:36 UTC
|
schickling-assistant
enabled auto-merge (squash)
September 28, 2026 16:19
…2026-09-27-deps-weaver-0-26 # Conflicts: # CHANGELOG.md
Collaborator
Author
|
Resolved the conflict by merging current Checks on the merged commit: The longer Buck startup allowance was needed on this IO-loaded host; the complete quick-check dependency graph passed. Posted on behalf of @schickling
|
schickling-assistant
deleted the
schickling-assistant/2026-09-27-deps-weaver-0-26
branch
September 28, 2026 21:31
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.
Problem
The repo pins Weaver 0.24.2 and OpenTelemetry semantic conventions v1.37.0. The newest stable releases are Weaver 0.26.1 and semconv v1.44.0. Moving to them takes coordinated changes to the source pins, the generated projections, the emitted dependency schema, and the validation policy.
Goal
Pin Weaver 0.26.1 and semconv v1.44.0, regenerate the registry projections, and keep the Weaver gates (
//:weaver_check,//:weaver_version_smoke,weaver:diff, and live-check) green and meaningful.Decisions
name+registry_pathdependency form the emitted manifest uses, and upstream restored it in 0.26.0 (Restore support for dependencies declared by name in legacy (v1) manifests open-telemetry/weaver#1696).schema_urlthat Weaver 0.26 requires (Dependencytype,renderManifest, and test fixture).weaver:diffnormalizes a pre-0.26 baseline manifest to the current dependencyschema_url, so the one-time migration does not mask first-party changes.--future) in the Buckweaver-check-runner,weaver:diff, and the live-check integration test. This was measured with the built 0.26.1 against v1.44.0:weaver registry checkexits 0, while--futureexits 1 with 32 errors, allFile format definition/2 is not yet stablein upstream/nix/store/…semconv-model-1.44.0files and none in the first-party registry.weaver:checkmoved from a devenv task to the Buck runner (packages/@overeng/buck2-tools/src/weaver-check-runner.ts). The policy change is applied there, and the spec text is rebased onto the Buck wording.src,semconvSrc,weaver-uipnpm deps) were realized locally with no mismatch, so no refresh was needed.Verification
nix build .#weaver .#semconv-model: builtweaver-0.26.1(weaver --version→weaver 0.26.1) andsemconv-model-1.44.0. All three FOD hashes verified.devenv tasks run genie:run: regeneration produced no further diff, so the committed projections, fingerprints, and manifest are current.weaver registry check, stable vs--future, on the emitted registry against the local v1.44.0 model:stable rc=0,future rc=1(only upstreamdefinition/2errors).devenv tasks run weaver:diff:✓ no breaking (removed) changes vs baseline afa95a89. Its gate semantics were re-verified on 0.26.1 with two throwaway mutations, both reverted:acme.attemptgives✗ BREAKING — the registry failed to diff/resolve against its baseline (exit 1).git.baregives✗ BREAKING compat change — … REMOVED: - git.bare.devenv tasks run check:quick: exit 0. 15 tasks passed with no failures.buck2:quick(BUILD SUCCEEDED) includes:weaver_checkand:weaver_version_smokein the quick aggregate.Complexity
The
schema_urlfield and the baseline normalization are required by Weaver 0.26. Stable policy mode keeps upstream experimental definitions from failing this repo's registry gates.Concerns
Without
--future, diagnostics about experimental upstream definitions stay warnings instead of errors. First-party--futurecleanliness is not gated any more, but it currently holds: no first-party errors under--future.Friction & bottlenecks
The Weaver Rust build took about 8.5 minutes on a heavily loaded host (load average ~100 on 32 cores).
Follow-ups
--futureonce upstream semconv stabilizesdefinition/2.References
Posted on behalf of @schickling
agent_identitysessionagent_personaagent_supervisoragent_toolagent_tool_versionagent_runtimeagent_modelworktreetooling_profile