Update otel/weaver Docker tag to v0.26.1 - #573
Merged
Merged
Conversation
There was a problem hiding this comment.
Copilot wasn't able to review any files in this pull request.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Member
|
this should fix #549 and open-telemetry/semantic-conventions#4021 |
trask
approved these changes
Sep 3, 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.
This PR contains the following updates:
v0.25.1→v0.26.1Release Notes
open-telemetry/weaver (otel/weaver)
v0.26.1: 0.26.1 - 2026-09-02Compare Source
Release Notes
weaver-installer.shfailing to detect Unix platforms due to missing bash shell in release workflow. (#1744)Install weaver 0.26.1
Install prebuilt binaries via shell script
Install prebuilt binaries via powershell script
powershell -ExecutionPolicy Bypass -c "irm https://github.com/open-telemetry/weaver/releases/download/v0.26.1/weaver-installer.ps1 | iex"Download weaver 0.26.1
Verifying GitHub Artifact Attestations
The artifacts in this release have attestations generated with GitHub Artifact Attestations. These can be verified by using the GitHub CLI:
You can also download the attestation from GitHub and verify against that directly:
v0.26.0: 0.26.0 - 2026-09-02Compare Source
Release Notes
registry live-checkandregistry infernow bind their OTLP and HTTP admin listeners to127.0.0.1instead of0.0.0.0, so they no longer listen on every local address by default. Pass--otlp-grpc-address(live-check) or--grpc-address(infer) to bind a specific interface, or0.0.0.0for all of them. The admin listener now binds to the same address as the OTLP listener rather than always to0.0.0.0. (#1740 by @lmolkova)crypto-ring,crypto-aws-lc,crypto-openssl,crypto-openssl-vendored,crypto-symcrypt), withcrypto-ringas the default. (#1712 by @lquerel)weaver.yamland.weaver.toml. (#1693 by @jsuereth)entity_refsandlookup_entityto thesemconvRego library, so anafter_resolutionpolicy can read the entity definition that anentity_associationsleaf names, including one a dependency defines.entity_refswalks theone_ofandall_oflevels of an association. (#1719 by @jerbly)lookup_entityJinja function, which turns anentity_associationsleaf into the entity definition it names, forweaver registry generateon a v2 registry. (#1718 by @jerbly)entity_associationsreference into a dependency, or to an entity refinement, neither of which the checker could see before: those entities went unchecked, so a resource missing their required attributes passed clean. A Rego advice policy can read the same v2 definitions, asdata.entities. (#1716 by @jerbly)entity_associationsleaf in the materialized schema now says which registry defines the entity, as the published schema already did. A leaf that was the bare namehostis now{ type: host, provenance: { source: <schema url> } }, and a leaf with no provenance means this registry defines it. A template, jq filter or Rego policy that read the leaf as a string reads.typeinstead, and theserveUI and its API are updated too. (#1710 by @jerbly)dependenciesin the materialized (forge) schema is now a map keyed by schema url holding each registry once, and thedependency_graphgives the direct dependencies of each. (#1730 by @jerbly)type: resourcegroup converting to a v2 entity whose type carried the group-id prefix. The entity type now comes from the group'sname, as it always did for imports, and falls back to the id when the group has none. Everyresourcegroup of semconv v1.33.0 has this shape, soresource.hostbecame the entityresource.hostrather thanhost, and anentity_associationsentry naminghostmatched nothing. (#1704 by @jerbly)entity.orspan.prefix from the type. I.e. an entity authored astype: entity.testnow keeps the typeentity.testinstead oftest. (#1704 by @jerbly)entity.hostandhostboth become the entityhostand the second silently replaced the first. (#1704 by @jerbly)entity_associationsentry, and record which registry defines the entity it names. A name that nothing in scope defines now fails resolution, as does one that two dependencies each declare an unrelated entity under. A private entity (dependency_resolution.exclude) satisfies an association only for a signal that is private too. In the v2 resolved schema an association leaf is now an object ({ type, provenance }) instead of a bare entity type;provenance.sourceindexesdependenciesand is absent for an entity of this registry. (#1704 by @jerbly)stabilityanddeprecatedon v2 attribute references. (#1720 by @lmolkova)importspattern that matched nothing in any dependency, as a warning. A typo or a stale name was previously dropped in silence. (#1701 by @jerbly)sampling_relevantsetting on its attributes. This is per-span state, held on the span's attribute reference rather than on the catalog attribute, so the import path never read it. Refining such a span was unaffected. (#1694 by @jerbly)importsnever matching a legacytype: resourceentity in a dependency. Such a group sets nonameand holds its entity type in the group id, so the matcher now matches the group id as well as the name. (#1694 by @jerbly)name+registry_pathin legacy (v1) manifests. (#1696 by @lmolkova)stabilityfrom the signal that declares it. The catalog lookup required the field to be present, so an entity could be published with an emptyidentity. A missing stability now converts todevelopment, the documented default, instead ofalpha. (#1695 by @jerbly)dependenciesset is the table thatDependencyRefprovenance indexes into, but it listed only direct dependencies, so anything reaching the registry through a dependency-of-a-dependency had no entry to point at. It now records the full closure. (#1655 by @jerbly)Install weaver 0.26.0
Install prebuilt binaries via shell script
Install prebuilt binaries via powershell script
powershell -ExecutionPolicy Bypass -c "irm https://github.com/open-telemetry/weaver/releases/download/v0.26.0/weaver-installer.ps1 | iex"Download weaver 0.26.0
Verifying GitHub Artifact Attestations
The artifacts in this release have attestations generated with GitHub Artifact Attestations. These can be verified by using the GitHub CLI:
You can also download the attestation from GitHub and verify against that directly:
Configuration
📅 Schedule: (UTC)
* 0-7 * * 2)🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.