maint(deps): bump the example-deps group across 1 directory with 3 updates

[dependabot]

Bumps the example-deps group with 3 updates in the /packages/honeycomb-opentelemetry-web/examples/hello-world-web directory: @opentelemetry/auto-instrumentations-web, @opentelemetry/context-zone and esbuild.

Updates @opentelemetry/auto-instrumentations-web from 0.40.0 to 0.41.0

Commits

• b31df37 chore: release main (#2083)
• f3406ea chore: remove patch and unpatch diag from instrumentations (#2107)
• 73e01f2 chore(examples/graphql): use exported strings for attributes (#2122)
• 80cbee7 chore: experimental 0.51.0, remove instrumentations generic type to align wit...
• 46b6775 test(instr-document-load): fix test to allow missing network span events (#2145)
• 931318c refactor(instr-aws-sdk): use exported strings for attributes (#2142)
• 77452c1 chore(examples/connect): use exported strings for attributes (#2120)
• 5f1910b chore(examples/web): use exported strings for attributes (#2129)
• 0d38081 docs: remove key column on readme (#2132)
• 2d709ec chore(instrumentation-fs): remove unused semconv package (#2141)
• Additional commits viewable in compare view

Updates @opentelemetry/context-zone from 1.25.1 to 1.26.0

Release notes

Sourced from @​opentelemetry/context-zone's releases.

semconv/v1.26.0

@opentelemetry/[email protected]

Note: This package will now be versioned according to the version of semantic conventions being provided.

🚀 (Enhancement)

• feat(semconv): update semantic conventions to 1.27 (from 1.7.0) #4690 @​dyladan
  • Exported names have changed to ATTR_{name} for attributes (e.g. ATTR_HTTP_REQUEST_METHOD), {name}_VALUE_{value} for enumeration values (e.g. HTTP_REQUEST_METHOD_VALUE_POST), and METRIC_{name} for metrics. Exported names from previous versions are deprecated.
  • Import @opentelemetry/semantic-conventions for stable semantic conventions. Import @opentelemetry/semantic-conventions/incubating for all semantic conventions, stable and unstable.

v1.26.0

1.26.0

🚀 (Enhancement)

• feat: include instrumentation scope info in console span and log record exporters #4848 @​blumamir
• feat(semconv): update semantic conventions to 1.27 (from 1.7.0) #4690 @​dyladan
  • Exported names have changed to ATTR_{name} for attributes (e.g. ATTR_HTTP_REQUEST_METHOD), {name}_VALUE_{value} for enumeration values (e.g. HTTP_REQUEST_METHOD_VALUE_POST), and METRIC_{name} for metrics. Exported names from previous versions are deprecated.
  • Import @opentelemetry/semantic-conventions for stable semantic conventions. Import @opentelemetry/semantic-conventions/incubating for all semantic conventions, stable and unstable.
  • Note: Semantic conventions are now versioned separately from other stable artifacts, to correspond to the version of semantic conventions they provide. Changes will be in a separate changelog.

🐛 (Bug Fix)

• fix(sdk-node): avoid spurious diag errors for unknown OTEL_NODE_RESOURCE_DETECTORS values #4879 @​trentm
• deps(opentelemetry-instrumentation): Bump shimmer types to 1.2.0 #4865 @​lforst
• fix(instrumentation): Fix optional property types #4833 @​alecmev
• fix(sdk-metrics): fix(sdk-metrics): use inclusive upper bounds in histogram #4829

🏠 (Internal)

• refactor: Simplify the code for the getEnv function #4799 @​danstarns
• refactor: remove "export *" in favor of explicit named exports #4880 @​robbkidd
  • Packages updated:
    • opentelemetry-context-zone
    • opentelemetry-core
    • opentelemetry-exporter-jaeger
    • opentelemetry-exporter-zipkin
    • opentelemetry-propagator-b3
    • opentelemetry-propagator-jaeger
    • opentelemetry-sdk-trace-base
    • opentelemetry-sdk-trace-node
    • opentelemetry-sdk-trace-web
    • propagator-aws-xray
    • sdk-metrics
• deps(sdk-metrics): remove unused lodash.merge dependency #4905 @​pichlermarc

Changelog

Sourced from @​opentelemetry/context-zone's changelog.

1.26.0

🚀 (Enhancement)

• feat: include instrumentation scope info in console span and log record exporters #4848 @​blumamir
• feat(semconv): update semantic conventions to 1.27 (from 1.7.0) #4690 @​dyladan
  • Exported names have changed to ATTR_{name} for attributes (e.g. ATTR_HTTP_REQUEST_METHOD), {name}_VALUE_{value} for enumeration values (e.g. HTTP_REQUEST_METHOD_VALUE_POST), and METRIC_{name} for metrics. Exported names from previous versions are deprecated.
  • Import @opentelemetry/semantic-conventions for stable semantic conventions. Import @opentelemetry/semantic-conventions/incubating for all semantic conventions, stable and unstable.
  • Note: Semantic conventions are now versioned separately from other stable artifacts, to correspond to the version of semantic conventions they provide. Changes will be in a separate changelog.

🐛 (Bug Fix)

• fix(sdk-node): avoid spurious diag errors for unknown OTEL_NODE_RESOURCE_DETECTORS values #4879 @​trentm
• deps(opentelemetry-instrumentation): Bump shimmer types to 1.2.0 #4865 @​lforst
• fix(instrumentation): Fix optional property types #4833 @​alecmev
• fix(sdk-metrics): fix(sdk-metrics): use inclusive upper bounds in histogram #4829

🏠 (Internal)

• refactor: Simplify the code for the getEnv function #4799 @​danstarns
• refactor: remove "export *" in favor of explicit named exports #4880 @​robbkidd
  • Packages updated:
    • opentelemetry-context-zone
    • opentelemetry-core
    • opentelemetry-exporter-jaeger
    • opentelemetry-exporter-zipkin
    • opentelemetry-propagator-b3
    • opentelemetry-propagator-jaeger
    • opentelemetry-sdk-trace-base
    • opentelemetry-sdk-trace-node
    • opentelemetry-sdk-trace-web
    • propagator-aws-xray
    • sdk-metrics
• deps(sdk-metrics): remove unused lodash.merge dependency #4905 @​pichlermarc

Commits

• 720bc8c chore: prepare next release (#4960)
• 65cedf7 chore: prepare next release (#4949)
• bd25230 docs: document console exporter output stability (#4956)
• 948496d chore: pin unit test to node 22.6 until 22.8 is available (#4957)
• 966ac17 docs: Describe support for ESM (#4876)
• 2ca2459 test(exporter-logs-otlp-grpc): improve error reporting in particular test fai...
• c398601 feat(jaeger-remote-sampler): Implement jaeger remote sampler (#4589)
• 3cf1c52 chore: prepare next release (#4939)
• 5578a11 chore: sync package-lock.json (#4947)
• 5c1ae0a docs(sdk-metrics): Update Histogram docs to reflect upper bound inclusivity (...
• Additional commits viewable in compare view

Updates esbuild from 0.23.0 to 0.23.1

Release notes

Sourced from esbuild's releases.

v0.23.1

• Allow using the node: import prefix with es* targets (#3821)

  The node: prefix on imports is an alternate way to import built-in node modules. For example, import fs from "fs" can also be written import fs from "node:fs". This only works with certain newer versions of node, so esbuild removes it when you target older versions of node such as with --target=node14 so that your code still works. With the way esbuild's platform-specific feature compatibility table works, this was added by saying that only newer versions of node support this feature. However, that means that a target such as --target=node18,es2022 removes the node: prefix because none of the es* targets are known to support this feature. This release adds the support for the node: flag to esbuild's internal compatibility table for es* to allow you to use compound targets like this:

  // Original code
  import fs from 'node:fs'
  fs.open
  // Old output (with --bundle --format=esm --platform=node --target=node18,es2022)
  import fs from "fs";
  fs.open;
  // New output (with --bundle --format=esm --platform=node --target=node18,es2022)
  import fs from "node:fs";
  fs.open;

• Fix a panic when using the CLI with invalid build flags if --analyze is present (#3834)

  Previously esbuild's CLI could crash if it was invoked with flags that aren't valid for a "build" API call and the --analyze flag is present. This was caused by esbuild's internals attempting to add a Go plugin (which is how --analyze is implemented) to a null build object. The panic has been fixed in this release.

• Fix incorrect location of certain error messages (#3845)

  This release fixes a regression that caused certain errors relating to variable declarations to be reported at an incorrect location. The regression was introduced in version 0.18.7 of esbuild.

• Print comments before case clauses in switch statements (#3838)

  With this release, esbuild will attempt to print comments that come before case clauses in switch statements. This is similar to what esbuild already does for comments inside of certain types of expressions. Note that these types of comments are not printed if minification is enabled (specifically whitespace minification).

• Fix a memory leak with pluginData (#3825)

  With this release, the build context's internal pluginData cache will now be cleared when starting a new build. This should fix a leak of memory from plugins that return pluginData objects from onResolve and/or onLoad callbacks.

Changelog

Sourced from esbuild's changelog.

0.23.1

• Allow using the node: import prefix with es* targets (#3821)

  The node: prefix on imports is an alternate way to import built-in node modules. For example, import fs from "fs" can also be written import fs from "node:fs". This only works with certain newer versions of node, so esbuild removes it when you target older versions of node such as with --target=node14 so that your code still works. With the way esbuild's platform-specific feature compatibility table works, this was added by saying that only newer versions of node support this feature. However, that means that a target such as --target=node18,es2022 removes the node: prefix because none of the es* targets are known to support this feature. This release adds the support for the node: flag to esbuild's internal compatibility table for es* to allow you to use compound targets like this:

  // Original code
  import fs from 'node:fs'
  fs.open
  // Old output (with --bundle --format=esm --platform=node --target=node18,es2022)
  import fs from "fs";
  fs.open;
  // New output (with --bundle --format=esm --platform=node --target=node18,es2022)
  import fs from "node:fs";
  fs.open;

• Fix a panic when using the CLI with invalid build flags if --analyze is present (#3834)

  Previously esbuild's CLI could crash if it was invoked with flags that aren't valid for a "build" API call and the --analyze flag is present. This was caused by esbuild's internals attempting to add a Go plugin (which is how --analyze is implemented) to a null build object. The panic has been fixed in this release.

• Fix incorrect location of certain error messages (#3845)

  This release fixes a regression that caused certain errors relating to variable declarations to be reported at an incorrect location. The regression was introduced in version 0.18.7 of esbuild.

• Print comments before case clauses in switch statements (#3838)

  With this release, esbuild will attempt to print comments that come before case clauses in switch statements. This is similar to what esbuild already does for comments inside of certain types of expressions. Note that these types of comments are not printed if minification is enabled (specifically whitespace minification).

• Fix a memory leak with pluginData (#3825)

  With this release, the build context's internal pluginData cache will now be cleared when starting a new build. This should fix a leak of memory from plugins that return pluginData objects from onResolve and/or onLoad callbacks.

Commits

• 3327274 publish 0.23.1 to npm
• 38e22ed add a warning/debug log message for #3867
• a15bb51 fix #3825: memory leak of pluginData values
• f6e6481 fix #3838: print comments before case clauses
• 9c13ae1 fix #3853: update go 1.22.4 => 1.22.5
• 78f89e4 fix #3845: some incorrect error message locations
• 892d2a7 fix #3834: cli sometimes panics with --analyze
• 360d472 fix a typo in the release notes
• e3f4e2d fix #3821: allow node: prefix with es* targets
• See full diff in compare view

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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[wolfgangcodes]

@dependabot squash and merge