test(integration-w3c): fix inconsistent api versions loaded #2752
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Which problem is this PR solving?
In the latest changes, one of the package.json is changed and triggered cache invalidations at https://github.com/open-telemetry/opentelemetry-js/blob/main/.github/workflows/w3c-integration-test.yml#L28 and installed @opentelemtry/api with different versions for private package propagation-validation-server (^1.0.3) and lerna package @opentelemtry/sdk-trace-base (~1.0.3 in dev dependencies). Lerna treats this inconsistent semver mark as incompatible semvers and installs different versions for each package.
This leads to the failure of registration of BasicTracerProvider for https://github.com/open-telemetry/opentelemetry-js-api/blob/main/src/internal/global-utils.ts#L53.
Short description of the changes
propagation-validation-server
to~1.0.3
.Type of change
Checklist: