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-dev): bump @opentelemetry/sdk-trace-base from 1.13.0 to 1.17.1 #415

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Oct 10, 2023

Bumps @opentelemetry/sdk-trace-base from 1.13.0 to 1.17.1.

Release notes

Sourced from @​opentelemetry/sdk-trace-base's releases.

v1.17.1

1.17.1

🐛 (Bug Fix)

  • fix(sdk-trace-base): BatchSpanProcessor flushes when maxExportBatchSize is reached #3958 @​nordfjord
  • fix(sdk-metrics): allow instrument names to contain '/' #4155
  • fix(sdk-metrics): prevent per-reader storages from keeping unreported accumulations in memory #4163 @​pichlermarc
    • fixes a memory leak which occurred when two or more MetricReader instances are registered to a MeterProvider
  • fix(sdk-metrics): do not report empty scopes and metrics #4135 @​pichlermarc
    • Instruments that were created, but did not have measurements will not be exported anymore
    • Meters (Scopes) that were created, but did not have any instruments with measurements under them will not be exported anymore.
  • fix(exporter-zipkin): round duration to the nearest int in annotations to be compliant with zipkin protocol #4167 @​FelipeEmerim

📚 (Refine Doc)

  • docs(contributing): added guidelines for adding benchmark tests #4169

🏠 (Internal)

  • test: added a performance benchmark test for span creation #4105
  • test: added a workflow to run performance benchmark tests automatically #4144

v1.17.0

SDK 1.17.0

🐛 (Bug Fix)

  • Revert "feat(api): add attributes argument to recordException API #4071"
    • This feature was an unintentional breaking change introduced with API 1.5.0
    • This PR updates all SDK packages to allow API 1.6.0, where this change has been reverted.

v1.16.0

SDK 1.16.0

[!WARNING] This release widened the range of the API peer dependency to include@opentelemetry/api@1.5.x, which introduced an unintentional breaking change. This change was rolled back in https://github.com/open-telemetry/opentelemetry-js/releases/tag/v1.17.0.

🚀 (Enhancement)

  • feat(sdk-metrics): implement MetricProducer specification #4007
  • feat: update PeriodicExportingMetricReader and PrometheusExporter to accept optional metric producers #4077 @​aabmass

🐛 (Bug Fix)

  • fix(exporter-zipkin): rounding duration to the nearest int to be compliant with zipkin protocol #4064 @​n0cloud
  • fix(sdk-metrics): metric names should be case-insensitive

📚 (Refine Doc)

... (truncated)

Changelog

Sourced from @​opentelemetry/sdk-trace-base's changelog.

1.17.1

🐛 (Bug Fix)

  • fix(sdk-trace-base): BatchSpanProcessor flushes when maxExportBatchSize is reached #3958 @​nordfjord
  • fix(sdk-metrics): allow instrument names to contain '/' #4155
  • fix(sdk-metrics): prevent per-reader storages from keeping unreported accumulations in memory #4163 @​pichlermarc
    • fixes a memory leak which occurred when two or more MetricReader instances are registered to a MeterProvider
  • fix(sdk-metrics): do not report empty scopes and metrics #4135 @​pichlermarc
    • Instruments that were created, but did not have measurements will not be exported anymore
    • Meters (Scopes) that were created, but did not have any instruments with measurements under them will not be exported anymore.
  • fix(exporter-zipkin): round duration to the nearest int in annotations to be compliant with zipkin protocol #4167 @​FelipeEmerim

📚 (Refine Doc)

  • docs(contributing): added guidelines for adding benchmark tests #4169

🏠 (Internal)

  • test: added a performance benchmark test for span creation #4105
  • test: added a workflow to run performance benchmark tests automatically #4144

1.17.0

🐛 (Bug Fix)

  • Revert "feat(api): add attributes argument to recordException API #4071"
    • This feature was an unintentional breaking change introduced with API 1.5.0
    • This PR updates all SDK packages to allow API 1.6.0, where this change has been reverted.

1.16.0

🚀 (Enhancement)

  • feat(sdk-metrics): implement MetricProducer specification #4007
  • feat: update PeriodicExportingMetricReader and PrometheusExporter to accept optional metric producers #4077 @​aabmass

🐛 (Bug Fix)

  • fix(exporter-zipkin): rounding duration to the nearest int to be compliant with zipkin protocol #4064 @​n0cloud
  • fix(sdk-metrics): metric names should be case-insensitive

📚 (Refine Doc)

  • docs(guidelines): add dependencies guidelines #4040

1.15.2

🐛 (Bug Fix)

... (truncated)

Commits
  • f8e187b chore: release SDK 1.17.1/Experimental 0.44.0 (#4183)
  • 4eb10f7 fix(sdk-metrics): prevent per-reader storages from keeping unreported accumul...
  • c320c98 deps: update proto-loader (#4192)
  • 5fd3737 chore: remove outdated and empty docs (#4181)
  • 84861cd chore(deps): update dependency @​types/jquery to v3.5.21 (#4187)
  • 9122561 fix: BatchExporter should export continuously when batch size is reached (#3958)
  • 5ce32c0 Added performance benchmarking doc (#4169)
  • 5af8653 chore(deps): update dependency @​types/sinon to v10.0.18 (#4179)
  • 868f75e fix(benchmark): write benchmark results to file (#4172)
  • c84698d Benchmark tests workflow (#4144)
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by pichlermarc, a new releaser for @​opentelemetry/sdk-trace-base since your current version.


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/sdk-trace-base](https://github.com/open-telemetry/opentelemetry-js) from 1.13.0 to 1.17.1.
- [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@v1.13.0...v1.17.1)

---
updated-dependencies:
- dependency-name: "@opentelemetry/sdk-trace-base"
  dependency-type: direct:development
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Oct 10, 2023
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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants