Skip to content

build(deps-dev): bump the npm-development group with 3 updates - #243

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/npm-development-3c387fde65
Closed

build(deps-dev): bump the npm-development group with 3 updates#243
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/npm-development-3c387fde65

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 30, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Bumps the npm-development group with 3 updates: @biomejs/biome, @opentelemetry/exporter-metrics-otlp-grpc and @opentelemetry/otlp-transformer.

Updates @biomejs/biome from 2.5.15 to 2.6.2

Release notes

Sourced from @​biomejs/biome's releases.

Biome CLI v2.6.2

2.6.2

Minor Changes

  • #11479 5c60ba8 Thanks @​nhedger! - Added a --git flag to biome init. The flag enables Git VCS integration and sets vcs.useIgnoreFile to true in the generated configuration, even when the command runs outside a Git repository.

  • #11742 3a1356d Thanks @​Netail! - Added the biome migrate stylelint command. It imports a Stylelint configuration and its ignore settings into your Biome configuration, mapping Stylelint rules to their Biome equivalents. Pass --write to apply the changes, and --include-inspired or --include-nursery to migrate additional rules.

  • #12318 774b5b5 Thanks @​Netail! - Added the new assist action useGraphqlSortedDefinitions, which sorts the named definitions of a GraphQL document, such as types, type extensions, directives, fragments, and operations.

    Invalid:

    type User {
  id: ID!
}
enum Role {
ADMIN
USER
}
directive @​auth on FIELD_DEFINITION

  • #6886 3479d15 Thanks @​christymcgrory! - biome rage now shows the resolved files.includes and files.ignoreUnknown configuration.

  • #11102 0874b7f Thanks @​gameroman! - Added support for useTailwindSortedClasses rule in HTML-ish files.

  • #10711 40de5a0 Thanks @​soconnor-seeq! - Adds a new resolutionKind option for object-syntax plugin entries.

    This allows shared Biome configs in monorepos to load local Grit plugins from the package that declares them instead of resolving plugin paths from the consuming project.

    {
  "plugins": [
    { "path": "./grit/no-debugger.grit", "resolutionKind": "config" },
    { "path": "local-plugin.grit", "resolutionKind": "project" },
    { "path": "local-plugin.grit" }
  ]
}

    Use resolutionKind: "config" to resolve the plugin from the configuration file that declares it. Use resolutionKind: "project" to resolve the plugin from the consuming project. When omitted, resolutionKind defaults to project. This only affects plugin resolution; includes still apply to end-user project files as usual.

  • #11432 4befd08 Thanks @​ematipico! - Added biome inspect config to show resolved configuration values and their origins as human-readable diagnostics, including matching overrides.

    Configuration files can also extend other configurations up to ten levels deep. Repeated references to the same resolved file are ignored with an information diagnostic, while resolving multiple versions of one extended package produces an error.

... (truncated)

Changelog

Sourced from @​biomejs/biome's changelog.

2.6.2

Patch Changes

2.6.1

Patch Changes

2.6.0

