Skip to content

chore(deps): update github-actions (non-major) - #640

Merged
castrojo merged 1 commit into
mainfrom
renovate/github-actions-(non-major)
Nov 15, 2026
Merged

castrojo merged 1 commit into
mainfrom
renovate/github-actions-(non-major)

Conversation

@mergeraptor

@mergeraptor mergeraptor Bot commented Nov 8, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
docker.io/library/registry (source) service digest 3890751 → 82f6ff4
taiki-e/install-action (changelog) action digest 3a3daaf → cfdb7ed

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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate CLI.

@mergeraptor
mergeraptor Bot enabled auto-merge November 8, 2026 12:19
@jeefy
jeefy requested review from bketelsen and hanthor November 8, 2026 12:19
@jeefy

jeefy commented Nov 8, 2026

Copy link
Copy Markdown
Collaborator

[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:

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

@mergeraptor
mergeraptor Bot added this pull request to the merge queue Nov 8, 2026
@hivecommons-hive

hivecommons-hive Bot commented Nov 8, 2026 •

Copy link
Copy Markdown
Contributor
2bdab85

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

Hive flagged this PR (author @mergeraptor[bot], head 2bdab851c645) 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 4 sensitive path(s) (Touches a sensitive path (OWNERS, workflows, policies, hive config, security docs, …))
    • .github/workflows/build.yml
    • .github/workflows/reproducibility.yml
    • .github/workflows/track-junctions.yml
    • .github/workflows/unit-tests.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.

@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Nov 8, 2026
@mergeraptor
mergeraptor Bot added this pull request to the merge queue Nov 8, 2026
@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to no response for status checks Nov 9, 2026
@mergeraptor
mergeraptor Bot added this pull request to the merge queue Nov 9, 2026
@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Nov 9, 2026
@mergeraptor
mergeraptor Bot added this pull request to the merge queue Nov 9, 2026
@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Nov 9, 2026
@mergeraptor
mergeraptor Bot added this pull request to the merge queue Nov 9, 2026
@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Nov 10, 2026
@mergeraptor
mergeraptor Bot added this pull request to the merge queue Nov 10, 2026
hanthor
hanthor previously approved these changes Nov 10, 2026

@hanthor hanthor left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed diff and CI; no blocking issues found.

@jeefy jeefy added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 10, 2026
@jeefy

jeefy commented Nov 10, 2026

Copy link
Copy Markdown
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hanthor

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

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

@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Nov 10, 2026
@mergeraptor
mergeraptor Bot added this pull request to the merge queue Nov 10, 2026
@Danathar

Copy link
Copy Markdown
Contributor

/lgtm
/approve

Reviewed at 4e7a920: only moves taiki-e/install-action from 3a3daaf to cfdb7ed, which is where its v2 tag now points. This fixes the zizmor "mismatched version comment" failure that every open server PR currently hits.

@jeefy

jeefy commented Nov 10, 2026

Copy link
Copy Markdown
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: danathar, hanthor

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

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

@jeefy jeefy added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Nov 10, 2026
@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Nov 10, 2026
@hanthor
hanthor added this pull request to the merge queue Nov 10, 2026
@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Nov 10, 2026
@mergeraptor
mergeraptor Bot added this pull request to the merge queue Nov 10, 2026
@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Nov 14, 2026
@castrojo

Copy link
Copy Markdown
Contributor

/lgtm

@jeefy

jeefy commented Nov 14, 2026

Copy link
Copy Markdown
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: danathar

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

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

@jeefy jeefy added lgtm "Looks good to me", indicates that a PR is ready to be merged. and removed lgtm "Looks good to me", indicates that a PR is ready to be merged. labels Nov 14, 2026
@castrojo
castrojo added this pull request to the merge queue Nov 14, 2026
@mergeraptor

mergeraptor Bot commented Nov 14, 2026

Copy link
Copy Markdown
Contributor Author

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@castrojo

Copy link
Copy Markdown
Contributor

/hold

Holding until the BuildStream cache root-cause fix #664 lands. Do not enqueue pre-fix builds.

@jeefy jeefy added the hold Indicates that a PR should not merge because someone has issued a /hold command. label Nov 14, 2026
@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to a conflict with the base branch Nov 14, 2026
@castrojo

Copy link
Copy Markdown
Contributor

/hold

Cache repair order: #664 first; then #669 (payload-completeness correction, retargeted to main after #664 lands). Keep this PR out of the queue until both are merged, both main seed variants have actually succeeded, and the GCC payload can be pulled from the project CAS. Then resume #640 before #591, one at a time. #667 and #665 are closed as superseded; do not re-enqueue them.

@castrojo

Copy link
Copy Markdown
Contributor

Sequencing correction: #665, #667 and #669 are now closed because every correction is consolidated directly into #664 at 47ce75e, including the verified systemd clock-epoch fix. Keep this PR held until #664 passes the full queue and merges, both main seed variants succeed and a real project-CAS GCC payload pull succeeds. Then resume #640 before #591, one at a time; no separate #669 merge is required.

@castrojo

Copy link
Copy Markdown
Contributor

Keep held: final cache-repair sequence is #664, verified main seed payloads, then prepared #670 to remove advisory warming from the release critical path. #670 is draft behind #664 so the running full build is not restarted. Resume #640 before #591 only after those prerequisites are complete.

@castrojo

Copy link
Copy Markdown
Contributor

Compatibility precheck: this PR changes the taiki-e/install-action pin and the local test-registry digest, not BuildStream or the FSDK junction. After #664 and #670 land, refresh this branch against main before queueing: the two seed jobs move from build.yml to cache-warm.yml, so update their installer-action pins there rather than restoring removed jobs in build.yml. Preserve the registry digest update. Keep held until the cache-repair and actual payload checks pass; no extra full-build run requested.

@castrojo

castrojo commented Nov 14, 2026 •

Copy link
Copy Markdown
Contributor

/hold cancel

Cancelling my earlier sequencing hold: #664 is merged and its full main build, boot tests, release and real GCC cache-payload pull passed. #670 is independent and is not a prerequisite for this dependency update.

Completed the two-commit refresh onto current main as 2bdab85 instead of waiting for the external bot. The conflicts were the competing install-action version comments. Kept the cfdb7ed/v2.90.3 update and the registry 82f6ff4 digest, retained all of #664, and collapsed the now-redundant comment-fix commit. The resulting change is still four workflow files, eight replacements: no BuildStream container, FSDK junction or cache-configuration changes.

Local actionlint and docs checks passed. The pending bot retry is cleared to avoid a competing rewrite. Fresh native CI will validate the refreshed head before normal merge-queue admission; no administrative bypass.

@castrojo castrojo removed the hold Indicates that a PR should not merge because someone has issued a /hold command. label Nov 14, 2026
Signed-off-by: castrojo <castrojo@users.noreply.github.com>
Assisted-by: GPT-6.1 via GitHub Copilot
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@castrojo
castrojo force-pushed the renovate/github-actions-(non-major) branch from 664dfa5 to 2bdab85 Compare November 14, 2026 23:46
@jeefy

jeefy commented Nov 14, 2026

Copy link
Copy Markdown
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: danathar

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

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

@jeefy jeefy removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Nov 14, 2026
@castrojo

Copy link
Copy Markdown
Contributor

/lgtm
/approve

Reviewed refreshed head 2bdab85 against current main. It preserves the same two dependency values already in this PR: install-action cfdb7ed/v2.90.3 and registry digest 82f6ff4. The conflict resolution retains #664 and all existing required checks; BuildStream, FSDK, cache endpoints and permissions are unchanged. Local actionlint and docs checks passed. Native CI and the normal merge queue must pass before landing.

@castrojo
castrojo enabled auto-merge November 14, 2026 23:48
@jeefy

jeefy commented Nov 14, 2026

Copy link
Copy Markdown
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: castrojo, danathar

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

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

@jeefy jeefy added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Nov 14, 2026
@castrojo
castrojo added this pull request to the merge queue Nov 14, 2026
Merged via the queue into main with commit bcfcac4 Nov 15, 2026
39 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm "Looks good to me", indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants