Update dependency invoke to v3

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
invoke (changelog)	==2.2.1 → ==3.0.3

---

Release Notes

pyinvoke/invoke (invoke)

v3.0.3

Compare Source

v3.0.2

Compare Source

v3.0.1

Compare Source

v3.0.0

Compare Source

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At 12:00 AM through 04:59 AM and 10:00 PM through 11:59 PM, Monday through Friday (* 0-4,22-23 * * 1-5)
  • Only on Sunday and Saturday (* * * * 0,6)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[dd-prapprover]

PRApprover will approve and merge this PR, FAQ, #dx-source-code-management

🛠️ PRApproval Status

• ✅ PR is eligible for auto-approval by rule datadog-agent-renovate - 2026-05-15T00:04:19Z
• ⬜ CI tests passed
• ⬜ Approved
• ⬜ Merge Started
• ⬜ Merged

➡️ Current phase: CI tests failed. Please fix the failing tests to continue.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 374f31f037

ℹ️ 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]

Regenerate Bazel lockfile for updated invoke version

Bumping invoke here without updating MODULE.bazel.lock leaves Bazel’s resolved dependency graph stale (MODULE.bazel.lock in this commit still records invoke-2.2.1), which means CI will fail in the bazel:mod-deps check I inspected at .gitlab/build/bazel/lint.yml (bazel mod deps ... followed by git diff --exit-code). This change should include the lockfile refresh so the committed lock state matches invoke==3.0.3.

Useful? React with 👍 / 👎.

[dd-octo-sts]

Files inventory check summary

File checks results against ancestor 8a1f3da0:

Results for datadog-agent_7.80.0~devel.git.817.374f31f.pipeline.113306811-1_amd64.deb:

No change detected

[dd-octo-sts]

Static quality checks

✅ Please find below the results from static quality gates
Comparison made with ancestor 8a1f3da
📊 Static Quality Gates Dashboard
🔗 SQG Job

33 successful checks with minimal change (< 2 KiB)

	Quality gate	Current Size
✅	agent_deb_amd64	744.262 MiB
✅	agent_deb_amd64_fips	702.290 MiB
✅	agent_heroku_amd64	310.046 MiB
✅	agent_msi	609.557 MiB
✅	agent_rpm_amd64	744.246 MiB
✅	agent_rpm_amd64_fips	702.273 MiB
✅	agent_rpm_arm64	721.923 MiB
✅	agent_rpm_arm64_fips	683.073 MiB
✅	agent_suse_amd64	744.246 MiB
✅	agent_suse_amd64_fips	702.273 MiB
✅	agent_suse_arm64	721.923 MiB
✅	agent_suse_arm64_fips	683.073 MiB
✅	docker_agent_amd64	804.408 MiB
✅	docker_agent_arm64	806.898 MiB
✅	docker_agent_jmx_amd64	995.327 MiB
✅	docker_agent_jmx_arm64	986.597 MiB
✅	docker_cluster_agent_amd64	206.857 MiB
✅	docker_cluster_agent_arm64	220.826 MiB
✅	docker_cws_instrumentation_amd64	7.154 MiB
✅	docker_cws_instrumentation_arm64	6.689 MiB
✅	docker_dogstatsd_amd64	39.503 MiB
✅	docker_dogstatsd_arm64	37.753 MiB
✅	docker_host_profiler_amd64	302.254 MiB
✅	docker_host_profiler_arm64	313.762 MiB
✅	dogstatsd_deb_amd64	30.162 MiB
✅	dogstatsd_deb_arm64	28.284 MiB
✅	dogstatsd_rpm_amd64	30.162 MiB
✅	dogstatsd_suse_amd64	30.162 MiB
✅	iot_agent_deb_amd64	44.449 MiB
✅	iot_agent_deb_arm64	41.414 MiB
✅	iot_agent_deb_armhf	42.122 MiB
✅	iot_agent_rpm_amd64	44.449 MiB
✅	iot_agent_suse_amd64	44.449 MiB

[alopezz]

We rather this stay in sync with what dda provides: https://github.com/DataDog/datadog-agent-dev/blob/8bfd74e0652876f5976640efbccaec2b844f5b3f/pyproject.toml#L103
Therefore no update.

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 3.x releases. But if you manually upgrade to 3.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.