chore(deps): update actions/stale action to v10.3.0

[elastic-renovate-prod]

This PR contains the following updates:

Package	Type	Update	Change
actions/stale	action	minor	v10.2.0 -> v10.3.0

---

Release Notes

actions/stale (actions/stale)

v10.3.0

Compare Source

What's Changed

Bug Fix

• Enhancement: ignore stale labeling events by @​shamoon in https://github.com/actions/stale/pull/1311

Dependency Updates

• Upgrade dependencies (@​actions/core, @​octokit/plugin-retry, @​typescript-eslint) by @​Copilot in https://github.com/actions/stale/pull/1335

New Contributors

• @​shamoon made their first contribution in https://github.com/actions/stale/pull/1311

Full Changelog: actions/stale@v10...v10.3.0

---

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.

[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: #2661 — chore(deps): update actions/stale action to v10.3.0
Classification: Direct PR
Change type: Tooling
Scope: Minor

Summary

Automated Renovate bot PR that bumps the actions/stale GitHub Action from v10.2.0 to v10.3.0 in the stale-issue workflow. This is a single-line CI dependency pin update with no impact on ECS schemas, tooling, or documentation. Straightforward Direct PR per classification-rules §2 (CI / automation).

Files changed

• Schemas: none
• Generated: none
• Tooling/scripts/tests: none
• Docs (hand-authored): none
• CI / GitHub: .github/workflows/stale.yml (1 addition, 1 deletion — hash pin update from v10.2.0 to v10.3.0)
• RFCs: none

Routing decision

Direct PR is appropriate. The change touches only .github/workflows/stale.yml, updating a pinned GitHub Action version. Per classification-rules §2, CI/automation changes to .github/workflows/ that are non-breaking are eligible for direct merge. 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. This is a minor version bump (v10.2.0 to v10.3.0) of a GitHub Action used only for stale issue/PR management. The upstream release notes indicate a bug fix and dependency updates only.
• OTel / semconv: N/A — no schema or field changes.
• Scope / reuse: N/A — no fieldset, reuse, or categorization changes.

Completeness checklist

• PR description (all sections) — Bot-generated Renovate description is complete for this type of change. The standard ECS PR template sections do not meaningfully apply to automated dependency bumps, and all relevant information (package, update type, version change, release notes) is provided.
• CHANGELOG.next.md — Not required. No schemas/ or scripts/ files changed; CI-only PRs are exempt from changelog entries.
• make + committed generated outputs — N/A. No schema change; no regeneration needed.
• OTel otel: on new/changed semconv-related fields — N/A. No field changes.
• Tests / make check — N/A. No schema or tooling changes; CI workflow syntax is validated by GitHub Actions itself.
• CLA (contributor) — N/A. Author is elastic-renovate-prod, an Elastic-owned bot; CLA is not applicable.

Recommended next actions

1. Review the upstream release notes for actions/stale v10.3.0 to confirm no unexpected behavioral changes to stale PR/issue management.
2. Verify CI passes (the workflow file syntax is valid) and merge at convenience.

---

Posted by PR Triage workflow