Skip to content

Conversation

@ddog-nasirthomas
Copy link
Contributor

What does this PR do?

Allows for all integrations to be tracked for a new release. This will be added to the agent changelog

This is an example of what the new markdown produces:
image

Motivation

AI-5790

Review checklist (to be filled by reviewers)

  • Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
  • Add the qa/skip-qa label if the PR doesn't need to be tested during QA.
  • If you need to backport this PR to another branch, you can add the backport/<branch-name> label to the PR and it will automatically open a backport PR once this one is merged

@codecov
Copy link

codecov bot commented Dec 5, 2025

Codecov Report

❌ Patch coverage is 94.44444% with 2 lines in your changes missing coverage. Please review.
✅ Project coverage is 91.18%. Comparing base (8c6c226) to head (304b7ab).
⚠️ Report is 7 commits behind head on master.

Additional details and impacted files
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@ddog-nasirthomas ddog-nasirthomas marked this pull request as ready for review December 5, 2025 14:47
@ddog-nasirthomas ddog-nasirthomas requested a review from a team as a code owner December 5, 2025 14:47
Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

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.

ℹ️ 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 on lines 78 to 82
new_integration = any(not ver[1] for ver in version_changes.values())
if new_integration:
changelog_contents.write('### New Integrations\n')
for name, ver in version_changes.items():
if not ver[1]:

Choose a reason for hiding this comment

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

P1 Badge Misclassify non‑breaking updates as “New Integrations”

The new changelog split uses ver[1] (the breaking-change flag) to decide what counts as a new integration. Any update where an existing integration bumps version without a major change sets ver[1] to False, so this loop prints it under the “New Integrations” heading instead of under “New Changes”. For example, upgrading an existing check from 1.2.0 to 1.3.0 will be reported as a brand-new integration, making the release notes inaccurate for all non-breaking updates.

Useful? React with 👍 / 👎.

@ddog-nasirthomas ddog-nasirthomas marked this pull request as draft December 5, 2025 15:00
@ddog-nasirthomas ddog-nasirthomas marked this pull request as ready for review December 5, 2025 17:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants