[pull] master from DataDog:master#509
Merged
Merged
Conversation
* Use uv as hatch installer for faster test environment setup - ddev hatch plugin: set installer = 'uv' on every collected env (default, test, e2e, benchmark, latest, lint) and switch _dd-install-packages scripts to 'uv pip install'. - Bump min hatch dependency to >=1.13 (first version with the uv installer). - CI: add astral-sh/setup-uv and migrate the shared dependency cache from ~/.cache/pip to ~/.cache/uv (plus pip path for the Py2 branch). Workflows updated: cache-shared-deps, test-target, test-fips-e2e, docs, build-ddev. * Bump virtualenv min in datadog-checks-dev[cli] to unblock hatch>=1.13 Modern hatch (1.10+, where the uv installer lives) requires virtualenv>=20.26.1, but datadog_checks_dev[cli] was capping it at <20.22.0 — a constraint added in 2023 to keep Py2 testing alive. Core no longer tests Py2, and the [cli] extras already pull tools that don't support Py2 anyway, so the upper bound was dead weight. Also adds changelog entries for both packages. * Add pip to uv-managed envs and switch hatch.toml pip calls to uv uv-managed venvs don't seed pip the way virtualenv does. This breaks two classes of in-env consumers: - mypy --install-types in lint envs (auto-installs missing type stubs) - python -m pip subprocess calls in tests / hatch.toml pre/post-install commands Fixes: - Add pip to lint env deps (for mypy) and to test/e2e env deps (defensively, for any test that subprocesses pip). - Migrate the four hatch.toml files that explicitly used python -m pip (ddev, datadog_checks_dev, root docs env, kafka_consumer) to uv pip. * Use canonical hyphenated distribution name for datadog-checks-tests-helper uv builds this legacy setup.py-only package via setuptools.build_meta:__legacy__, which writes the name verbatim into METADATA. With the underscored form 'datadog_checks_tests_helper', get_datadog_wheels() in datadog_checks_base (filters by 'datadog-' prefix) didn't pick it up, breaking test_get_datadog_wheels. Distribution names should use hyphens per PEP 503/625 anyway. * Set UV_LINK_MODE=copy on Windows to allow venv cleanup uv defaults to hardlink mode on Windows. When backports.zstd._zstd.pyd (transitive of hatch>=1.13) is loaded by Python during the test run, Windows refuses to delete the venv's hardlinked copy while the cache copy is still pinned. This breaks hatch env remove invoked by ddev test --compat / --recreate. See astral-sh/uv#7918 * Scope UV_LINK_MODE=copy to Windows minimum-base-package only Regular Windows test jobs do not invoke 'hatch env remove' at the end, so they keep uv's hardlink speed-up. Only minimum-base-package jobs (which run with --compat) need the copy mode to allow venv cleanup. * Make sap_hana audit log test tolerant of venv binary name The application_name field in HANA audit logs reflects the client process name (argv[0]). uv-created venvs launch pytest as 'python3', virtualenv-created venvs launch it as 'python'. Both are valid; the integration just forwards whatever HANA reports. Use ANY instead of asserting on the runner's binary name. * Pin sap_hana audit log application_name to python3 uv-created venvs (which is what hatch>=1.13 uses with installer=uv) launch pytest as python3, so HANA records the audit-log application_name as python3 rather than python. Update the test to match the new stable layout. * Pin hatch and virtualenv in build-ddev workflow Pin to specific versions for deterministic builds and stable cache reuse. virtualenv stays on the 20.x line (latest 20.39.1) due to hatch issue #2193. * Pin virtualenv to 21.3.0 to match hatch 1.16.5 requirements hatch 1.16.5 declares virtualenv>=21 as a hard requirement (the 2026-02-25 virtualenv 21.0.0 release moved interpreter discovery to the python-discovery package, fixed in hatch by pypa/hatch#2196). The earlier 20.39.1 pin would have failed dependency resolution.
* Track pinned Python deps in workflows via Renovate Add a custom regex manager that picks up 'name==X.Y[.Z]' patterns in .github/workflows/*.yml and proposes Renovate PRs to bump them. Groups all workflow Python deps under one weekly batch with a dedicated label. PRs require human review (no auto-merge). * Cover env-var pins via Renovate annotations and add CI validator Codex review on PR #23511 noted that the regex manager only matches literal name==X.Y.Z pins, missing two of the four pinned workflow deps (pyoxidizer via the PYOXIDIZER_VERSION env var, and the ddev fallback default in release-dispatch.yml). - Annotate PYOXIDIZER_VERSION with '# renovate: datasource=pypi depName=pyoxidizer'. - Refactor release-dispatch.yml to extract the default ddev version into a DEFAULT_DDEV_VERSION env var with the same annotation. The resolved install command is functionally equivalent. - Extend renovate.json's customManager with a second matchString pattern that picks up annotated 'KEY: "X.Y[.Z]"' env values. - Add validate-renovate-config.yml so CI fails if renovate.json ever becomes invalid.
* [Release] Bumped datadog_checks_dev version to 38.0.0 * [Release] Update metadata
* [Release] Bumped cisco_aci version to 4.14.2 * fix confilcts in check-base * [Release] Bumped http_check version to 12.6.2 * [Release] Bumped ibm_was version to 5.5.1 * [Release] Bumped mac_audit_logs version to 1.4.1 * [Release] Bumped mysql version to 15.16.1 * [Release] Bumped sqlserver version to 23.0.1 * [Release] Bumped tls version to 5.6.2
* Bump datadog_checks_dev to 38.0.0 * Add changelog
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
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 : )