Skip to content

chore(ci): add semconv-update workflow for automatic updates #6750

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

Open
wants to merge 18 commits into
base: main
Choose a base branch
from

Conversation

kema-dev
Copy link

@kema-dev kema-dev commented May 7, 2025

Description

  • Add semconv update workflow

Why

  • Manually running the update looks tedious, automated daily update looks nicer to me
  • You can see an example here

Additional notes

  • We might want to edit RELEASING.md accordingly, let me know if the workflow-way is practicable, I would edit the file if so

Copy link

linux-foundation-easycla bot commented May 7, 2025

CLA Signed

The committers listed above are authorized under a signed CLA.

@kema-dev kema-dev closed this May 7, 2025
@kema-dev kema-dev reopened this May 7, 2025
@pellared
Copy link
Member

pellared commented May 7, 2025

Thank you for your PR.

It seems that @MrAlias is working on a new way to generate semconv packages (see: #6683).

@kema-dev
Copy link
Author

kema-dev commented May 8, 2025

Added minor UX upgrades and changed cache key to one specific to semconvkit's usage, example here

Copy link
Contributor

@MrAlias MrAlias left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This will not generate the migration documentation for the packge. #6248 needs a resolution and then automation to add that documentation needs to be added prior to being able to automate the generation in this manner.

@@ -4,24 +4,6 @@

Create a `Version Release` issue to track the release process.

## Semantic Convention Generation
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This shouldn't be completely removed. We still need the option to generate the packages locally and that process should be documented. Additionally, the automated way of generating the package should be added.

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.

4 participants