chore: release 1.2.0

[dyladan]

🤖 I have created a release *beep* *boop*

1.2.0 (2022-08-09)

Features

• Add getActiveSpan to trace API (#163) (17ccb3a)
• deprecate Sampler (#166) (313b2e2)

---

This PR was generated with Release Please. See documentation.

[codecov]

Codecov Report

Merging #171 (3dcb9cf) into main (313b2e2) will not change coverage.
The diff coverage is n/a.

❗ Current head 3dcb9cf differs from pull request most recent head f49e0e4. Consider uploading reports for the commit f49e0e4 to get more accurate results

@@           Coverage Diff           @@
##             main     #171   +/-   ##
=======================================
  Coverage   95.23%   95.23%           
=======================================
  Files          45       45           
  Lines         650      650           
  Branches      102      102           
=======================================
  Hits          619      619           
  Misses         31       31           

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[dyladan]

@open-telemetry/javascript-maintainers this would require the latest SDK in oder to be used because the minor version is updated. Should we instead release this as 1.1.1? It is not a bug fix, but it is strictly compatible with the previous SDK version.

[dyladan]

Lint check fails because the link to the release is broken until the release is made.

[Flarna]

Should we instead release this as 1.1.1?

Why should we violate semver? If some instrumentation uses the new API it should depend on 1.2.0 to clearly indicated that it can't work with 1.1.x.

There is compatibility with old SDK but not with old API.

[legendecas]

I have no good argument to break the semver semantics.

Notably, in our docs, we always ignore the patch bit in the semver: https://github.com/open-telemetry/opentelemetry-js#compatibility-matrix. I found @Flarna's point is fair.

[dyladan]

OK sounds good

[dyladan]

🤖 Release is at https://github.com/open-telemetry/opentelemetry-js-api/releases/tag/v1.2.0 🌻

[cartermp]

@dyladan what are the next steps here? The API docs we point people towards are up to date w.r.t. 1.2: https://open-telemetry.github.io/opentelemetry-js-api/interfaces/tracer.html

But there's no corresponding 1.2 package on npmjs that people can use.

[dyladan]

https://www.npmjs.com/package/@opentelemetry/api/v/1.2.0

[cartermp]

Heh, whoopsie. Hmm. Weird that it doesn't pop up when I search for it? https://www.npmjs.com/package/@opentelemetry/api (points to 1.1 for me)

[dyladan]

1.2 has the next tag until open-telemetry/opentelemetry-js#3192 is merged and released in order to avoid a situation where the latest API and SDK are not compatible.

[dyladan]

We're discussing merging the API and SDK repositories back into a single repo so we can link everything with lerna and release all at once in order to avoid this issue in the future. It will also help with developing new API features.

[cartermp]

Awesome, thank you! I will track that for now (my intent is to update docs for both otel and honeycomb once this is in place).

[cartermp]

👋🏻 noticed everything's been merged and released - is there anything else needed to get the tag updated for the API package?