Skip to content
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

chore(deps): bump @opentelemetry/instrumentation-http from 0.51.1 to 0.52.0 #153

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jun 10, 2024

Bumps @opentelemetry/instrumentation-http from 0.51.1 to 0.52.0.

Release notes

Sourced from @​opentelemetry/instrumentation-http's releases.

experimental/v0.52.0

0.52.0

💥 Breaking Change

  • feat(exporter--otlp-)!: move serialization for Node.js exporters to @opentelemetry/otlp-transformer #4542 @​pichlermarc
    • Breaking changes:
      • (user-facing) convert() now returns an empty object and will be removed in a follow-up
      • (internal) OTLPExporterNodeBase now has additional constructor parameters that are required
      • (internal) OTLPExporterNodeBase now has an additional ResponseType type parameter
  • feat(exporter--otlp-)!: move serialization for Node.js exporters to @opentelemetry/otlp-transformer #4581 @​pichlermarc
    • Breaking changes:
      • (user-facing) convert() has been removed from all exporters
      • (internal) OTLPExporterBrowserBase: RequestType has been replaced by a ResponseType type-argument
      • (internal) OTLPExporterNodeBase: ServiceRequest has been replaced by a ServiceResponse type-argument
      • (internal) the @opentelemetry/otlp-exporter-proto-base package has been removed, and will from now on be deprecated in npm
  • feat(instrumentation): remove default value for config in base instrumentation constructor #4695: @​blumamir
  • fix(instrumentation)!: remove unused supportedVersions from Instrumentation interface #4694 @​blumamir
  • feat(instrumentation)!: simplify registerInstrumentations() API
    • Breaking changes:
      • removes InstrumentationOptions type
      • occurrences of InstrumentationOptions are now replaced by (Instrumentation | Instrumentation[])[]
        • migrate usages of registerInstrumentations({instrumentations: fooInstrumentation}) to registerInstrumentations({instrumentations: [fooInstrumentation]})
        • passing Instrumentation classes to registerInstrumentations() is now not possible anymore.
  • feat(sdk-node)!: simplify type of instrumentations option
    • Breaking changes:
      • replaces InstrumentationOptions with (Instrumentation | Instrumentation[])[]

🚀 (Enhancement)

  • feat(instrumentation): apply unwrap before wrap in base class #4692
  • feat(instrumentation): add util to execute span customization hook in base class #4663 @​blumamir
  • feat(instrumentation): generic config type in instrumentation base #4659 @​blumamir
  • feat: support node 22 #4666 @​dyladan
  • feat(propagator-aws-xray-lambda): add AWS Xray Lambda propagator 4554
  • refactor(instrumentation-xml-http-request): use exported strings for semantic attributes. #4681

🐛 (Bug Fix)

📚 (Refine Doc)

  • docs(instrumentation): better docs for supportedVersions option #4693 @​blumamir
  • docs: align all supported versions to a common format #4696 @​blumamir
  • refactor(examples): use new exported string constants for semconv in experimental/examples/opencensus-shim #4763 @​Zen-cronic
Commits
  • c4d3351 fix(sdk-logs): adapt versions for release (#4769)
  • 26974c4 chore: prepare release API 1.9.0/Core 1.25.0/Experimental 0.52.0 (#4677)
  • 957fa3b refactor(examples/esm-http-ts): use new exported string constants for semconv...
  • 97d0ec5 refactor(examples/basic-tracer-node): use new exported string constants for s...
  • 929e345 refactor(examples/grpc-js): use new exported string constants for semconv (#4...
  • 97f372b refactor(experimental/examples/opencensus-shim): use new exported string cons...
  • 9cd2021 refactor(examples/otlp-exporter-node): use new exported string constants for ...
  • de50349 refactor(examples/opentracing-shim): use new exported string constants for se...
  • 7c808e3 add Events SDK (#4629)
  • 9d3bc18 chore: move flarna from approver to emeritus (#4757)
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [@opentelemetry/instrumentation-http](https://github.com/open-telemetry/opentelemetry-js) from 0.51.1 to 0.52.0.
- [Release notes](https://github.com/open-telemetry/opentelemetry-js/releases)
- [Changelog](https://github.com/open-telemetry/opentelemetry-js/blob/main/CHANGELOG.md)
- [Commits](open-telemetry/opentelemetry-js@experimental/v0.51.1...experimental/v0.52.0)

---
updated-dependencies:
- dependency-name: "@opentelemetry/instrumentation-http"
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Jun 10, 2024
@dependabot dependabot bot requested a review from saidsef June 10, 2024 23:52
@saidsef
Copy link
Owner

saidsef commented Jun 12, 2024

/code pr

Copy link
Owner

@saidsef saidsef left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖

Review Summary

The PR updates the @opentelemetry/instrumentation-http dependency from version 0.51.1 to 0.52.0. The changes are reflected in both package-lock.json and package.json.

Files Reviewed

package-lock.json

  • Version Update: The version of @opentelemetry/instrumentation-http is updated from 0.51.1 to 0.52.0.
  • Dependencies Update: The dependencies for @opentelemetry/instrumentation-http have been updated to:
    • @opentelemetry/core from 1.24.1 to 1.25.0
    • @opentelemetry/instrumentation from 0.51.1 to 0.52.0
    • @opentelemetry/semantic-conventions from 1.24.1 to 1.25.0
  • New Dependencies: Several new dependencies have been added under @opentelemetry/instrumentation-http:
    • @opentelemetry/api-logs version 0.52.0
    • import-in-the-middle version 1.8.0
    • require-in-the-middle version 7.1.1
    • shimmer version 1.2.1

package.json

  • Version Update: The version of @opentelemetry/instrumentation-http is updated from 0.51.0 to 0.52.0.

Recommendations

  • Testing: Ensure that the application is thoroughly tested after this dependency update to confirm that there are no breaking changes or regressions.
  • Documentation: If there are any significant changes in the new version of @opentelemetry/instrumentation-http, consider updating the project documentation to reflect these changes.

Conclusion

The PR is straightforward and primarily involves updating a dependency to a newer version. The changes are well-contained and should be safe, provided that adequate testing is performed.

> gpt-4o [pr | 1]

Copy link
Contributor Author

dependabot bot commented on behalf of github Jun 14, 2024

Looks like @opentelemetry/instrumentation-http is up-to-date now, so this is no longer needed.

@dependabot dependabot bot closed this Jun 14, 2024
@dependabot dependabot bot deleted the dependabot-npm_and_yarn-opentelemetry-instrumentation-http-0.52.0 branch June 14, 2024 06:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant