Skip to content

[pull] master from DataDog:master - #711

Merged
pull[bot] merged 7 commits into
ConnectionMaster:masterfrom
DataDog:master
Aug 13, 2026
Merged

[pull] master from DataDog:master#711
pull[bot] merged 7 commits into
ConnectionMaster:masterfrom
DataDog:master

Conversation

@pull

@pull pull Bot commented Aug 13, 2026

Copy link
Copy Markdown

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? 💖 Please sponsor : )

AAraKKe and others added 7 commits August 13, 2026 09:59
…pass (#24848)

ghcr.io and registry.ddbuild.io do not return release timestamps, and since Renovate
42 a missing timestamp counts as never having aged, so the 7-day
renovate/stability-days check on those images stays pending forever. Scope
minimumReleaseAgeBehaviour to timestamp-optional for that group, which keeps the
age check wherever a registry does publish timestamps.

Also enable the dependency dashboard, so updates held back by the age check are
visible instead of just absent.
* Bump pyasn1 from 0.6.3 to 0.6.4

Remediates three DoS advisories in pyasn1's BER/CER/DER decoding
(CVE-2026-59885, CVE-2026-59886, PYSEC-2026-3455), all fixed in 0.6.4.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

* Add changelog entry

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

* Update dependency resolution

* Update dependency resolution

* Remove pyasn1 from dep-update exclusion list

The upstream issue blocking updates (pyasn1/pyasn1#52) was closed in 2023, so excluding pyasn1 from automated dependency bumps is no longer needed.

* Update dependency resolution

---------

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
Co-authored-by: dd-agent-integrations-bot[bot] <dd-agent-integrations-bot[bot]@users.noreply.github.com>
The DatabaseCheck base class, DBM health reporting, schema collection, and
sql_commenter live in datadog_checks_base but are only consumed by the DBM
integrations, so route their reviews to database-monitoring-agent the way
db/utils.py, db/sql.py, and db/statement_metrics.py already are.

Co-authored-by: Cursor <cursoragent@cursor.com>
* [DBMON-6882] Make Postgres check teardown idempotent

_finalize() now runs at most once. The check is already cancelled more than once in
practice -- run_one_check() cancels and the integration_check fixture cancels again on
teardown -- so teardown re-closed connections and re-tore down the async jobs each time.

Nulling log.check also moves after the final log line. CheckLoggingAdapter.process reads
back through that attribute for checks whose check_id was never resolved, so the trailing
debug call raised AttributeError once debug logging was enabled.

Co-authored-by: Cursor <cursoragent@cursor.com>

* Add changelog

Co-authored-by: Cursor <cursoragent@cursor.com>

* Trim teardown test coverage

Drop the logging-hazard test and the rationale comment on the idempotency test.

Co-authored-by: Cursor <cursoragent@cursor.com>

* Do not log from the finalize guard

The first teardown nulls log.check, so a second call cannot log through the adapter --
which is the very hazard this change is fixing elsewhere.

Co-authored-by: Cursor <cursoragent@cursor.com>

---------

Co-authored-by: Cursor <cursoragent@cursor.com>
@pull pull Bot locked and limited conversation to collaborators Aug 13, 2026
@pull pull Bot added the ⤵️ pull label Aug 13, 2026
@pull
pull Bot merged commit 640de87 into ConnectionMaster:master Aug 13, 2026
@pull pull Bot added the ⤵️ pull label Aug 13, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants