You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Semantic Convention tooling group is deprecating build-tools in favor of new code-generation tool - weaver, see open-telemetry/build-tools#322 for the details.
Build-tools are compatible with the latest version of semantic-convention (1.28.0), but might become incompatible with the future versions of semantic-conventions. New features (such as event definition) are added to the weaver only and won't be supported by the build-tools.
Migration steps are documented here along with some non-normative guidelines on the code organization and artifact stability.
Looking for volunteers and happy to help or provide any additional details.
The text was updated successfully, but these errors were encountered:
Hi @lmolkova! Thanks for raising this issue. @robbkidd is working on incorporating weaver into our semantic conventions gem. See #1651 for the progress so far.
👋 This issue has been marked as stale because it has been open with no activity. You can: comment on the issue or remove the stale label to hold stale off for a while, add the keep label to hold stale off permanently, or do nothing. If you do nothing this issue will be closed eventually by the stale bot.
Semantic Convention tooling group is deprecating build-tools in favor of new code-generation tool - weaver, see open-telemetry/build-tools#322 for the details.
Build-tools are compatible with the latest version of semantic-convention (1.28.0), but might become incompatible with the future versions of semantic-conventions. New features (such as event definition) are added to the weaver only and won't be supported by the build-tools.
Migration steps are documented here along with some non-normative guidelines on the code organization and artifact stability.
Looking for volunteers and happy to help or provide any additional details.
The text was updated successfully, but these errors were encountered: