Repository navigation
Register official Datadog v2 freshness audit - #116
Merged
Merged
Conversation
This was referenced Oct 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Register Datadog v2's official SDK-generation artifact for weekly freshness checks and validated imports, continuing the exact source already cited in the stored API's x-origin. The vendor README identifies public OpenAPI generation and opt-in unstable endpoints; preserve those annotations and expose this scope limitation. v1 and other Datadog products need separate audits.
Validation: 69 updater tests pass locally. Official revision
2240a46b47e2d135962176dfc9dc665f506628af, entry SHA-2562b3da388fca085e5c9dfef7fdf4617af85fc8126695e3065f7ad46badaa0118b, passes full OpenAPI 3.0 validation without bundling, conversion or patches. Stored/source fixed version1.0is unchanged, but coverage is 1008 / 1591 → 1042 / 1647 paths / operations: 35 paths and 57 operations added, one path/operation removed. That RUM removal is explicitly documented by the vendor's merged retirement PR #4077, resolving the removal review despite lingering reference documentation. API refresh follows separately. No new workflow permissions or automatic merging.