Skip to content

chore(deps): update actions/create-github-app-token digest to bcd2ba4#2649

Open
elastic-renovate-prod[bot] wants to merge 1 commit into
mainfrom
renovate/actions-create-github-app-token-digest
Open

chore(deps): update actions/create-github-app-token digest to bcd2ba4#2649
elastic-renovate-prod[bot] wants to merge 1 commit into
mainfrom
renovate/actions-create-github-app-token-digest

Conversation

@elastic-renovate-prod

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
actions/create-github-app-token action digest 1b10c78 -> bcd2ba4

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 May 13, 2026 02:37
@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: #2649 — chore(deps): update actions/create-github-app-token digest to bcd2ba4
Classification: Direct PR
Change type: Tooling
Scope: Minor

Summary

Automated Renovate bot PR that updates the actions/create-github-app-token GitHub Action digest pin from 1b10c78 to bcd2ba4 (v3) in the build_ecs_typescript.yml CI workflow. This is a routine, non-breaking CI dependency bump with no impact on ECS schemas, generated artifacts, or documentation.

Files changed

  • Schemas: none
  • Generated: none
  • Tooling/scripts/tests: none
  • Docs (hand-authored): none
  • CI / GitHub: .github/workflows/build_ecs_typescript.yml (1 line changed — action digest pin update)
  • RFCs: none

Routing decision

Direct PR is appropriate. This change falls squarely under classification-rules §2 ("CI / automation — .github/workflows/ (non-breaking)"). Only a single CI workflow file is modified, and the change is limited to updating a pinned action digest hash. No schema files, generated artifacts, tooling scripts, or documentation are affected. No RFC triggers from §1 are present, and no ambiguous conditions from §3 apply.

Risk notes

  • Breaking / deprecation: No. The action remains pinned to v3; only the commit digest changes. This is a standard security/maintenance practice for GitHub Actions.
  • 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 template; ECS PR template sections are not applicable for automated dependency updates. The description adequately explains the change (package, type, update, change hash).
  • CHANGELOG.next.md — Not required. No schemas/ or scripts/ files were changed; CI-only PRs are exempt from changelog requirements.
  • make + committed generated outputs — Not applicable. No schema changes were made.
  • OTel otel: on new/changed semconv-related fields — N/A. No field changes.
  • Tests / make check — Not applicable for a CI workflow digest pin change. Standard CI will validate the workflow syntax.
  • CLA (contributor) — N/A. Author is elastic-renovate-prod bot (Elastic-owned automation).

Recommended next actions

  1. Maintainer: Verify the new digest bcd2ba4 corresponds to a legitimate release of actions/create-github-app-token v3 (standard due diligence for pinned action updates).
  2. Maintainer: Merge when CI passes. No further contributor action needed.

Posted by PR Triage workflow

@github-actions

Copy link
Copy Markdown
Contributor

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 github-actions Bot added the stale Stale issues and pull requests label Jun 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

stale Stale issues and pull requests

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants