Skip to content

Auto-activate nodejs manifest tests#7261

Open
dd-octo-sts[bot] wants to merge 1 commit into
mainfrom
auto-nodejs-manifest
Open

Auto-activate nodejs manifest tests#7261
dd-octo-sts[bot] wants to merge 1 commit into
mainfrom
auto-nodejs-manifest

Conversation

@dd-octo-sts

@dd-octo-sts dd-octo-sts Bot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

Automated activation of easy-win tests for nodejs
View nightly workflow run

  • If you approve this PR please also merge it.
  • If the tests are failing it might be due to a change made since the last nightly system-tests run. You can close the PR, an updated one will be available tomorrow.
  • If you close the PR please also delete the branch

This commit was created from the local commit with hash 9fec56018564496423c47a03f5b4ed950c843711.
@dd-octo-sts dd-octo-sts Bot requested a review from a team as a code owner July 6, 2026 07:49
@dd-octo-sts dd-octo-sts Bot enabled auto-merge (squash) July 6, 2026 07:49
@github-actions

github-actions Bot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

CODEOWNERS have been resolved as:

manifests/nodejs.yml                                                    @DataDog/dd-trace-js

@chatgpt-codex-connector chatgpt-codex-connector 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.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: f27ec03418

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread manifests/nodejs.yml
Comment on lines +165 to +169
express5: '>=6.0.0'
express4: '>=6.0.0'
express4-typescript: '>=6.0.0'
fastify: '>=6.0.0'
uds-express4: '>=6.0.0'

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Use the 6.0.0-pre threshold for Node 6 activations

When Node.js CI is running the 6.0 prerelease, these new >=6.0.0 thresholds do not match 6.0.0-pre because prereleases sort before the final 6.0.0; this same manifest defines ref_6_0_0 as >=6.0.0-pre on line 102 and uses it elsewhere. As written, the newly activated tests with >=6.0.0/v6.0.0 and the corresponding <6.0.0 skips remain xfailed on 6.0.0-pre runs and only flip after the final release, so use *ref_6_0_0/>=6.0.0-pre and matching prerelease-aware lower bounds if the intent is to activate on the current Node 6 line.

Useful? React with 👍 / 👎.

@datadog-prod-us1-6

Copy link
Copy Markdown

Pipelines  Tests

Fix all issues with BitsAI

⚠️ Warnings

🚦 22 Pipeline jobs failed

Testing the test | System Tests (nodejs, dev) / End-to-end #1 / anthropic-js@0.71.0 1   View in Datadog   GitHub Actions

Testing the test | System Tests (nodejs, dev) / End-to-end #1 / express4-typescript 1   View in Datadog   GitHub Actions

Testing the test | System Tests (nodejs, dev) / End-to-end #1 / express5 1   View in Datadog   GitHub Actions

View all 22 failed jobs.

ℹ️ Info

No other issues found (see more)

🧪 All tests passed
❄️ No new flaky tests detected

Useful? React with 👍 / 👎

This comment will be updated automatically if new data arrives.
🔗 Commit SHA: f27ec03 | Docs | Datadog PR Page | Give us feedback!

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.

0 participants