-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Track new integrations released #22057
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Track new integrations released #22057
Conversation
Codecov Report❌ Patch coverage is Additional details and impacted files🚀 New features to boost your workflow:
|
There was a problem hiding this 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".
| 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]: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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 👍 / 👎.
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:

Motivation
AI-5790
Review checklist (to be filled by reviewers)
qa/skip-qalabel if the PR doesn't need to be tested during QA.backport/<branch-name>label to the PR and it will automatically open a backport PR once this one is merged