Skip to content

build(deps): bump node-fetch from 2.6.1 to 2.6.7#16

Merged
Qard merged 1 commit into
mainfrom
dependabot/npm_and_yarn/node-fetch-2.6.7
Feb 1, 2022
Merged

build(deps): bump node-fetch from 2.6.1 to 2.6.7#16
Qard merged 1 commit into
mainfrom
dependabot/npm_and_yarn/node-fetch-2.6.7

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Feb 1, 2022

Copy link
Copy Markdown

Bumps node-fetch from 2.6.1 to 2.6.7.

Release notes

Sourced from node-fetch's releases.

v2.6.7

Security patch release

Recommended to upgrade, to not leak sensitive cookie and authentication header information to 3th party host while a redirect occurred

What's Changed

Full Changelog: node-fetch/node-fetch@v2.6.6...v2.6.7

v2.6.6

What's Changed

Full Changelog: node-fetch/node-fetch@v2.6.5...v2.6.6

v2.6.2

fixed main path in package.json

Commits
  • 1ef4b56 backport of #1449 (#1453)
  • 8fe5c4e 2.x: Specify encoding as an optional peer dependency in package.json (#1310)
  • f56b0c6 fix(URL): prefer built in URL version when available and fallback to whatwg (...
  • b5417ae fix: import whatwg-url in a way compatible with ESM Node (#1303)
  • 18193c5 fix v2.6.3 that did not sending query params (#1301)
  • ace7536 fix: properly encode url with unicode characters (#1291)
  • 152214c Fix(package.json): Corrected main file path in package.json (#1274)
  • See full diff in compare view
Maintainer changes

This version was pushed to npm by endless, a new releaser for node-fetch since your current version.


Dependabot compatibility score

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 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)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

@dependabot dependabot Bot added the dependencies Pull requests that update a dependency file label Feb 1, 2022
@Qard
Qard merged commit 17554fb into main Feb 1, 2022
@dependabot
dependabot Bot deleted the dependabot/npm_and_yarn/node-fetch-2.6.7 branch February 1, 2022 17:45
szegedi added a commit that referenced this pull request Jul 2, 2026
…stom-labels (#347)

Port OTEP-4947 thread-context writer from polarsignals/custom-labels

Adds a Node.js writer for the OpenTelemetry Thread Local Context Record
(OTEP-4947), ported from the in-development upstream at
polarsignals/custom-labels (#16, #17).

Native addon (bindings/otel-thread-ctx.cc/.hh): the writer, namespaced
as dd::OtelThreadCtx::Init(exports) and called from binding.cc. The
thread_local discovery symbol otel_thread_ctx_nodejs_v1 stays in
extern "C" at file scope so a reader can find it by name in the
dd_pprof.node dynsym table. Records use a flexible-array tail, are
right-sized to the encoded payload (36-byte attrs_data floor, ×2
growth on append, 612-byte cap), and realloc-on-append updates the
wrapper's record_ pointer in place so every async-context frame holding
the same reference observes the new buffer. binding.gyp adds
-mtls-dialect=gnu2 on x86_64 Linux (TLSDESC; arm64 needs no flag).
Compiles across Node 18–26 (V8 ABI guards) and MSVC.

TS layer (ts/src/otel-thread-ctx.ts), Linux-only with no-op stubs
elsewhere: a ThreadContext class constructed with (traceId, spanId,
attributes?) and re-installed per async-context fire. Instance methods
enter()/run(fn) route through the prototype so only a real
ThreadContext can enter the AsyncLocalStorage; appendAttributes(),
isTruncated(), debugBytes(). Module-level getContext(), clearContext(),
and getProcessContextAttributes(keys) — the frozen OTEP-4719 snapshot
(schema version, uint8-key→name map, V8 layout constants) a reader
needs. Surfaced on the package root as require('@datadog/pprof').
otelThreadCtx.

Tests: a mocha suite (skipped on non-Linux) covering construction,
wire encoding incl. multibyte UTF-8 truncation, the cap and
isTruncated, in-place append vs realloc, async propagation,
enter/run/clearContext lifecycle, getProcessContextAttributes shape,
and a readelf check that the TLS symbol is exported correctly. A
scripts/docker/ harness + `npm run test:docker` runs the full suite in
a Linux container from any host. Verified 158 passing.
szegedi added a commit that referenced this pull request Jul 3, 2026
…stom-labels (#347)

Port OTEP-4947 thread-context writer from polarsignals/custom-labels

Adds a Node.js writer for the OpenTelemetry Thread Local Context Record
(OTEP-4947), ported from the in-development upstream at
polarsignals/custom-labels (#16, #17).

Native addon (bindings/otel-thread-ctx.cc/.hh): the writer, namespaced
as dd::OtelThreadCtx::Init(exports) and called from binding.cc. The
thread_local discovery symbol otel_thread_ctx_nodejs_v1 stays in
extern "C" at file scope so a reader can find it by name in the
dd_pprof.node dynsym table. Records use a flexible-array tail, are
right-sized to the encoded payload (36-byte attrs_data floor, ×2
growth on append, 612-byte cap), and realloc-on-append updates the
wrapper's record_ pointer in place so every async-context frame holding
the same reference observes the new buffer. binding.gyp adds
-mtls-dialect=gnu2 on x86_64 Linux (TLSDESC; arm64 needs no flag).
Compiles across Node 18–26 (V8 ABI guards) and MSVC.

TS layer (ts/src/otel-thread-ctx.ts), Linux-only with no-op stubs
elsewhere: a ThreadContext class constructed with (traceId, spanId,
attributes?) and re-installed per async-context fire. Instance methods
enter()/run(fn) route through the prototype so only a real
ThreadContext can enter the AsyncLocalStorage; appendAttributes(),
isTruncated(), debugBytes(). Module-level getContext(), clearContext(),
and getProcessContextAttributes(keys) — the frozen OTEP-4719 snapshot
(schema version, uint8-key→name map, V8 layout constants) a reader
needs. Surfaced on the package root as require('@datadog/pprof').
otelThreadCtx.

Tests: a mocha suite (skipped on non-Linux) covering construction,
wire encoding incl. multibyte UTF-8 truncation, the cap and
isTruncated, in-place append vs realloc, async propagation,
enter/run/clearContext lifecycle, getProcessContextAttributes shape,
and a readelf check that the TLS symbol is exported correctly. A
scripts/docker/ harness + `npm run test:docker` runs the full suite in
a Linux container from any host. Verified 158 passing.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant