dependabot[bot] opened a new pull request, #704:
URL: https://github.com/apache/doris-opentelemetry-demo/pull/704

   Bumps 
[@opentelemetry/sdk-node](https://github.com/open-telemetry/opentelemetry-js) 
and 
[@opentelemetry/auto-instrumentations-node](https://github.com/open-telemetry/opentelemetry-js-contrib/tree/HEAD/packages/auto-instrumentations-node).
 These dependencies needed to be updated together.
   Updates `@opentelemetry/sdk-node` from 0.57.2 to 0.223.0
   <details>
   <summary>Release notes</summary>
   <p><em>Sourced from <a 
href="https://github.com/open-telemetry/opentelemetry-js/releases";>@​opentelemetry/sdk-node's
 releases</a>.</em></p>
   <blockquote>
   <h2>experimental/v0.223.0</h2>
   <h2>0.223.0</h2>
   <h3>:boom: Breaking Changes</h3>
   <ul>
   <li>chore(web-common)!: clean up and deprecate network span utils <a 
href="https://redirect.github.com/open-telemetry/opentelemetry-js/issues/7114";>#7114</a>
   <ul>
   <li>These utilities were long planned for removal. They were moved from the 
<code>sdk-trace-web</code> package and are currently only used by the 
(deprecated) <code>instrumentation-fetch</code> and 
<code>instrumentation-xml-http-request</code> packages.</li>
   <li>Drop the <code>skipOldSemconvContentLengthAttrs</code> vestigial option 
from <code>addSpanNetworkEvents()</code>.</li>
   </ul>
   </li>
   </ul>
   <h3>:house: Internal</h3>
   <ul>
   <li>refactor(web-common, instrumentation-fetch, 
instrumentation-xml-http-request): move utils from 
<code>@opentelemetry/sdk-trace-web</code>
   into <code>@opentelemetry/web-common</code> and use them in 
<code>@opentelemetry/instrumentation-fetch</code> and 
<code>@opentelemetry/instrumentation-xml-http-request</code>.
   With this change the instrumentations do not depend on SDK packages and the 
utils are kept in a shared package so we avoid code duplication.</li>
   </ul>
   <h2>experimental/v0.222.0</h2>
   <h2>0.222.0</h2>
   <h3>:boom: Breaking Changes</h3>
   <ul>
   <li>fix(sdk-node)!: fail-fast on Propagator creation from config file <a 
href="https://redirect.github.com/open-telemetry/opentelemetry-js/pull/6930";>#6930</a>
 <a href="https://github.com/trentm";><code>@​trentm</code></a></li>
   <li>fix(sdk-node)!: fail-fast on MeterProvider creation from config file <a 
href="https://redirect.github.com/open-telemetry/opentelemetry-js/pull/6954";>#6954</a>
 <a href="https://github.com/trentm";><code>@​trentm</code></a></li>
   <li>fix(sdk-node)!: fail-fast on TracerProvider creation from config file <a 
href="https://redirect.github.com/open-telemetry/opentelemetry-js/pull/6962";>#6962</a>
 <a href="https://github.com/trentm";><code>@​trentm</code></a></li>
   <li>fix(sdk-node)!: fail-fast on Resource creation from config file <a 
href="https://redirect.github.com/open-telemetry/opentelemetry-js/pull/6989";>#6989</a>
 <a href="https://github.com/trentm";><code>@​trentm</code></a>
   <ul>
   <li>
   <p>This also breaks some usage of <code>startNodeSDK()</code> for 
<em>environment-based</em> config, i.e. when <em>not</em> using a config file. 
For example with <code>OTEL_NODE_RESOURCE_DETECTORS=all</code>, it results in 
an error message and a no-op SDK.
   (This does not impact users of <code>new NodeSDK()</code> -- the currently 
recommended mechanism to start an SDK using this package.)</p>
   <pre lang="bash"><code>Could not create OpenTelemetry SDK from 
configuration, SDK will not be setup: unknown ExperimentalResourceDetector name 
in configuration: &quot;container&quot;
   </code></pre>
   </li>
   </ul>
   </li>
   </ul>
   <h3>:rocket: Features</h3>
   <ul>
   <li>feat(sdk-logs): deprecate <code>SdkLogRecord</code> in favor of 
<code>ReadWriteLogRecord</code> <a 
href="https://redirect.github.com/open-telemetry/opentelemetry-js/pull/6939";>#6939</a>
 <a href="https://github.com/pichlermarc";><code>@​pichlermarc</code></a></li>
   </ul>
   <h3>:bug: Bug Fixes</h3>
   <ul>
   <li>fix(instrumentation-http): redact sensitive query parameters on incoming 
(server) spans; add <code>redactedQueryParamsServer</code> config option <a 
href="https://github.com/dyladan";><code>@​dyladan</code></a></li>
   <li>fix(sdk-node): support <code>headers_list</code> when creating OTLP 
exporters from declarative configuration <a 
href="https://redirect.github.com/open-telemetry/opentelemetry-js/issues/6953";>#6953</a>
 <a href="https://github.com/JacksonWeber";><code>@​JacksonWeber</code></a></li>
   </ul>
   <h3>:books: Documentation</h3>
   <ul>
   <li>docs(sdk-logs): mark logger configuration as experimental <a 
href="https://redirect.github.com/open-telemetry/opentelemetry-js/pull/6996";>#6996</a>
 <a href="https://github.com/LarryHu0217";><code>@​LarryHu0217</code></a></li>
   <li>docs(configuration): document the <code>ConfigModel</code> suffix naming 
convention for exported types <a 
href="https://redirect.github.com/open-telemetry/opentelemetry-js/issues/6612";>#6612</a>
 <a 
href="https://github.com/vedantchalke36";><code>@​vedantchalke36</code></a></li>
   </ul>
   <h3>:house: Internal</h3>
   <ul>
   <li>refactor(sampler-jaeger-remote): remove <code>axios</code> dependency 
and use <code>fetch</code> to get the sampler configuration from Jaeger API <a 
href="https://redirect.github.com/open-telemetry/opentelemetry-js/pull/6963";>#6963</a>
 <a href="https://github.com/david-luna";><code>@​david-luna</code></a></li>
   </ul>
   <!-- raw HTML omitted -->
   </blockquote>
   <p>... (truncated)</p>
   </details>
   <details>
   <summary>Commits</summary>
   <ul>
   <li><a 
href="https://github.com/open-telemetry/opentelemetry-js/commit/92b844e8aa7d9655e4b3560154e912c4c1ced64d";><code>92b844e</code></a>
 chore: prepare next v2.x release (<a 
href="https://redirect.github.com/open-telemetry/opentelemetry-js/issues/7151";>#7151</a>)</li>
   <li><a 
href="https://github.com/open-telemetry/opentelemetry-js/commit/a859aff9825ec8138cf287d08ac86401f00aad7c";><code>a859aff</code></a>
 fix(web-common): export getElementXPath utility (<a 
href="https://redirect.github.com/open-telemetry/opentelemetry-js/issues/7124";>#7124</a>)</li>
   <li><a 
href="https://github.com/open-telemetry/opentelemetry-js/commit/2bd5a73e7af7ab363f3b239f8cb1f5f56eaa3ad5";><code>2bd5a73</code></a>
 chore(web-common)!: deprecate <code>addSpanNetworkEvents()</code> et al 
instrumentation-...</li>
   <li><a 
href="https://github.com/open-telemetry/opentelemetry-js/commit/d60f05edeac6aec8e64736c10672077fd4a766b5";><code>d60f05e</code></a>
 doc(sdk-trace): add description for StackContextManager (<a 
href="https://redirect.github.com/open-telemetry/opentelemetry-js/issues/7089";>#7089</a>)</li>
   <li><a 
href="https://github.com/open-telemetry/opentelemetry-js/commit/5bd476e6f7a22e6cf2e94a645833247284aa295d";><code>5bd476e</code></a>
 chore: move context manager to sdk-trace (<a 
href="https://redirect.github.com/open-telemetry/opentelemetry-js/issues/7086";>#7086</a>)</li>
   <li><a 
href="https://github.com/open-telemetry/opentelemetry-js/commit/554c0c6467c77e9ef1f2676f2bd20b505e228417";><code>554c0c6</code></a>
 chore: move sdk-trace-web utils to web-common (<a 
href="https://redirect.github.com/open-telemetry/opentelemetry-js/issues/7058";>#7058</a>)</li>
   <li><a 
href="https://github.com/open-telemetry/opentelemetry-js/commit/788922c5780a17d5aaace76a0da458858b2ad88a";><code>788922c</code></a>
 ci: support maintenance branch releases (<a 
href="https://redirect.github.com/open-telemetry/opentelemetry-js/issues/7036";>#7036</a>)</li>
   <li><a 
href="https://github.com/open-telemetry/opentelemetry-js/commit/0b72a81636fa476e8f1f1afd2ae0c90a1362194c";><code>0b72a81</code></a>
 chore: prepare next release (<a 
href="https://redirect.github.com/open-telemetry/opentelemetry-js/issues/7044";>#7044</a>)</li>
   <li><a 
href="https://github.com/open-telemetry/opentelemetry-js/commit/a9c5338a9f485f1433df9308f24bd7397a4a0321";><code>a9c5338</code></a>
 ci: roll prerelease changelog into one final release changelog (<a 
href="https://redirect.github.com/open-telemetry/opentelemetry-js/issues/7045";>#7045</a>)</li>
   <li><a 
href="https://github.com/open-telemetry/opentelemetry-js/commit/f41805e769ba10fb6dae72a4b7a5a3dc67cca82e";><code>f41805e</code></a>
 chore: prepare next release (<a 
href="https://redirect.github.com/open-telemetry/opentelemetry-js/issues/7042";>#7042</a>)</li>
   <li>Additional commits viewable in <a 
href="https://github.com/open-telemetry/opentelemetry-js/compare/experimental/v0.57.2...experimental/v0.223.0";>compare
 view</a></li>
   </ul>
   </details>
   <details>
   <summary>Maintainer changes</summary>
   <p>This version was pushed to npm by <a 
href="https://www.npmjs.com/~GitHub%20Actions";>GitHub Actions</a>, a new 
releaser for <code>@​opentelemetry/sdk-node</code> since your current 
version.</p>
   </details>
   <br />
   
   Updates `@opentelemetry/auto-instrumentations-node` from 0.56.1 to 0.81.2
   <details>
   <summary>Release notes</summary>
   <p><em>Sourced from <a 
href="https://github.com/open-telemetry/opentelemetry-js-contrib/releases";>@​opentelemetry/auto-instrumentations-node's
 releases</a>.</em></p>
   <blockquote>
   <h2>auto-instrumentations-node: v0.81.2</h2>
   <h2><a 
href="https://github.com/open-telemetry/opentelemetry-js-contrib/compare/auto-instrumentations-node-v0.81.1...auto-instrumentations-node-v0.81.2";>0.81.2</a>
 (2026-10-16)</h2>
   <h3>Dependencies</h3>
   <ul>
   <li>The following workspace dependencies were updated
   <ul>
   <li>dependencies
   <ul>
   <li><code>@​opentelemetry/instrumentation-winston</code> bumped from ^0.68.0 
to ^0.68.1</li>
   </ul>
   </li>
   </ul>
   </li>
   </ul>
   <h2>instrumentation-winston: v0.68.0</h2>
   <h2><a 
href="https://github.com/open-telemetry/opentelemetry-js-contrib/compare/instrumentation-winston-v0.67.0...instrumentation-winston-v0.68.0";>0.68.0</a>
 (2026-10-15)</h2>
   <h3>Features</h3>
   <ul>
   <li><strong>instrumentation-winston:</strong> add 
<code>@​opentelemetry/winston-transport</code> as peer dependency (<a 
href="https://redirect.github.com/open-telemetry/opentelemetry-js-contrib/issues/3771";>#3771</a>)
 (<a 
href="https://redirect.github.com/open-telemetry/opentelemetry-js-contrib/issues/3776";>#3776</a>)
 (<a 
href="https://github.com/open-telemetry/opentelemetry-js-contrib/commit/79df7ccf47e0cecba5956cdae4191f731150745d";>79df7cc</a>)</li>
   <li><strong>winston:</strong> support native OpenTelemetry log levels and 
custom severity mapping (<a 
href="https://redirect.github.com/open-telemetry/opentelemetry-js-contrib/issues/3345";>#3345</a>)
 (<a 
href="https://redirect.github.com/open-telemetry/opentelemetry-js-contrib/issues/3740";>#3740</a>)
 (<a 
href="https://github.com/open-telemetry/opentelemetry-js-contrib/commit/60893066c1b6326bdd22384f150f7e742b839d15";>6089306</a>)</li>
   </ul>
   <h3>Dependencies</h3>
   <ul>
   <li>The following workspace dependencies were updated
   <ul>
   <li>devDependencies
   <ul>
   <li><code>@​opentelemetry/winston-transport</code> bumped from ^0.33.0 to 
^0.34.0</li>
   </ul>
   </li>
   <li>peerDependencies
   <ul>
   <li><code>@​opentelemetry/winston-transport</code> bumped from ^0.32.0 to 
^0.34.0</li>
   </ul>
   </li>
   </ul>
   </li>
   </ul>
   <h2>instrumentation-pg: v0.76.0</h2>
   <h2><a 
href="https://github.com/open-telemetry/opentelemetry-js-contrib/compare/instrumentation-pg-v0.75.0...instrumentation-pg-v0.76.0";>0.76.0</a>
 (2026-10-15)</h2>
   <h3>Features</h3>
   <ul>
   <li><strong>instrumentation-pg:</strong> add connectionHook for connect 
spans (<a 
href="https://redirect.github.com/open-telemetry/opentelemetry-js-contrib/issues/3799";>#3799</a>)
 (<a 
href="https://github.com/open-telemetry/opentelemetry-js-contrib/commit/ffbf8e5af1c0cc44a93b651f29b6a3f27534d0a6";>ffbf8e5</a>)</li>
   </ul>
   <h2>instrumentation-nestjs-core: v0.70.0</h2>
   <h2><a 
href="https://github.com/open-telemetry/opentelemetry-js-contrib/compare/instrumentation-nestjs-core-v0.69.0...instrumentation-nestjs-core-v0.70.0";>0.70.0</a>
 (2026-10-15)</h2>
   <h3>⚠ BREAKING CHANGES</h3>
   <ul>
   <li><strong>instrumentation-nestjs-core:</strong> 
&quot;feat(instrumentation-nestjs-core): add support for NestJS 12 (<a 
href="https://redirect.github.com/open-telemetry/opentelemetry-js-contrib/issues/3733";>#3733</a>)&quot;
 (<a 
href="https://github.com/open-telemetry/opentelemetry-js-contrib/tree/HEAD/packages/auto-instrumentations-node/issues/3836";>#3836</a>)</li>
   </ul>
   <h3>Reverts</h3>
   <ul>
   <li><strong>instrumentation-nestjs-core:</strong> 
&quot;feat(instrumentation-nestjs-core): add support for NestJS 12 (<a 
href="https://redirect.github.com/open-telemetry/opentelemetry-js-contrib/issues/3733";>#3733</a>)&quot;
 (<a 
href="https://redirect.github.com/open-telemetry/opentelemetry-js-contrib/issues/3836";>#3836</a>)
 (<a 
href="https://github.com/open-telemetry/opentelemetry-js-contrib/commit/086158fc91d6380aeea3f5b0f3207a685a4667d6";>086158f</a>)</li>
   </ul>
   <h2>instrumentation-mysql: v0.69.1</h2>
   <h2><a 
href="https://github.com/open-telemetry/opentelemetry-js-contrib/compare/instrumentation-mysql-v0.69.0...instrumentation-mysql-v0.69.1";>0.69.1</a>
 (2026-10-15)</h2>
   <!-- raw HTML omitted -->
   </blockquote>
   <p>... (truncated)</p>
   </details>
   <details>
   <summary>Changelog</summary>
   <p><em>Sourced from <a 
href="https://github.com/open-telemetry/opentelemetry-js-contrib/blob/main/packages/auto-instrumentations-node/CHANGELOG.md";>@​opentelemetry/auto-instrumentations-node's
 changelog</a>.</em></p>
   <blockquote>
   <h2><a 
href="https://github.com/open-telemetry/opentelemetry-js-contrib/compare/auto-instrumentations-node-v0.81.1...auto-instrumentations-node-v0.81.2";>0.81.2</a>
 (2026-10-16)</h2>
   <h3>Dependencies</h3>
   <ul>
   <li>The following workspace dependencies were updated
   <ul>
   <li>dependencies
   <ul>
   <li><code>@​opentelemetry/instrumentation-winston</code> bumped from ^0.68.0 
to ^0.68.1</li>
   </ul>
   </li>
   </ul>
   </li>
   </ul>
   <h2><a 
href="https://github.com/open-telemetry/opentelemetry-js-contrib/compare/auto-instrumentations-node-v0.81.0...auto-instrumentations-node-v0.81.1";>0.81.1</a>
 (2026-10-15)</h2>
   <h3>Dependencies</h3>
   <ul>
   <li>The following workspace dependencies were updated
   <ul>
   <li>dependencies
   <ul>
   <li><code>@​opentelemetry/instrumentation-express</code> bumped from ^0.71.0 
to ^0.71.1</li>
   <li><code>@​opentelemetry/instrumentation-mysql</code> bumped from ^0.69.0 
to ^0.69.1</li>
   <li><code>@​opentelemetry/instrumentation-nestjs-core</code> bumped from 
^0.69.0 to ^0.70.0</li>
   <li><code>@​opentelemetry/instrumentation-pg</code> bumped from ^0.75.0 to 
^0.76.0</li>
   <li><code>@​opentelemetry/instrumentation-runtime-node</code> bumped from 
^0.36.0 to ^0.36.1</li>
   <li><code>@​opentelemetry/instrumentation-winston</code> bumped from ^0.67.0 
to ^0.68.0</li>
   </ul>
   </li>
   </ul>
   </li>
   </ul>
   <h2><a 
href="https://github.com/open-telemetry/opentelemetry-js-contrib/compare/auto-instrumentations-node-v0.80.0...auto-instrumentations-node-v0.81.0";>0.81.0</a>
 (2026-10-06)</h2>
   <h3>Features</h3>
   <ul>
   <li><strong>deps:</strong> update deps matching '@opentelemetry/*' (<a 
href="https://redirect.github.com/open-telemetry/opentelemetry-js-contrib/issues/3804";>#3804</a>)
 (<a 
href="https://github.com/open-telemetry/opentelemetry-js-contrib/commit/36fcb9cd8f83e0a1c1fdc0fbff795612215b10b7";>36fcb9c</a>)</li>
   </ul>
   <h3>Dependencies</h3>
   <ul>
   <li>The following workspace dependencies were updated
   <ul>
   <li>dependencies
   <ul>
   <li><code>@​opentelemetry/instrumentation-amqplib</code> bumped from ^0.69.0 
to ^0.70.0</li>
   <li><code>@​opentelemetry/instrumentation-aws-lambda</code> bumped from 
^0.74.0 to ^0.75.0</li>
   <li><code>@​opentelemetry/instrumentation-aws-sdk</code> bumped from ^0.77.0 
to ^0.78.0</li>
   <li><code>@​opentelemetry/instrumentation-bunyan</code> bumped from ^0.67.0 
to ^0.68.0</li>
   <li><code>@​opentelemetry/instrumentation-cassandra-driver</code> bumped 
from ^0.67.0 to ^0.68.0</li>
   <li><code>@​opentelemetry/instrumentation-connect</code> bumped from ^0.65.0 
to ^0.66.0</li>
   <li><code>@​opentelemetry/instrumentation-cucumber</code> bumped from 
^0.38.0 to ^0.39.0</li>
   <li><code>@​opentelemetry/instrumentation-dataloader</code> bumped from 
^0.39.0 to ^0.40.0</li>
   <li><code>@​opentelemetry/instrumentation-dns</code> bumped from ^0.65.0 to 
^0.66.0</li>
   <li><code>@​opentelemetry/instrumentation-express</code> bumped from ^0.70.0 
to ^0.71.0</li>
   <li><code>@​opentelemetry/instrumentation-fs</code> bumped from ^0.41.0 to 
^0.42.0</li>
   <li><code>@​opentelemetry/instrumentation-generic-pool</code> bumped from 
^0.65.0 to ^0.66.0</li>
   <li><code>@​opentelemetry/instrumentation-graphql</code> bumped from ^0.70.0 
to ^0.71.0</li>
   <li><code>@​opentelemetry/instrumentation-hapi</code> bumped from ^0.68.0 to 
^0.69.0</li>
   <li><code>@​opentelemetry/instrumentation-host-metrics</code> bumped from 
^0.5.0 to ^0.6.0</li>
   </ul>
   </li>
   </ul>
   </li>
   </ul>
   <!-- raw HTML omitted -->
   </blockquote>
   <p>... (truncated)</p>
   </details>
   <details>
   <summary>Commits</summary>
   <ul>
   <li><a 
href="https://github.com/open-telemetry/opentelemetry-js-contrib/commit/862c270a3db6f46e4f9294d76bdec762a2d232be";><code>862c270</code></a>
 chore: release main (<a 
href="https://github.com/open-telemetry/opentelemetry-js-contrib/tree/HEAD/packages/auto-instrumentations-node/issues/3837";>#3837</a>)</li>
   <li><a 
href="https://github.com/open-telemetry/opentelemetry-js-contrib/commit/3c4859931ede7939362f05818aaea4c2abd60014";><code>3c48599</code></a>
 chore: release main (<a 
href="https://github.com/open-telemetry/opentelemetry-js-contrib/tree/HEAD/packages/auto-instrumentations-node/issues/3805";>#3805</a>)</li>
   <li><a 
href="https://github.com/open-telemetry/opentelemetry-js-contrib/commit/cc263ac4e94320402ac3afe50d50eb00905e1bb8";><code>cc263ac</code></a>
 chore: release main (<a 
href="https://github.com/open-telemetry/opentelemetry-js-contrib/tree/HEAD/packages/auto-instrumentations-node/issues/3719";>#3719</a>)</li>
   <li><a 
href="https://github.com/open-telemetry/opentelemetry-js-contrib/commit/36fcb9cd8f83e0a1c1fdc0fbff795612215b10b7";><code>36fcb9c</code></a>
 feat(deps): update deps matching '@opentelemetry/*' (<a 
href="https://github.com/open-telemetry/opentelemetry-js-contrib/tree/HEAD/packages/auto-instrumentations-node/issues/3804";>#3804</a>)</li>
   <li><a 
href="https://github.com/open-telemetry/opentelemetry-js-contrib/commit/2729b781e49196b9fc8f4c66f65697a10621cc9b";><code>2729b78</code></a>
 chore: revert &quot;chore!: raise minimum supported Node.js to 22.15.0, 
dropping 1...</li>
   <li><a 
href="https://github.com/open-telemetry/opentelemetry-js-contrib/commit/36dffd26bbeb0a93f5f51aa7fec9642543227d21";><code>36dffd2</code></a>
 chore!: raise minimum supported Node.js to 22.15.0, dropping 18 and 20 
suppor...</li>
   <li><a 
href="https://github.com/open-telemetry/opentelemetry-js-contrib/commit/932fc967b142a8eb47d306fe92107b62962099f0";><code>932fc96</code></a>
 chore: release main (<a 
href="https://github.com/open-telemetry/opentelemetry-js-contrib/tree/HEAD/packages/auto-instrumentations-node/issues/3638";>#3638</a>)</li>
   <li><a 
href="https://github.com/open-telemetry/opentelemetry-js-contrib/commit/015582a5b839b942c7a6a0aa8a60d1665b16663f";><code>015582a</code></a>
 feat(deps): update deps matching '@opentelemetry/*' (<a 
href="https://github.com/open-telemetry/opentelemetry-js-contrib/tree/HEAD/packages/auto-instrumentations-node/issues/3716";>#3716</a>)</li>
   <li><a 
href="https://github.com/open-telemetry/opentelemetry-js-contrib/commit/27e172a9e0d549559056ccd58f27d13467454156";><code>27e172a</code></a>
 chore: release main (<a 
href="https://github.com/open-telemetry/opentelemetry-js-contrib/tree/HEAD/packages/auto-instrumentations-node/issues/3596";>#3596</a>)</li>
   <li><a 
href="https://github.com/open-telemetry/opentelemetry-js-contrib/commit/466d5def474cf251217881322ed4db13fad96b86";><code>466d5de</code></a>
 feat(deps): update deps matching '@opentelemetry/*' (<a 
href="https://github.com/open-telemetry/opentelemetry-js-contrib/tree/HEAD/packages/auto-instrumentations-node/issues/3629";>#3629</a>)</li>
   <li>Additional commits viewable in <a 
href="https://github.com/open-telemetry/opentelemetry-js-contrib/commits/auto-instrumentations-node-v0.81.2/packages/auto-instrumentations-node";>compare
 view</a></li>
   </ul>
   </details>
   <details>
   <summary>Maintainer changes</summary>
   <p>This version was pushed to npm by <a 
href="https://www.npmjs.com/~GitHub%20Actions";>GitHub Actions</a>, a new 
releaser for <code>@​opentelemetry/auto-instrumentations-node</code> since your 
current version.</p>
   </details>
   <br />
   
   
   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-automerge-start)
   [//]: # (dependabot-automerge-end)
   
   ---
   
   <details>
   <summary>Dependabot commands and options</summary>
   <br />
   
   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 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)
   You can disable automated security fix PRs for this repo from the [Security 
Alerts page](https://github.com/apache/doris-opentelemetry-demo/network/alerts).
   
   </details>


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to