[elastic-renovate-prod]

This PR contains the following updates:

Package	Type	Update	Change
python	uses-with	minor	3.12 → 3.15

---

Release Notes

actions/python-versions (python)

v3.15.2: 3.15.2

Compare Source

Python 3.15.2

v3.15.1: 3.15.1

Compare Source

Python 3.15.1

v3.15.0: 3.15.0

Compare Source

Python 3.15.0

v3.14.10: 3.14.10

Compare Source

Python 3.14.10

v3.14.9: 3.14.9

Compare Source

Python 3.14.9

v3.14.8: 3.14.8

Compare Source

Python 3.14.8

v3.14.7: 3.14.7

Compare Source

Python 3.14.7

v3.14.6: 3.14.6

Compare Source

Python 3.14.6

v3.14.5: 3.14.5

Compare Source

Python 3.14.5

v3.14.4: 3.14.4

Compare Source

Python 3.14.4

v3.14.3: 3.14.3

Compare Source

Python 3.14.3

v3.14.2: 3.14.2

Compare Source

Python 3.14.2

v3.14.1: 3.14.1

Compare Source

Python 3.14.1

v3.14.0: 3.14.0

Compare Source

Python 3.14.0

v3.13.18: 3.13.18

Compare Source

Python 3.13.18

v3.13.17: 3.13.17

Compare Source

Python 3.13.17

v3.13.16: 3.13.16

Compare Source

Python 3.13.16

v3.13.15: 3.13.15

Compare Source

Python 3.13.15

v3.13.14: 3.13.14

Compare Source

Python 3.13.14

v3.13.13: 3.13.13

Compare Source

Python 3.13.13

v3.13.12: 3.13.12

Compare Source

Python 3.13.12

v3.13.11: 3.13.11

Compare Source

Python 3.13.11

v3.13.10: 3.13.10

Compare Source

Python 3.13.10

v3.13.9: 3.13.9

Compare Source

Python 3.13.9

v3.13.8: 3.13.8

Compare Source

Python 3.13.8

v3.13.7: 3.13.7

Compare Source

Python 3.13.7

v3.13.6: 3.13.6

Compare Source

Python 3.13.6

v3.13.5: 3.13.5

Compare Source

Python 3.13.5

v3.13.4: 3.13.4

Compare Source

Python 3.13.4

v3.13.3: 3.13.3

Compare Source

Python 3.13.3

v3.13.2: 3.13.2

Compare Source

Python 3.13.2

v3.13.1: 3.13.1

Compare Source

Python 3.13.1

v3.13.0: 3.13.0

Compare Source

Python 3.13.0

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• 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 has been generated by Mend Renovate CLI.

[github-actions]

🤖 GitHub comments

Just comment with:

• run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

[github-actions]

ECS PR Triage (automated)

PR Triage Report

PR: #2665 — chore(deps): update dependency python to 3.14
Classification: Direct PR
Change type: Tooling
Scope: Minor

Summary

This is an automated Renovate bot PR that bumps the Python version used in actions/setup-python from 3.12 to 3.14 across seven GitHub Actions workflow files. All changes are confined to .github/workflows/ CI configuration. No schemas, generated artifacts, tooling scripts, docs, or RFCs are affected. This is a routine, non-breaking CI dependency update that classifies as a Direct PR per classification-rules §2 ("CI / automation — .github/workflows/ (non-breaking)").

Files changed

• Schemas: none
• Generated: none
• Tooling/scripts/tests: none
• Docs (hand-authored): none
• CI / GitHub: .github/workflows/ecs-release-day.yml, .github/workflows/ecs-release-ff.yml, .github/workflows/ecs-release-post.yml, .github/workflows/ecs-release-prep.yml, .github/workflows/ecs-release-rc-tag.yml, .github/workflows/ecs-release-rc.yml, .github/workflows/port-label-cleanup.yml
• RFCs: none

Routing decision

Direct PR — all changes are limited to .github/workflows/ files, updating only the python-version parameter in actions/setup-python steps from "3.12" to "3.14". Per classification-rules §2, non-breaking CI/automation changes are eligible for direct PR. No RFC triggers from §1 apply (no schema files, no breaking changes, no new field sets, no reuse topology changes). No ambiguous signals from §3 apply either.

Risk notes

• Breaking / deprecation: No. The change is a Python runtime version bump for CI workflows only. However, a minor risk exists that Python 3.14 may introduce deprecation warnings or behavioral differences in the ECS generator scripts that run in these workflows. Maintainers should verify CI passes cleanly.
• OTel / semconv: N/A — no schema fields are involved.
• Scope / reuse: N/A — no field sets, fields, or reuse topology affected.

Completeness checklist

• PR description (all sections) — Renovate bot uses its own template format with package details, release notes, and configuration. While the standard ECS 7-section PR template is not used, this is expected and acceptable for automated bot dependency PRs on CI-only files.
• CHANGELOG.next.md — not required; no schemas/ or scripts/ files changed. CI-only PRs are exempt per completeness rules.
• make + committed generated outputs — not applicable; no schema changes.
• OTel otel: on new/changed semconv-related fields — N/A; no schema fields involved.
• Tests / make check — not directly applicable for CI workflow changes; CI should validate the workflows run correctly with Python 3.14.
• CLA (contributor) — Renovate bot is an authorized automated account; CLA not required.

Recommended next actions

1. Verify CI passes: Confirm that all GitHub Actions workflows succeed with Python 3.14, particularly the release workflows that depend on ECS Python tooling (scripts/). Python 3.14 is relatively new and may surface deprecation warnings or compatibility issues.
2. Check actions/setup-python version consistency: Note that ecs-release-ff.yml uses a pinned actions/setup-python@a309ff8b426b58ec0e2a45f0f869d46889d02405 # v6 while the other six workflows use actions/setup-python@v5. This inconsistency predates this PR but may be worth addressing separately.
3. Merge when CI is green: If all workflows pass, this is safe to merge as a routine dependency update.

---

Posted by PR Triage workflow

[github-actions]

Hi!

We just realized that we haven't looked into this PR in a while. We're
sorry!

We're labeling this PR as Stale to make it hit our filters and
make sure we get back to it as soon as possible. In the meantime, it'd
be extremely helpful if you could take a look at it as well and confirm its
relevance. A simple comment with a nice emoji will be enough :+1.

If there is no activity on this PR within the next 2 weeks, it will be
automatically closed.

Thank you for your contribution!

[github-actions]

Hi!

We just realized that we haven't looked into this PR in a while. We're
sorry!

We're labeling this PR as Stale to make it hit our filters and
make sure we get back to it as soon as possible. In the meantime, it'd
be extremely helpful if you could take a look at it as well and confirm its
relevance. A simple comment with a nice emoji will be enough :+1.

If there is no activity on this PR within the next 2 weeks, it will be
automatically closed.

Thank you for your contribution!