Skip to content
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

chore: prepare next release #18

Conversation

marcpichler
Copy link
Collaborator

@marcpichler marcpichler commented Aug 15, 2024

1.26.0

🚀 (Enhancement)

  • feat: include instrumentation scope info in console span and log record exporters #4848 @blumamir
  • feat(semconv): update semantic conventions to 1.27 (from 1.7.0) #4690 @dyladan
    • Exported names have changed to ATTR_{name} for attributes (e.g. ATTR_HTTP_REQUEST_METHOD), {name}_VALUE_{value} for enumeration values (e.g. HTTP_REQUEST_METHOD_VALUE_POST), and METRIC_{name} for metrics. Exported names from previous versions are deprecated.
    • Import @opentelemetry/semantic-conventions for stable semantic conventions. Import @opentelemetry/semantic-conventions/incubating for all semantic conventions, stable and unstable.
    • Note: Semantic conventions are now versioned separately from other stable artifacts, to correspond to the version of semantic conventions they provide.

🐛 (Bug Fix)

  • fix(sdk-node): avoid spurious diag errors for unknown OTEL_NODE_RESOURCE_DETECTORS values #4879 @trentm
  • deps(opentelemetry-instrumentation): Bump shimmer types to 1.2.0 #4865 @lforst

🏠 (Internal)

0.52.1

🚀 (Enhancement)

  • refactor(instrumentation-fetch): move fetch to use SEMATRR #4632
  • refactor(otlp-transformer): use explicit exports #4785 @pichlermarc

🐛 (Bug Fix)

🏠 (Internal)

  • test: add npm run maint:regenerate-test-certs maintenance script and regenerate recently expired test certs #4777

@JamieDanielson
Copy link
Collaborator

This PR is so far a successful semconv release PR separate from the SDK release PR, using this command prepare_release:semconv:minor; action workflow here.

Next step is confirming a SDK release PR doesn't include semconv.

Then need to set proper version of the package.

@JamieDanielson
Copy link
Collaborator

Hmm, SDK release did bump package version of semantic conventions with the command prepare_release:sdk:minor; action workflow here. Next step is figure out why that wasn't excluded.

@marcpichler marcpichler force-pushed the release/next-version branch 2 times, most recently from 5da34ed to 956434f Compare August 15, 2024 15:00
@JamieDanielson
Copy link
Collaborator

prepare_release:semconv:minor successful version bump (action workflow) 🎉

next step: prepare_release:semconv:minor to bump version and exclude semconv 🤞

@JamieDanielson
Copy link
Collaborator

🤔 prepare_release:sdk:minor still includes version bump for semantic conventions... but includes for experimental too? action workflow

@marcpichler marcpichler force-pushed the release/next-version branch 2 times, most recently from a325db1 to d6bdb13 Compare August 15, 2024 17:08
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.

3 participants