chore(deps): update otel/weaver docker tag to v0.13.0 #6292
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.12.0
->v0.13.0
Release Notes
open-telemetry/weaver (otel/weaver)
v0.13.0
: 0.13.0 - 2025-02-07Compare Source
Release Notes
What's changed
Breaking Change: Introduced a new
weaver registry diff
command to generate a diff report between two versions ofthe semantic convention registry. This PR introduces a breaking change in the semantic conventions schema. While the
text-based
deprecated
field is still supported for compatibility reasons, future semantic conventions should use thenew
deprecated
structured format. (#400 by @lquerel).deprecated
field is now a structured field defining the precise reason for deprecation. The semanticconventions must be updated to adopt this new format.
deprecated
field (i.e., string → struct) also have a potential impact on certaintemplates that reference the
deprecated
field as containing text. These templates will need to be updated to usethe
brief
field, which provides a textual explanation of the reasons for the deprecation.Improvement of comment generation: removal of
<p>
tags that precede@
Javadoc tags.(#574 by @trask).
For Issue #564 - Require attributes and event fields to have stability: Added warnings for missing stability
on: Attributes, Enum members in attributes, Event AnyValues, Enum members in AnyValues. (#568 by @jerbly).
For issue [#569](Add include_stability config into semconv_grouped_attributes):
is_experimental
returnstrue
by default. (#570 by @jerbly).Added an OTLP receiver to Weaver to prepare for the
weaver registry live-check
command. (see #548 by @lquerel)Add is_array filter and test for AttributeType. (#540 by @arthurDiff).
Refactored CLI registry commands to remove some duplication. Resolving the registry with policy checks is common for
generate
,resolve
andcheck
. (#536 by @jerbly).after_resolution
policy checks togenerate
andresolve
through the common code.--registry-git-sub-dir
option.check
if--skip-policies
was specified then it would not fail for any validation errors.Semantic Conventions Issue #1513 - Make span_kind required in yaml and break down multi-kind span
definitions - (#542 by @jerbly).
span_kind
as mandatory forspan
group types. Added a group validitycheck as a warning.
First iteration of the new command:
registry emit
. Emits a semantic convention registry as example spans to yourOTLP receiver. This may be useful in testing/simulation scenarios. (#549 by @jerbly)
For issue [#569](Add include_stability config into semconv_grouped_attributes): added
stable_only
boolean flag as a parameter forsemconv_signal
,semconv_grouped_attributes
, and othersemconv_*
JQ semconv helpers. Whenstable_only
is set totrue
,corresponding helper function returns stable conventions only. If the flag is not set or set to false, stability filtering does not apply.
It's recommended to use
stable_only
flag instead ofexclude_stability
parameter.(#588 by @lmolkova)
Install weaver 0.13.0
Install prebuilt binaries via shell script
Install prebuilt binaries via powershell script
powershell -c "irm https://github.com/open-telemetry/weaver/releases/download/v0.13.0/weaver-installer.ps1 | iex"
Download weaver 0.13.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: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, 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.