[Snyk] Upgrade @opentelemetry/semantic-conventions from 1.24.1 to 1.25.1

[hashim21223445]

Snyk has created this PR to upgrade @opentelemetry/semantic-conventions from 1.24.1 to 1.25.1.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

• The recommended version is 2 versions ahead of your current version.

• The recommended version was released on a month ago.

Issues fixed by the recommended upgrade:

	Issue	Score	Exploit Maturity
	Uncontrolled resource consumption SNYK-JS-BRACES-6838727	169	Proof of Concept
	Inefficient Regular Expression Complexity SNYK-JS-MICROMATCH-6838728	169	No Known Exploit
	Uncontrolled Resource Consumption SNYK-JS-GRPCGRPCJS-7242922	169	No Known Exploit

Release notes

Package name: @opentelemetry/semantic-conventions

• 1.25.1 - 2024-06-20
  

  1.25.1

  📚 (Refine Doc)

  • refactor(examples): added usage of @ opentelemetry/semantic-conventions and @ opentelemetry/resources to the examples in examples/opentelemetry-web for maintaining consistency across all examples. #4764 @ Zen-cronic

  🏠 (Internal)

  • refactor(context-zone-peer-dep): use explicit exports #4785 @ pichlermarc
  • refactor(context-async-hooks): use explicit exports #4785 @ pichlermarc
• 1.25.0 - 2024-06-05
  

  1.25.0

  🚀 (Enhancement)

  • feat: support node 22 #4666 @ dyladan
  • feat(context-zone*): support zone.js 0.12.x #4376 @ maldago
  • refactor(core): Use tree-shakeable string constants for semconv #4739 @ JohannesHuster
  • refactor(shim-opentracing): Use tree-shakeable string constants for semconv #4746 @ JohannesHuster
  • refactor(sdk-trace-web): Use tree-shakeable string constants for semconv #4747 @ JohannesHuster
  • refactor(sdk-trace-node): Use tree-shakeable string constants for semconv #4748 @ JohannesHuster
  • refactor(sdk-trace-base): Use tree-shakeable string constants for semconv #4749 @ JohannesHuster
  • refactor(resources): update deprecated semconv to use exported strings #4755 @ JamieDanielson
  • refactor(exporters): update deprecated semconv to use exported strings #4756 @ JamieDanielson

  📚 (Refine Doc)

  • refactor(examples): use new exported string constants for semconv in examples/esm-http-ts #4758 @ Zen-cronic
  • refactor(examples): use new exported string constants for semconv in examples/basic-tracer-node #4759 @ Zen-cronic
  • refactor(examples): use new exported string constants for semconv in examples/http #4750 @ Zen-cronic
  • refactor(examples): use new exported string constants for semconv in examples/grpc-js #4760 @ Zen-cronic
  • refactor(examples): use new exported string constants for semconv in examples/otlp-exporter-node #4762 @ Zen-cronic
  • refactor(examples): use new exported string constants for semconv in examples/opentracing-shim #4761 @ Zen-cronic
• 1.24.1 - 2024-05-07
  

  1.24.1

  🐛 (Bug Fix)

  • fix(core): align inconsistent behavior of getEnv() and getEnvWithoutDefaults() when a process polyfill is used #4648 @ pichlermarc
    • getEnvWithoutDefaults() would use process.env if it was defined when running in a browser, while getEnv() would always use _globalThis. Now both use _globalThis when running in a browser.
  • fix(resources): prevent circular import (resource -> detector -> resource -> ...) #4653 @ pichlermarc
    • fixes a circular import warning which would appear in rollup when bundling @ opentelemetry/resources
  • fix(exporter-metrics-otlp-grpc): add explicit otlp-exporter-base dependency to exporter-metrics-otlp-grpc #4678 @ AkselAllas

from @opentelemetry/semantic-conventions GitHub release notes

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• This PR was automatically created by Snyk using the credentials of a real user.
• Max score is 1000. Note that the real score may have changed since the PR was raised.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

• 🧐 View latest project report
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs