chore(release): script to align workspace on new semconv package version

[trentm]

This is to be used as part of the semconv release process.

Refs: #4904

[trentm]

@JamieDanielson ./scripts/align-semconv-deps.js will do the thing. Where should this fit into the various package.json scripts for the semconv release process?

Example running it in a checkout of #4936:

Updating semconv dep in 20 workspace dirs:
 $ cd packages/opentelemetry-core && npm install --save-exact @opentelemetry/semantic-conventions@1.26.0
 $ cd packages/opentelemetry-exporter-jaeger && npm install --save-exact @opentelemetry/semantic-conventions@1.26.0
 $ cd packages/opentelemetry-exporter-zipkin && npm install --save-exact @opentelemetry/semantic-conventions@1.26.0
 $ cd packages/opentelemetry-resources && npm install --save-exact @opentelemetry/semantic-conventions@1.26.0
 $ cd packages/opentelemetry-sdk-trace-base && npm install --save-exact @opentelemetry/semantic-conventions@1.26.0
 $ cd packages/opentelemetry-sdk-trace-node && npm install --save-exact @opentelemetry/semantic-conventions@1.26.0
 $ cd packages/opentelemetry-sdk-trace-web && npm install --save-exact @opentelemetry/semantic-conventions@1.26.0
 $ cd packages/opentelemetry-shim-opentracing && npm install --save-exact @opentelemetry/semantic-conventions@1.26.0
 $ cd experimental/packages/opentelemetry-exporter-prometheus && npm install --save-exact @opentelemetry/semantic-conventions@1.26.0
 $ cd experimental/packages/opentelemetry-instrumentation-fetch && npm install --save-exact @opentelemetry/semantic-conventions@1.26.0
 $ cd experimental/packages/opentelemetry-instrumentation-grpc && npm install --save-exact @opentelemetry/semantic-conventions@1.26.0
 $ cd experimental/packages/opentelemetry-instrumentation-http && npm install --save-exact @opentelemetry/semantic-conventions@1.26.0
 $ cd experimental/packages/opentelemetry-instrumentation-xml-http-request && npm install --save-exact @opentelemetry/semantic-conventions@1.26.0
 $ cd experimental/packages/opentelemetry-sdk-node && npm install --save-exact @opentelemetry/semantic-conventions@1.26.0
 $ cd experimental/examples/opencensus-shim && npm install --save-exact @opentelemetry/semantic-conventions@1.26.0
 $ cd examples/otlp-exporter-node && npm install --save-exact @opentelemetry/semantic-conventions@1.26.0
 $ cd examples/opentelemetry-web && npm install --save-exact @opentelemetry/semantic-conventions@1.26.0
 $ cd examples/http && npm install --save-exact @opentelemetry/semantic-conventions@1.26.0
 $ cd examples/https && npm install --save-exact @opentelemetry/semantic-conventions@1.26.0
 $ cd examples/esm-http-ts && npm install --save-exact @opentelemetry/semantic-conventions@1.26.0

[JamieDanielson]

Where should this fit into the various package.json scripts for the semconv release process?

I believe these will go into the prepare_release:semconv:ver scripts in the root package.json:

-    "prepare_release:semconv:patch": "npm run _check:no_changes && npm run _backup:package-json && npm run _lerna:remove_everything_except_semconv && npm run _lerna:version_patch && npm run _restore:package-json && npm run _changelog:prepare_semconv",
-    "prepare_release:semconv:minor": "npm run _check:no_changes && npm run _backup:package-json && npm run _lerna:remove_everything_except_semconv && npm run _lerna:version_minor && npm run _restore:package-json && npm run _changelog:prepare_semconv",
+    "prepare_release:semconv:patch": "npm run _check:no_changes && npm run _backup:package-json && npm run _lerna:remove_everything_except_semconv && npm run _lerna:version_patch && lerna run align-semconv-deps && npm run _restore:package-json && npm run _changelog:prepare_semconv",
+    "prepare_release:semconv:minor": "npm run _check:no_changes && npm run _backup:package-json && npm run _lerna:remove_everything_except_semconv && npm run _lerna:version_minor && lerna run align-semconv-deps && npm run _restore:package-json && npm run _changelog:prepare_semconv",

and then every package.json, below the align-api-deps script:

-    "align-api-deps": "node ../../scripts/align-api-deps.js"
+    "align-api-deps": "node ../../scripts/align-api-deps.js",
+    "align-semconv-deps": "node ../../scripts/align-semconv-deps.js"

EDIT: Re-reading this more closely, I had this wrong. Ignore the previous above comment for now 😅

[trentm]

REviewer note, the package-lock was slightly unsync'd. Here is the clean update to package-lock:

diff --git a/package-lock.json b/package-lock.json
index 03d754ec0..6e75249ed 100644
--- a/package-lock.json
+++ b/package-lock.json
@@ -2045,6 +2045,9 @@
       "dependencies": {
         "@opentelemetry/api-logs": "0.52.1",
         "@opentelemetry/core": "1.25.1",
+        "@opentelemetry/exporter-logs-otlp-grpc": "0.52.1",
+        "@opentelemetry/exporter-logs-otlp-http": "0.52.1",
+        "@opentelemetry/exporter-logs-otlp-proto": "0.52.1",
         "@opentelemetry/exporter-trace-otlp-grpc": "0.52.1",
         "@opentelemetry/exporter-trace-otlp-http": "0.52.1",
         "@opentelemetry/exporter-trace-otlp-proto": "0.52.1",
@@ -36903,6 +36906,9 @@
         "@opentelemetry/context-async-hooks": "1.25.1",
         "@opentelemetry/core": "1.25.1",
         "@opentelemetry/exporter-jaeger": "1.25.1",
+        "@opentelemetry/exporter-logs-otlp-grpc": "0.52.1",
+        "@opentelemetry/exporter-logs-otlp-http": "0.52.1",
+        "@opentelemetry/exporter-logs-otlp-proto": "0.52.1",
         "@opentelemetry/exporter-trace-otlp-grpc": "0.52.1",
         "@opentelemetry/exporter-trace-otlp-http": "0.52.1",
         "@opentelemetry/exporter-trace-otlp-proto": "0.52.1",

[JamieDanielson]

🎉