-
Notifications
You must be signed in to change notification settings - Fork 486
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
bump all dependencies to trigger release for dependency updates in autoinstrumentation/nodejs #2754
bump all dependencies to trigger release for dependency updates in autoinstrumentation/nodejs #2754
Conversation
c7c68fe
to
d1eac48
Compare
@pavolloffay, all checks are green, can you merge it? |
@atsu85 could you please remove the changelog |
Sure. Initially i didn't have it, but build pipeline failed, so i included it as it seemed to be present on other release PRs as well (example) |
To trigger release for open-telemetry#2622 that already bumped auto-instrumentations-node via open-telemetry#2745
d1eac48
to
82dfeea
Compare
@pavolloffay, removed the changelog |
@TylerHelmuth, thanks for approving this PR! |
@pavolloffay, thanks for merging this PR! @pavolloffay, @TylerHelmuth, could you also review #2767 that is needed for releasing the operator? |
…toinstrumentation/nodejs (open-telemetry#2754) * Bump all NodeJS devDependences to latest versions * Bump all NodeJS dependences to latest versions To trigger release for open-telemetry#2622 that already bumped auto-instrumentations-node via open-telemetry#2745
Description:
Bump NodeJS dependencies
Link to tracking Issue(s):
@opentelemetry/auto-instrumentations-node
to allow enabling only selected instrumentations via env #2745Testing:
dependencies
that affect the runtime are semver minor or patch-level, so shouldn't break consumersdevDependencies
contain also semver major-level, but those are not included in runtime, so shouldn't break consumers.