Finalize Agent release 7.83.0

[dd-octo-sts]

What does this PR do?

Finalize Agent release 7.83.0 updating the changelog files.

Motivation

Agent 7.83.0 has been released.

Additional Notes

This PR was automatically generated.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 973692e44e

ℹ️ 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".

[chatgpt-codex-connector]

Mark NGINX 10.0.0 as a breaking change

The release upgrades NGINX from 9.4.1 to 10.0.0, whose integration changelog classifies the release under Changed, but this entry omits the **BREAKING CHANGE** notice included for the other major-version upgrades. This occurs because the generator compares major-version strings, so the 9 → 10 transition is not detected; users consulting the Agent changelog are therefore not warned about this backward-incompatible update. Regenerate after comparing majors numerically or add the notice here.

AGENTS.md reference: AGENTS.md:L218-L218

Useful? React with 👍 / 👎.

[datadog-datadog-prod-us1]

The Agent changelog does not mark the NGINX update from 9.4.1 to 10.0.0 as a breaking change.

_{Open Bits AI session}

_{🤖 Datadog Autotest · Commit 973692e · What is Autotest? · @DataDog review to ask questions · Any feedback? Reach out in #autotest}

[datadog-datadog-prod-us1]

Mark the NGINX major update as breaking

Users can miss a breaking change during the Agent 7.83.0 update.

Assertion details

• Input: A user reviews the Agent 7.83.0 changes before an update from NGINX integration 9.4.1 to 10.0.0.
• Expected: The entry marks this major version update as a breaking change.
• Actual: The changelog lists NGINX 10.0.0 without the breaking-change marker.

Was this helpful? React 👍 or 👎
_{🤖 Datadog Autotest · What is Autotest? · @DataDog review to ask questions · Any feedback? Reach out in #autotest · Open Bits AI session}

[cit-pr-commenter-54b7da]

evalya-impact-summary

evalya impact analysis

Impact analysis: 0 selected, 0 skipped (of 0 test tasks)
Publish tasks:   2 (always emitted)
Diff (76 files):
  AGENT_CHANGELOG.md
  AGENT_INTEGRATIONS.md
  active_directory/CHANGELOG.md
  aerospike/CHANGELOG.md
  amazon_msk/CHANGELOG.md
  aspdotnet/CHANGELOG.md
  boundary/CHANGELOG.md
  cisco_aci/CHANGELOG.md
  clickhouse/CHANGELOG.md
  cockroachdb/CHANGELOG.md
  datadog_checks_base/CHANGELOG.md
  datadog_checks_downloader/CHANGELOG.md
  directory/CHANGELOG.md
  do_query_actions/CHANGELOG.md
  dotnetclr/CHANGELOG.md
  duckdb/CHANGELOG.md
  envoy/CHANGELOG.md
  esxi/CHANGELOG.md
  exchange_server/CHANGELOG.md
  falco/CHANGELOG.md
  ... and 56 more

Debug a specific task: evalya plan impact --path <path> --task <task>

Learn more about CI impact filtering

[dd-octo-sts]

Validation Report

All 21 validations passed.

Show details

Validation	Description	Status
agent-reqs	Verify check versions match the Agent requirements file	✅
ci	Validate CI configuration and code coverage settings	✅
codeowners	Validate every integration has a CODEOWNERS entry	✅
config	Validate default configuration files against spec.yaml	✅
dep	Verify dependency pins are consistent and Agent-compatible	✅
http	Validate integrations use the HTTP wrapper correctly	✅
imports	Validate check imports do not use deprecated modules	✅
integration-style	Validate check code style conventions	✅
jmx-metrics	Validate JMX metrics definition files and config	✅
labeler	Validate PR labeler config matches integration directories	✅
legacy-signature	Validate no integration uses the legacy Agent check signature	✅
license-headers	Validate Python files have proper license headers	✅
licenses	Validate third-party license attribution list	✅
metadata	Validate metadata.csv metric definitions	✅
models	Validate configuration data models match spec.yaml	✅
openmetrics	Validate OpenMetrics integrations disable the metric limit	✅
package	Validate Python package metadata and naming	✅
qa-label	Validate the pull request declares whether it needs QA for the next Agent release	✅
readmes	Validate README files have required sections	✅
saved-views	Validate saved view JSON file structure and fields	✅
version	Validate version consistency between package and changelog	✅

View full run