Skip to content

Add package bugs metadata#2348

Merged
Drarig29 merged 4 commits into
DataDog:masterfrom
pesoszpesosz:bounty/datadog-ci-bugs-metadata
Jun 12, 2026
Merged

Add package bugs metadata#2348
Drarig29 merged 4 commits into
DataDog:masterfrom
pesoszpesosz:bounty/datadog-ci-bugs-metadata

Conversation

@pesoszpesosz

Copy link
Copy Markdown
Contributor

Summary

  • add the package-level bugs.url metadata for @datadog/datadog-ci

Validation

  • node -e "const p=require('./packages/datadog-ci/package.json'); if (p.bugs?.url !== 'https://github.com/DataDog/datadog-ci/issues') { console.error(p.bugs); process.exit(1) } console.log(JSON.stringify({name:p.name, version:p.version, bugs:p.bugs, repository:p.repository}, null, 2))"
  • git diff --check
  • npm view @datadog/[email protected] name version repository homepage bugs --json confirms the published package currently has no bugs field

@pesoszpesosz
pesoszpesosz requested a review from a team as a code owner June 11, 2026 12:59

@Drarig29 Drarig29 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

This repo has multiple package.json files. Can you add this to all of them? Also, please make sure yarn syncpack format --check passes. Edit sortFirst in .syncpackrc.json if needed.

@Drarig29 Drarig29 added the chores Related to the CI or developer experience label Jun 11, 2026
@datadog-datadog-prod-us1-2

datadog-datadog-prod-us1-2 Bot commented Jun 11, 2026

Copy link
Copy Markdown

Tests

🎉 All green!

🧪 All tests passed
❄️ No new flaky tests detected

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

@pesoszpesosz

Copy link
Copy Markdown
Contributor Author

The remaining failing check looks like a transient telemetry/API timeout in \End-to-end test the package (20)\ (ETIMEDOUT against Datadog logs/spans search); the Node 22 and 24 e2e shards passed on the same commit. I tried to rerun failed jobs, but I don't have permission on the upstream repo. Could someone rerun the failed job when convenient?

@Drarig29
Drarig29 merged commit f746050 into DataDog:master Jun 12, 2026
32 checks passed
@GabrielAnca GabrielAnca mentioned this pull request Jun 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

chores Related to the CI or developer experience

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants