Skip to content

Update Dependencies - #831

Open
datadog-lambda-js-bot[bot] wants to merge 1 commit into
mainfrom
update-dependencies
Open

datadog-lambda-js-bot[bot] wants to merge 1 commit into
mainfrom
update-dependencies

Conversation

@datadog-lambda-js-bot

Copy link
Copy Markdown
Contributor

Autogenerated PR to update all deps to latest versions

@datadog-datadog-us1-prod

datadog-datadog-us1-prod Bot commented Sep 9, 2026 •

Copy link
Copy Markdown

Pipelines

✨ Unblock PR with BitsAI

❌ Errors

Your PR has failed checks. Please review the issues below and take necessary action before merging.

🚦 6 Pipeline jobs failed

local integration tests | nodejs22.x (amd64) — 🔧 Needs a code fix, caused by this PR

View more details · View in GitHub Actions

local integration tests | nodejs22.x (arm64) — 🔧 Needs a code fix, caused by this PR

View more details · View in GitHub Actions

local integration tests | nodejs24.x (amd64) — 🔧 Needs a code fix, caused by this PR

View more details · View in GitHub Actions

View all 6 failed jobs.

Useful? React with 👍 / 👎

This comment will be updated automatically if new data arrives.
🔗 Commit SHA: ae98872 | Docs | View more details | Give us feedback!

@datadog-lambda-js-bot
datadog-lambda-js-bot Bot force-pushed the update-dependencies branch 6 times, most recently from 84f253e to a721e1a Compare September 16, 2026 10:01
@datadog-lambda-js-bot
datadog-lambda-js-bot Bot force-pushed the update-dependencies branch 5 times, most recently from 39c662d to 257a16b Compare September 23, 2026 10:01
@datadog-lambda-js-bot
datadog-lambda-js-bot Bot force-pushed the update-dependencies branch 7 times, most recently from 0886d9e to 8c97a75 Compare October 1, 2026 10:01
@datadog-lambda-js-bot
datadog-lambda-js-bot Bot force-pushed the update-dependencies branch 5 times, most recently from 7b1e12f to d1e4694 Compare October 8, 2026 10:02
@datadog-lambda-js-bot
datadog-lambda-js-bot Bot force-pushed the update-dependencies branch 3 times, most recently from 55f6d2e to 9786cb9 Compare October 13, 2026 10:03
@datadog-lambda-js-bot
datadog-lambda-js-bot Bot force-pushed the update-dependencies branch 6 times, most recently from a8ba581 to be48dd7 Compare November 11, 2026 10:00

@datadog-datadog-us1-prod datadog-datadog-us1-prod Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bits Code Review: PASS

More details

The updated lockfile remains consistent with the dependency manifest and graph. Runtime compatibility remains unverified because tests were not run and CI status was inaccessible.

Was this helpful? React 👍 or 👎

Open Bits AI session

🤖 Bits Code Review · Commit be48dd7

@datadog-datadog-us1-prod datadog-datadog-us1-prod Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bits Code Review: PASS

More details

The updated dependency resolutions passed targeted TypeScript compatibility checks. Full build and runtime compatibility remain unverified.

Was this helpful? React 👍 or 👎

Open Bits AI session

🤖 Bits Code Review · Commit de518ae

@datadog-datadog-us1-prod datadog-datadog-us1-prod Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bits Code Review: PASS

More details

Consistent lockfile resolutions and passing CI builds and package tests support compatibility of the dependency updates. Integration tests and Node 26 unit tests remained pending.

Was this helpful? React 👍 or 👎

Open Bits AI session

🤖 Bits Code Review · Commit 8c340b9

@datadog-datadog-us1-prod datadog-datadog-us1-prod Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bits Code Review: PASS

More details

Completed CI checks passed for the reviewed dependency update, though some jobs remain pending. Local compatibility tests were not rerun because dependencies are not installed.

Was this helpful? React 👍 or 👎

Open Bits AI session

🤖 Bits Code Review · Commit 15df692

@datadog-datadog-us1-prod datadog-datadog-us1-prod Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bits Code Review: FAIL

The lockfile introduces Node 26 type declarations while retaining TypeScript 4.9.5, blocking clean builds with the declared toolchain.

Open Bits AI session

🤖 Bits Code Review · Commit 4f6e9f2

Comment thread yarn.lock
resolved "https://registry.npmjs.org/@types/node/-/node-20.17.0.tgz"
integrity sha512-a7zRo0f0eLo9K5X9Wp5cAqTUNGzuFLDG2R7C4HY2BhcMAsxgSPuRvAC1ZB6QkuUQXf0YZAgfOX2ZyrBa2n4nHQ==
"@types/node@*":
version "26.6.6"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Keep Node declarations compatible with TypeScript 4.9

A clean install now selects Node 26 declarations for transitive wildcard dependencies while TypeScript remains locked to 4.9.5. These declarations require newer compiler libraries, including esnext.disposable, and enter compilation through automatically included types such as @types/mock-fs despite the direct Node 20 dependency. This breaks yarn build and blocks packaging. Pin all Node declaration resolutions to a compiler-compatible release and regenerate the lockfile, or upgrade the compiler and related tooling together.

React: 👍 useful · 👎 wrong · 😕 unclear · 👀 right, but not acting on it

What each reaction means
  • 👍 Useful: correct, and you're fixing it or will.
  • 👎 Wrong: the finding is incorrect, for example the bug can't happen or the code was misread.
  • 😕 Unclear: you can't tell what it means or why it matters.
  • 👀 Right, not acting: correct, but intended, out of scope for this PR, a known risk, or too minor.

🤖 Bits Code Review · Open Bits AI session

@datadog-datadog-us1-prod datadog-datadog-us1-prod Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bits Code Review: PASS

More details

Lockfile consistency checks passed, and the static reviewer reported successful head-commit CI builds and npm package tests across supported Node versions. Some other CI checks remain pending.

Was this helpful? React 👍 or 👎

Open Bits AI session

🤖 Bits Code Review · Commit 08079d0

@datadog-datadog-us1-prod datadog-datadog-us1-prod Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bits Code Review: PASS

More details

Lockfile dependency references remain complete. The specialist reported passing completed CI builds and tests, though some checks were still pending and tests were not run locally.

Was this helpful? React 👍 or 👎

Open Bits AI session

🤖 Bits Code Review · Commit c629039

@datadog-datadog-us1-prod datadog-datadog-us1-prod Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bits Code Review: PASS

More details

The static reviewer reported successful CI builds across Node 18–26 for the updated dependency resolutions. Some tests remained pending, limiting confidence in runtime compatibility.

Was this helpful? React 👍 or 👎

Open Bits AI session

🤖 Bits Code Review · Commit 0d2d862

@datadog-datadog-us1-prod datadog-datadog-us1-prod Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bits Code Review: PASS

More details

The updated dependency resolutions remain consistent with the unchanged manifest. Integration validation remains pending, so runtime compatibility is not fully established.

Was this helpful? React 👍 or 👎

Open Bits AI session

🤖 Bits Code Review · Commit e9a864e

@datadog-datadog-us1-prod datadog-datadog-us1-prod Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bits Code Review: PASS

More details

The updated lockfile retains complete dependency references, and the specialist’s focused TypeScript compatibility checks found no new diagnostics.

Was this helpful? React 👍 or 👎

Open Bits AI session

🤖 Bits Code Review · Commit 82c3435

@datadog-datadog-us1-prod datadog-datadog-us1-prod Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bits Code Review: PASS

More details

The updated dependency graph retains complete references, and native-addon versions align with dd-trace. Runtime validation remains limited by pending CI checks and the absence of a local test run.

Was this helpful? React 👍 or 👎

Open Bits AI session

🤖 Bits Code Review · Commit c5adbb8

@datadog-datadog-us1-prod datadog-datadog-us1-prod Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bits Code Review: PASS

More details

The reviewer reported passing build and package checks, but unit and integration checks were still pending. Runtime compatibility remains only partially validated because local tests were not run.

Was this helpful? React 👍 or 👎

Open Bits AI session

🤖 Bits Code Review · Commit ae98872

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant