chore: add prepublishOnly to ensure a full build

[legendecas]

Which problem is this PR solving?

Fixes: #2843

Add npm script prepublishOnly to run a full build before publishing. prepare may be a good alternative but it also runs on npm install -- it may slow down the install step.

These build variants have already been tested in our GitHub Action suites.

Refs: https://docs.npmjs.com/cli/v8/using-npm/scripts#life-cycle-operation-order

Short description of the changes

• Also add the missing esnext config for propagator-jaeger and the template package.
• Update dependency @opentelemetry/api of @opentelemetry/sdk-node to ~1.1.0.

Type of change

• Bug fix (non-breaking change which fixes an issue)

Checklist:

• Followed the style guidelines of this project

[codecov]

Codecov Report

Merging #2844 (45ac10f) into main (8182dab) will increase coverage by 1.32%.
The diff coverage is n/a.

❗ Current head 45ac10f differs from pull request most recent head 9745804. Consider uploading reports for the commit 9745804 to get more accurate results

@@            Coverage Diff             @@
##             main    #2844      +/-   ##
==========================================
+ Coverage   93.52%   94.85%   +1.32%     
==========================================
  Files         163       16     -147     
  Lines        5572      602    -4970     
  Branches     1180      107    -1073     
==========================================
- Hits         5211      571    -4640     
+ Misses        361       31     -330     

Impacted Files	Coverage Δ
...emetry-api-metrics/src/platform/node/globalThis.ts	0.00% <0.00%> (-100.00%)	⬇️
packages/opentelemetry-core/src/utils/merge.ts
...strumentation/src/platform/node/instrumentation.ts
...ics-base/src/exemplar/NeverSampleExemplarFilter.ts
...emetry-sdk-metrics-base/src/state/MetricStorage.ts
...ges/opentelemetry-resources/src/detectors/index.ts
...kages/opentelemetry-core/src/trace/rpc-metadata.ts
...metry-sdk-metrics-base/src/InstrumentDescriptor.ts
packages/opentelemetry-core/src/utils/callback.ts
...ackages/opentelemetry-shim-opentracing/src/shim.ts
... and 138 more

[legendecas]

The test is failing. It seems like the gcp-detector is not behaving in an expected way...

[legendecas]

Well, it seems the problem is related to @opentelemetry/api version mismatch: @opentelemetry/sdk-node uses ~1.0.3, whilst @opentelemetry/resource-detector-gcp uses v1.1.0 (^1.0.2)

[vmarchaud]

I think we might consider moving the sdk node to the contrib since all detectors live there

[legendecas]

I believe we'll need a version bump on dependencies of experimental packages to get the CI working.

Edit: well, no need to do so. We have only @opentelemetry/sdk-node that uses ~1.0.3 notation on @opentelemetry/api.

[Flarna]

What is the main difference between compile and publishOnly script?

[legendecas]

@Flarna What is the main difference between compile and publishOnly script?

The publishOnly is an npm hook that is executed before the npm publish command (See https://docs.npmjs.com/cli/v8/using-npm/scripts#life-cycle-operation-order for more details), while compile is not an npm hooks.

I'd wait for @dyladan 's opinion on this since he is the one who performs the releases.

[Flarna]

Isn't it prepublishOnly?

[legendecas]

@Flarna thank you for pointing that out! That was a silly mistake I've made :(

[dyladan]

Thanks for adding this. We'll have to cut a 1.1.1 release to fix the release ASAP

[dyladan]

I'd wait for @dyladan 's opinion on this since he is the one who performs the releases.

I'm working locally on a branch to automate the releases as I don't want to do it forever