[dependabot]

Bumps the production-dependencies group with 5 updates:

Package	From	To
@opentelemetry/api	1.9.1	1.10.0
@opentelemetry/exporter-logs-otlp-proto	0.223.0	0.300.0
@opentelemetry/exporter-metrics-otlp-proto	0.223.0	0.300.0
@opentelemetry/exporter-trace-otlp-proto	0.223.0	0.300.0
@dagrejs/dagre	3.1.2	3.1.3

Updates @opentelemetry/api from 1.9.1 to 1.10.0

Release notes

Sourced from @​opentelemetry/api's releases.

api/v1.10.0

1.10.0

🚀 Features

• feat(api): integrate the Logs API into @opentelemetry/api #4862 @​hectorhdzg
• feat(api): add imperative context.attach() for setting context across callback boundaries that with() cannot wrap. #6845 @​pichlermarc
  • attach() returns a Token whose dispose() method restores the previous context. Use token.dispose() to detach.
  • attach is an optional method on the ContextManager interface; when the active context manager does not implement it, context.attach() logs a warning and returns a no-op token.
• feat(api): add AnyValue type (of type unknown) and extend Attributes type values to use AnyValue #6780 @​trentm
  • This is part of supporting OTEP 4485.
  • This is a breaking change for SDK implementations, in that they may need to support more attribute types for any APIs that accept Attributes or AnyValue. Implementors should refer to the OTEP 4485 link above for "MUST / SHOULD" requirements for complex attributes handling. See also the attributes-handling utilities provided by @opentelemetry/core to help. For example, cleanSimpleAttributes() can be used to limit user-provided attributes to the set of value types supported in earlier @opentelemetry/api versions.
  • This change is typically not a breaking change for users of @opentelemetry/api. There is one possible breaking case: If a TypeScript user was using the Attributes type in their own code and using TypeScript Narrowing to reduce an attribute value to an expected type (example here). It is expected that this usage should be rare and, likely, limited to SDK implementations, if at all. (If this impacted your code, please let us know.)
  • Note for users of attributes: Simple attributes SHOULD be used whenever possible. Instrumentations SHOULD assume that backends do not index individual properties of complex attributes, that querying or aggregating on such properties is inefficient and complicated, and that reporting complex attributes carries higher performance overhead.

🐛 Bug Fixes

• fix(api): cap tracestate list-members and total length in the deprecated TraceState.set() so it stays in step with TraceState from @opentelemetry/core #6964 @​Zuhef
• fix: resolve the ESM build through the default export condition instead of import, so a resolver that activates neither import nor require still finds an entry point #7132 @​overbalance

📚 Documentation

• docs(api): complete @since annotations for the public API #7023 @​nabeelamjadsheikh
  • Adds the three missing exported-type annotations and the member-level annotations for methods and properties introduced after their enclosing type.
  • Corrects Attributes, AttributeValue and TracerOptions from 1.3.0 to 1.1.0; all three were already importable in 1.1.0 via wildcard re-export.

🏠 Internal

• build: migrate the package build from tsc to tsdown, emitting dual CJS/ESM output from a single dist/ directory #6293 @​overbalance
  • The public entry points are unchanged: @opentelemetry/api and @opentelemetry/api/experimental. This package already declared an exports map, so deep imports such as @opentelemetry/api/build/src/... were rejected before this change and continue to be.
  • 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. The non-standard esnext condition has been dropped in favour of the standard import/require conditions.
• perf(api): add getGlobal fast-path #6956 @​legendecas
• chore: remove the redundant module field from package.json; bundlers resolve the ESM build through the exports map #7130 @​overbalance

Changelog

Sourced from @​opentelemetry/api's changelog.

1.10.0

🚀 (Enhancement)

• feat(resource): create sync resource with some attributes that resolve asynchronously #3460 @​samimusallam
• feat: collect host id for non-cloud environments #3575 @​mwear
• feat (api-logs): separate Events API into its own package 3550 @​martinkuba
• feat(sdk-metrics): apply binary search in histogram recording #3539 @​legendecas
• perf(propagator-jaeger): improve deserializeSpanContext performance #3541 @​doochik
• feat: support TraceState in SamplingResult #3530 @​raphael-theriault-swi
• feat(sdk-trace-base): add diagnostic logging when spans are dropped #3610 @​neoeinstein
• feat: add unit to view instrument selection criteria #3647 @​jlabatut
• feat(tracing): expose dropped counts for attributes, events and links on span #3576 @​mohitk05

🐛 (Bug Fix)

• fix(core): added falsy check to make otel core work with browser where webpack config had process as false or null #3613 @​ravindra-dyte
• fix(instrumentation-http): include query params in http.target #3646 @​kobi-co

📚 (Refine Doc)

• chore: update http example #3651 @​JamieDanielson

🏠 (Internal)

• chore(exporter-jaeger): deprecate jaeger exporter #3585 @​pichlermarc
• fix(sdk-metrics): fix flaky LastValueAggregator test by using fake timer #3587 @​pichlermarc
• fix(test): fix failing tests by preventing source-map generation #3642 @​pichlermarc

Commits

• 56e6b1b chore: Release API 1.4.1, SDK 1.10.0, Experimental 0.36.0 (#3654)
• ecb5ebe fix: Minor typing issues for web sandbox (#3660)
• 48ecf22 feat(sdk-trace-base): add dropped attributes and events count on span (#3576)
• 95bf6fc fix(build): add example/http to ignore list in update-ts-configs (#3657)
• 3a2ca58 feat: add unit to view instrument selection criteria (#3647)
• ebc8575 chore(jeager-exporter): deprecate jaeger exporter (#3585)
• 2f715bd feat: allow to add attributes from grpc metadata in the patched server (#3589)
• cbbdfd3 fix(sdk-node): update instrumentations once MeterProvider is initialized (#3624)
• 4a4484a chore: update http example (#3651)
• 494efff fix(otlp-exporter-base): fix changelog for merged retry pr (#3650)
• Additional commits viewable in compare view

Updates @opentelemetry/exporter-logs-otlp-proto from 0.223.0 to 0.300.0

Release notes

Sourced from @​opentelemetry/exporter-logs-otlp-proto'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
  • for notes on migrating to 3.x / 0.300.x see the upgrade guide
• Only stable versions 3.0.0 are compatible with this release

💥 Breaking Changes

• chore(shim-opencensus)!: remove the @opentelemetry/shim-opencensus package
  • In the OpenTelemetry Specification v1.58.0 the OpenCensus compatibility requirements were deprecated. The JavaScript OpenCensus shim package will not receive any more releases after the current 0.222.0 release (source code for last release).
• 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
  • See the stable CHANGELOG for future changes to the sdk-logs package.

... (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/exporter-metrics-otlp-proto from 0.223.0 to 0.300.0

Release notes

Sourced from @​opentelemetry/exporter-metrics-otlp-proto'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
  • for notes on migrating to 3.x / 0.300.x see the upgrade guide
• Only stable versions 3.0.0 are compatible with this release

💥 Breaking Changes

• chore(shim-opencensus)!: remove the @opentelemetry/shim-opencensus package
  • In the OpenTelemetry Specification v1.58.0 the OpenCensus compatibility requirements were deprecated. The JavaScript OpenCensus shim package will not receive any more releases after the current 0.222.0 release (source code for last release).
• 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
  • See the stable CHANGELOG for future changes to the sdk-logs package.

... (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/exporter-trace-otlp-proto from 0.223.0 to 0.300.0

Release notes

Sourced from @​opentelemetry/exporter-trace-otlp-proto'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
  • for notes on migrating to 3.x / 0.300.x see the upgrade guide
• Only stable versions 3.0.0 are compatible with this release

💥 Breaking Changes

• chore(shim-opencensus)!: remove the @opentelemetry/shim-opencensus package
  • In the OpenTelemetry Specification v1.58.0 the OpenCensus compatibility requirements were deprecated. The JavaScript OpenCensus shim package will not receive any more releases after the current 0.222.0 release (source code for last release).
• 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
  • See the stable CHANGELOG for future changes to the sdk-logs package.

... (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 @dagrejs/dagre from 3.1.2 to 3.1.3

Changelog

Sourced from @​dagrejs/dagre's changelog.

v3.1.3

Fixes & Improvements

• ESM & Package Exports (PR #516): Added "type": "module" to package.json and renamed the CommonJS bundle to dist/dagre.cjs so both ESM import and CommonJS require() resolve properly. Re-exported Graph with default generic parameters for backward compatibility.
• Dynamic Layout State Isolation (PR #515): Scoped remembered dynamic layout state to the input graph rather than module-level state to prevent state leaks across layouts.
• Cluster Edge Routing (PR #523): Restored internal edge routes inside clusters with custom rankdir directions.
• Zero-Width Node Intersections (PR #524): Fixed vertical edge route intersection calculations with zero-width nodes.
• Parallel Edge Subgraph Sorting (PR #522): Fixed sortSubgraph so each parallel-edge dummy node is paired at most once when laying out three or more parallel edges.
• Flat Graph Conflict Scan Optimization (PR #520): Skipped findType2Conflicts scan when no border dummy nodes are present in flat graphs.
• Release & Tooling (PR #526, PR #527): Added a preflight release check to ensure changelog.md is updated before releasing, and added .pre-commit-config.yaml to run tests.
• Dependency Updates: Updated @dagrejs/graphlib to 4.0.6.

---

[3.1.0] - 2026

New Features

• Per-Cluster Direction Support (PR #511): Each cluster/subgraph can now specify its own rankdir, ranksep, nodesep, and align settings. The layout engine recursively applies these settings, enabling complex nested cluster hierarchies with independent flow directions. Fully backward compatible with global rankdir and legacy layouts.
• Dynamic Graph Layout Support (PR #512): Added support for dynamic graph layouts via useDynamic and corePath configuration options in LayoutConfig. Enables persistent node ordering and layout stability when modifying graph structures.

Refactoring & Fixes

• TypeScript & Type Safety Improvements: Added ClusterNodeLabel and NodeCollection types, updated NodeLabel interfaces, and eliminated any type assertions across the codebase.
• Nested Cluster Fixes: Resolved edge cases in nested cluster isolation and improved edge routing for cross-cluster edges.

---

[3.0.0] - 2026

Major Improvements: TypeScript Migration

• Full TypeScript Rewrite (PR #509): Migrated the entire core codebase from JavaScript to TypeScript for improved type safety, better IDE autocompletion, and easier maintenance.
• Native Type Definitions: Removed the need for external @types/dagre packages; high-quality types are now shipped directly with the library.
• Modern Build Pipeline: * Replaced JSHint with ESLint for stricter code quality.
  • Replaced Browserify/Karma with modern bundling and testing tools.
  • Standardized project indentation to 2 spaces (aligning .eslintrc and .editorconfig).

Refactoring & Fixes

• Dependency Cleanup: Removed deprecated dependencies including bower.json and legacy test configurations.
• Module Exports: Standardized ESM and CommonJS exports to ensure compatibility with modern bundlers like Webpack 5, Vite, and Rollup.
• Internal Logic: Refined internal graph traversal algorithms to utilize TypeScript interfaces, reducing "undefined" runtime errors.

---

[2.0.0] - Legacy Modernization

Major Changes

• Organization Transfer: Formally moved the repository to the @dagrejs GitHub organization.
• Package Renaming: Published under the @dagrejs/dagre npm scope.
• Dropped Legacy Environments: Discontinued support for extremely old Node.js versions (pre-v10) and legacy browsers that do not support ES6 features.

Fixes

... (truncated)

Commits

• a73acbf Bumping for release
• a037580 Merge pull request #527 from dagrejs/check-release-notes
• 17757d9 Adding a check on release notes to the release
• 744d6e1 Bump version and set as pre-release
• 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 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