Skip to content

chore(deps): update actions/setup-python digest to ece7cb0#2668

Open
elastic-renovate-prod[bot] wants to merge 1 commit into
mainfrom
renovate/actions-setup-python-digest
Open

chore(deps): update actions/setup-python digest to ece7cb0#2668
elastic-renovate-prod[bot] wants to merge 1 commit into
mainfrom
renovate/actions-setup-python-digest

Conversation

@elastic-renovate-prod

@elastic-renovate-prod elastic-renovate-prod Bot commented Jun 29, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
actions/setup-python (changelog) action digest e797f83ece7cb0

Configuration

📅 Schedule: 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 Renovate Bot.

@elastic-renovate-prod
elastic-renovate-prod Bot requested a review from a team as a code owner June 29, 2026 06:38
@github-actions

Copy link
Copy Markdown
Contributor

🤖 GitHub comments

Just comment with:

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

@github-actions

Copy link
Copy Markdown
Contributor

ECS PR Triage (automated)

PR Triage Report

PR: #2668 — chore(deps): update actions/setup-python digest to ece7cb0
Classification: Direct PR
Change type: Tooling
Scope: Minor

Summary

Automated Renovate Bot PR that updates the pinned digest of actions/setup-python from e797f83/a309ff8 to ece7cb0 in two GitHub Actions workflow files. This is a routine CI dependency maintenance change with zero impact on ECS schemas, tooling, or documentation. No routing concerns.

Files changed

  • Schemas: none
  • Generated: none
  • Tooling/scripts/tests: none
  • Docs (hand-authored): none
  • CI / GitHub: .github/workflows/ecs-release-ff.yml, .github/workflows/test.yml
  • RFCs: none

Routing decision

Direct PR is appropriate. Per classification-rules SS2, CI/automation changes to .github/workflows/ that are non-breaking are low-risk and do not require an RFC or maintainer discussion. The change is limited to updating a pinned action digest hash -- a standard dependency maintenance operation with no functional impact on ECS content or build logic.

No RFC triggers from SS1 apply (no schema files, no breaking changes, no new fields, no reuse topology changes, no novel use cases). No ambiguity signals from SS3 apply (no new fields, no categorization changes, no maturity changes).

Risk notes

  • Breaking / deprecation: No. Digest pin update for the same major version (v6) of actions/setup-python. No behavioral change expected.
  • OTel / semconv: N/A -- no schema changes.
  • Scope / reuse: N/A -- CI-only change, no field sets or reuse affected.

Completeness checklist

  • PR description (all sections) -- PR uses Renovate Bot template rather than the ECS PR template. This is acceptable for automated dependency update PRs; the Renovate template provides adequate context (package, update type, change details).
  • CHANGELOG.next.md -- Not required. No schemas/ or scripts/ files changed.
  • make + committed generated outputs -- Not required. No schema changes.
  • OTel otel: on new/changed semconv-related fields -- N/A. No schema changes.
  • Tests / make check -- N/A for CI-only digest updates. CI workflows themselves will validate the updated action works.
  • CLA (contributor) -- N/A. Author is Renovate Bot (app/elastic-renovate-prod), an automated bot operating within the repository's configured automation.

Recommended next actions

  1. Maintainer: Verify CI passes with the updated actions/setup-python digest, then merge at convenience.
  2. No further action required from the contributor (bot-generated PR).

Posted by PR Triage workflow

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants