[mergeraptor]

This PR contains the following updates:

Package	Type	Update	Change
taiki-e/install-action (changelog)	action	digest	1e29709 → 5488ac5

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ 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]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign ahmedadan after the PR has been reviewed.
You can assign the PR to them by writing /assign @ahmedadan in a comment when ready.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[hivecommons-hive]

42e9312

ℹ️ Sentinel notice — informational; author is trusted (allow-listed bot), merge is not blocked

Hive flagged this PR (author @mergeraptor[bot], head 42e93126af65) because it matches behaviors that can override security controls, escalate privileges or damage the codebase. This is a heuristic, not an accusation — a maintainer should confirm the change is intended before it merges.

• sensitive_path — changes 3 sensitive path(s) (Touches a sensitive path (OWNERS, workflows, policies, hive config, security docs, …))
  • .github/workflows/bst-cache.yml
  • .github/workflows/ci.yml
  • .github/workflows/registry-actions.yml

Hive did not add the sentinel-alert label because this author is trusted. The finding remains recorded for audit and the dashboard Security tab; set sentinel.trusted_authors_block: true to require the blocking label for trusted authors too.

[hivecommons-hive]

Hive will not merge this PR: it changes path(s) listed in auto_merge.human_merge_paths for this repo, so a person must merge it.

• .github/workflows/registry-actions.yml

Hive added the hold label. A maintainer should review and merge this PR by hand.

[hivecommons-hive]

Reviewed — no findings from correctness, security, intent-alignment, style, docs-currency.

Confidence: 5/5 (safe)

— hive: agent=reviewer backend=copilot model=claude-fable-5.1 copilot=1.0.88

[hivecommons-hive]

Needs a decision, not a merge:

• the hold label is set
• the automerge lane will not merge this unattended

Head: verdict approved @42e9312, 8/8 checks green, soak 30m0s elapsed, labels: hold.

What to do: resolve the reason for hold and have a maintainer remove that label (/hive approve does not remove it).

_{Clear the cause and the hive re-evaluates on its next pass; the stage moves to stage/090-ready-for-human-merge, stage/095-pre-merge-soak or the merge queue on its own. An approval does not bypass CI, hold labels or other merge gates.}

[hivecommons-hive]

6b9497d

ℹ️ Sentinel notice — informational; author is trusted (allow-listed bot), merge is not blocked

Hive flagged this PR (author @mergeraptor[bot], head 6b9497d0d533) because it matches behaviors that can override security controls, escalate privileges or damage the codebase. This is a heuristic, not an accusation — a maintainer should confirm the change is intended before it merges.

• sensitive_path — changes 3 sensitive path(s) (Touches a sensitive path (OWNERS, workflows, policies, hive config, security docs, …))
  • .github/workflows/bst-cache.yml
  • .github/workflows/ci.yml
  • .github/workflows/registry-actions.yml

Hive did not add the sentinel-alert label because this author is trusted. The finding remains recorded for audit and the dashboard Security tab; set sentinel.trusted_authors_block: true to require the blocking label for trusted authors too.

[hivecommons-hive]

Reviewed — no findings from correctness, security, intent-alignment, style, docs-currency.

Confidence: 5/5 (safe)

— hive: agent=reviewer backend=copilot model=claude-fable-5.1 copilot=1.0.88

[Danathar]

Reviewed and merging: a pin-only bump of taiki-e/install-action (1e29709 to 5488ac5). The new digest is exactly what upstream's v2 tag points to (release 2.87.32), a linear 17 commits ahead, with no change to the action's own code (action.yml/main.sh); only tool-version manifests, the changelog and a CI script changed. Held as a human-merge path because it touches registry-actions.yml. The other two printer apps took the same bump earlier today. CI is green.