Minor Changes

  • #11479 5c60ba8 Thanks @​nhedger! - Added a --git flag to biome init. The flag enables Git VCS integration and sets vcs.useIgnoreFile to true in the generated configuration, even when the command runs outside a Git repository.

  • #11742 3a1356d Thanks @​Netail! - Added the biome migrate stylelint command. It imports a Stylelint configuration and its ignore settings into your Biome configuration, mapping Stylelint rules to their Biome equivalents. Pass --write to apply the changes, and --include-inspired or --include-nursery to migrate additional rules.

  • #12318 774b5b5 Thanks @​Netail! - Added the new assist action useGraphqlSortedDefinitions, which sorts the named definitions of a GraphQL document, such as types, type extensions, directives, fragments, and operations.

    Invalid:

    type User {
  id: ID!
}
enum Role {
ADMIN
USER
}
directive @​auth on FIELD_DEFINITION

  • #6886 3479d15 Thanks @​christymcgrory! - biome rage now shows the resolved files.includes and files.ignoreUnknown configuration.

  • #11102 0874b7f Thanks @​gameroman! - Added support for useTailwindSortedClasses rule in HTML-ish files.

  • #10711 40de5a0 Thanks @​soconnor-seeq! - Adds a new resolutionKind option for object-syntax plugin entries.

    This allows shared Biome configs in monorepos to load local Grit plugins from the package that declares them instead of resolving plugin paths from the consuming project.

    {
  "plugins": [
    { "path": "./grit/no-debugger.grit", "resolutionKind": "config" },
    { "path": "local-plugin.grit", "resolutionKind": "project" },

... (truncated)

Commits

Updates @opentelemetry/exporter-metrics-otlp-grpc from 0.222.0 to 0.300.0

Release notes

Sourced from @​opentelemetry/exporter-metrics-otlp-grpc's releases.

experimental/v0.300.0

0.300.0

Summary

  • The minimum supported Node.js has been raised to >=22.15.0. This means that support for Node.js 18 and 20 has been dropped.
  • The public interface has changed
  • Only stable versions 3.0.0 are compatible with this release

💥 Breaking Changes

  • chore(shim-opencensus)!: remove the @opentelemetry/shim-opencensus package
  • feat(instrumentation-http)!: remove deprecated serverName field from HttpInstrumentationConfig #7081
    • The serverName option had no effect; stable HTTP semantic conventions do not include http.server_name. Remove it from any setConfig() or constructor call.
  • feat(sdk-node)!: remove deprecated NodeSDKConfiguration fields logRecordProcessor, metricReader, spanProcessor and deprecated namespace re-exports node, tracing
    • NodeSDKConfiguration.logRecordProcessor — use logRecordProcessors instead.
    • NodeSDKConfiguration.metricReader — use metricReaders instead.
    • NodeSDKConfiguration.spanProcessor — use spanProcessors instead.
    • export * as node from '@opentelemetry/sdk-node' — import directly from @opentelemetry/sdk-trace-node instead.
    • export * as tracing from '@opentelemetry/sdk-node' — import directly from @opentelemetry/sdk-trace-base instead.
  • feat(sdk-logs)!: remove deprecated SdkLogRecord type alias and LoggerProviderConfig type alias #7062
    • SdkLogRecord — use ReadWriteLogRecord instead.
    • LoggerProviderConfig — use LoggerProviderOptions instead.
  • feat!: migrate package builds from tsc to tsdown, emitting dual CJS/ESM output from a single dist/ directory and declaring an exports map on every package #6293 @​overbalance
    • Importing a package by its name is unaffected in both CommonJS and ESM, as is every subpath listed in its exports map.
    • Deep imports into the build output no longer resolve. An exports map is an allowlist that Node.js and bundlers enforce, so specifiers such as @opentelemetry/sdk-logs/build/src/... or @opentelemetry/sdk-logs/build/esm/... now fail with ERR_PACKAGE_PATH_NOT_EXPORTED. Rewriting them to the new file layout does not help — unlisted subpaths are rejected whether or not the file exists.
    • The emitted files moved out of build/src (CJS), build/esm and build/esnext (ESM) into dist/, using .cjs/.mjs extensions with matching .d.cts/.d.mts declarations.
    • <package>/package.json is no longer importable for the same reason. Read a package's version from your own dependency metadata, or use SDK_INFO from @opentelemetry/core for the SDK version.
    • The non-standard esnext entry point has been removed; tools that preferred it fall back to module (ESM) or main (CJS).
    • Packages that ship separate Node.js and browser implementations export them under explicit subpaths, for example @opentelemetry/sdk-logs/platform. If you depend on something that is only reachable through a deep import, please open an issue so it can be considered for the public API.
  • feat(sdk-node)!: remove "jaeger" propagator from @opentelemetry/sdk-node #7077
    • OTEL_PROPAGATORS=jaeger and { jaeger: null } in the configuration object are no longer recognised. Replace with "tracecontext".
    • See the 3.x migration guide for full instructions.
  • fix(opentelemetry-exporter-prometheus)!: default exporter host to localhost #6599 @​cjihrig
  • chore!: bump minimum node.js version to >=22.15.0
  • feat(api-logs)!: move the Logs API to @opentelemetry/api and remove the standalone @opentelemetry/api-logs package #4862 @​hectorhdzg
  • fix(exporter-prometheus)!: stop reading Prometheus exporter host and port environment variables in the exporter constructor #6966 @​LarryHu0217
  • chore(web-common)!: clean up and deprecate network span utils #7114
    • These utilities were long planned for removal. They were moved from the sdk-trace-web package and are currently only used by the (deprecated) instrumentation-fetch and instrumentation-xml-http-request packages.
    • Drop the skipOldSemconvContentLengthAttrs vestigial option from addSpanNetworkEvents().
  • feat(sdk-node)!: drop SDK package re-exports (api, contextBase, core, logs, metrics, resources) #7111 @​pichlermarc
    • api / contextBase → import from @opentelemetry/api
    • core → import from @opentelemetry/core
    • logs → import from @opentelemetry/sdk-logs
    • metrics → import from @opentelemetry/sdk-metrics
    • resources → import from @opentelemetry/resources
  • feat(sdk-logs): mark @opentelemetry/sdk-logs as stable #7143 @​trentm

... (truncated)

Commits
  • 12a5817 chore: prepare next release (#7213)
  • 2a97587 docs: 3.x migration doc edits (#7216)
  • ebefa76 chore(deps): update dependency eslint to v10.13.0 (#7129)
  • 83b6922 chore(deps): update dependency superagent to v10.4.1 (#7184)
  • 68e9e6e fix(otlp-exporter-base): pick fetch mode from the document origin, not locati...
  • 7d2455e build: lint for unused dependencies with knip (#7200)
  • 5e65e0e fix(core): no longer drop an attribute value that is an object that has `un...
  • 2fbb404 chore(deps): dedupe nx to 23.3.0 (#7205)
  • c971f52 docs(changelog): trim unreleased entries (#7203)
  • 2516215 feat(instrumentation)!: make InstrumentationBase#_enabled protected on both p...
  • Additional commits viewable in compare view

Updates @opentelemetry/otlp-transformer from 0.222.0 to 0.300.0

Release notes

Sourced from @​opentelemetry/otlp-transformer's releases.

experimental/v0.300.0

0.300.0

Summary

  • The minimum supported Node.js has been raised to >=22.15.0. This means that support for Node.js 18 and 20 has been dropped.
  • The public interface has changed
  • Only stable versions 3.0.0 are compatible with this release

💥 Breaking Changes

  • chore(shim-opencensus)!: remove the @opentelemetry/shim-opencensus package
  • feat(instrumentation-http)!: remove deprecated serverName field from HttpInstrumentationConfig #7081
    • The serverName option had no effect; stable HTTP semantic conventions do not include http.server_name. Remove it from any setConfig() or constructor call.
  • feat(sdk-node)!: remove deprecated NodeSDKConfiguration fields logRecordProcessor, metricReader, spanProcessor and deprecated namespace re-exports node, tracing
    • NodeSDKConfiguration.logRecordProcessor — use logRecordProcessors instead.
    • NodeSDKConfiguration.metricReader — use metricReaders instead.
    • NodeSDKConfiguration.spanProcessor — use spanProcessors instead.
    • export * as node from '@opentelemetry/sdk-node' — import directly from @opentelemetry/sdk-trace-node instead.
    • export * as tracing from '@opentelemetry/sdk-node' — import directly from @opentelemetry/sdk-trace-base instead.
  • feat(sdk-logs)!: remove deprecated SdkLogRecord type alias and LoggerProviderConfig type alias #7062
    • SdkLogRecord — use ReadWriteLogRecord instead.
    • LoggerProviderConfig — use LoggerProviderOptions instead.
  • feat!: migrate package builds from tsc to tsdown, emitting dual CJS/ESM output from a single dist/ directory and declaring an exports map on every package #6293 @​overbalance
    • Importing a package by its name is unaffected in both CommonJS and ESM, as is every subpath listed in its exports map.
    • Deep imports into the build output no longer resolve. An exports map is an allowlist that Node.js and bundlers enforce, so specifiers such as @opentelemetry/sdk-logs/build/src/... or @opentelemetry/sdk-logs/build/esm/... now fail with ERR_PACKAGE_PATH_NOT_EXPORTED. Rewriting them to the new file layout does not help — unlisted subpaths are rejected whether or not the file exists.
    • The emitted files moved out of build/src (CJS), build/esm and build/esnext (ESM) into dist/, using .cjs/.mjs extensions with matching .d.cts/.d.mts declarations.
    • <package>/package.json is no longer importable for the same reason. Read a package's version from your own dependency metadata, or use SDK_INFO from @opentelemetry/core for the SDK version.
    • The non-standard esnext entry point has been removed; tools that preferred it fall back to module (ESM) or main (CJS).
    • Packages that ship separate Node.js and browser implementations export them under explicit subpaths, for example @opentelemetry/sdk-logs/platform. If you depend on something that is only reachable through a deep import, please open an issue so it can be considered for the public API.
  • feat(sdk-node)!: remove "jaeger" propagator from @opentelemetry/sdk-node #7077
    • OTEL_PROPAGATORS=jaeger and { jaeger: null } in the configuration object are no longer recognised. Replace with "tracecontext".
    • See the 3.x migration guide for full instructions.
  • fix(opentelemetry-exporter-prometheus)!: default exporter host to localhost #6599 @​cjihrig
  • chore!: bump minimum node.js version to >=22.15.0
  • feat(api-logs)!: move the Logs API to @opentelemetry/api and remove the standalone @opentelemetry/api-logs package #4862 @​hectorhdzg
  • fix(exporter-prometheus)!: stop reading Prometheus exporter host and port environment variables in the exporter constructor #6966 @​LarryHu0217
  • chore(web-common)!: clean up and deprecate network span utils #7114
    • These utilities were long planned for removal. They were moved from the sdk-trace-web package and are currently only used by the (deprecated) instrumentation-fetch and instrumentation-xml-http-request packages.
    • Drop the skipOldSemconvContentLengthAttrs vestigial option from addSpanNetworkEvents().
  • feat(sdk-node)!: drop SDK package re-exports (api, contextBase, core, logs, metrics, resources) #7111 @​pichlermarc
    • api / contextBase → import from @opentelemetry/api
    • core → import from @opentelemetry/core
    • logs → import from @opentelemetry/sdk-logs
    • metrics → import from @opentelemetry/sdk-metrics
    • resources → import from @opentelemetry/resources
  • feat(sdk-logs): mark @opentelemetry/sdk-logs as stable #7143 @​trentm

... (truncated)

Commits
  • 12a5817 chore: prepare next release (#7213)
  • 2a97587 docs: 3.x migration doc edits (#7216)
  • ebefa76 chore(deps): update dependency eslint to v10.13.0 (#7129)
  • 83b6922 chore(deps): update dependency superagent to v10.4.1 (#7184)
  • 68e9e6e fix(otlp-exporter-base): pick fetch mode from the document origin, not locati...
  • 7d2455e build: lint for unused dependencies with knip (#7200)
  • 5e65e0e fix(core): no longer drop an attribute value that is an object that has `un...
  • 2fbb404 chore(deps): dedupe nx to 23.3.0 (#7205)
  • c971f52 docs(changelog): trim unreleased entries (#7203)
  • 2516215 feat(instrumentation)!: make InstrumentationBase#_enabled protected on both p...
  • Additional commits viewable 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 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

@dependabot
build(deps-dev): bump the npm-development group with 3 updates
479a78d 
Bumps the npm-development group with 3 updates: [@biomejs/biome](https://github.com/biomejs/biome/tree/HEAD/packages/@biomejs/biome), [@opentelemetry/exporter-metrics-otlp-grpc](https://github.com/open-telemetry/opentelemetry-js) and [@opentelemetry/otlp-transformer](https://github.com/open-telemetry/opentelemetry-js).


Updates `@biomejs/biome` from 2.5.15 to 2.6.2
- [Release notes](https://github.com/biomejs/biome/releases)
- [Changelog](https://github.com/biomejs/biome/blob/@biomejs/biome@2.6.2/packages/@biomejs/biome/CHANGELOG.md)
- [Commits](https://github.com/biomejs/biome/commits/@biomejs/biome@2.6.2/packages/@biomejs/biome)

Updates `@opentelemetry/exporter-metrics-otlp-grpc` from 0.222.0 to 0.300.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.222.0...experimental/v0.300.0)

Updates `@opentelemetry/otlp-transformer` from 0.222.0 to 0.300.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.222.0...experimental/v0.300.0)

---
updated-dependencies:
- dependency-name: "@biomejs/biome"
  dependency-version: 2.6.2
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: npm-development
- dependency-name: "@opentelemetry/exporter-metrics-otlp-grpc"
  dependency-version: 0.300.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: npm-development
- dependency-name: "@opentelemetry/otlp-transformer"
  dependency-version: 0.300.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: npm-development
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added the dependencies Pull requests that update a dependency file label Oct 30, 2026
@dependabot
dependabot Bot requested a review from Goopil as a code owner October 30, 2026 05:15
@dependabot dependabot Bot added the javascript Pull requests that update javascript code label Oct 30, 2026
@dependabot @github

dependabot Bot commented on behalf of github Nov 5, 2026

Copy link
Copy Markdown
Contributor Author

Looks like these dependencies are updatable in another way, so this is no longer needed.

@dependabot dependabot Bot closed this Nov 5, 2026
@dependabot
dependabot Bot deleted the dependabot/npm_and_yarn/npm-development-3c387fde65 branch November 5, 2026 05:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@Goopil Goopil Awaiting requested review from Goopil Goopil is a code owner

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants