Skip to content

Update semconv version to v1.34.0 #2482

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 6 commits into from

Conversation

mjwolf
Copy link
Contributor

@mjwolf mjwolf commented May 29, 2025

To support generating the latest mappings between otel and semconv, update the semconv version which is used during file generation.

  • Have you signed the contributor license agreement? y
  • Have you followed the contributor guidelines? y
  • For proposing substantial changes or additions to the schema, have you reviewed the RFC process? n/a
  • If submitting code/script changes, have you verified all tests pass locally using make test? y
  • If submitting schema/fields updates, have you generated new artifacts by running make and committed those changes? y
  • Is your pull request against main? Unless there is a good reason otherwise, we prefer pull requests against main and will backport as needed. y
  • Have you added an entry to the CHANGELOG.next.md? y

To support generating the latest mappings between otel and semconv,
update the semconv version which is used during file generation.
@mjwolf mjwolf requested a review from a team as a code owner May 29, 2025 22:34
Copy link

Documentation changes preview: https://ecs_bk_2482.docs-preview.app.elstc.co/diff

Copy link

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

  • run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

@mjwolf
Copy link
Contributor Author

mjwolf commented May 30, 2025

Replaced by #2483

@mjwolf mjwolf closed this May 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants