Skip to content

chore(deps): update projectbluefin/actions digest to 3ab4328 - #1349

Open
mergeraptor[bot] wants to merge 1 commit into
mainfrom
renovate/projectbluefinactions
Open

mergeraptor[bot] wants to merge 1 commit into
mainfrom
renovate/projectbluefinactions

Conversation

@mergeraptor

@mergeraptor mergeraptor Bot commented Nov 19, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
projectbluefin/actions (changelog) workflow digest 75348af → 3ab4328

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.

@mergeraptor
mergeraptor Bot requested review from Danathar and bketelsen November 19, 2026 12:21
@mergeraptor

mergeraptor Bot commented Nov 19, 2026 •

Copy link
Copy Markdown
Contributor Author

[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

@hivecommons-hive hivecommons-hive Bot added no-dco A commit is missing Signed-off-by — run `git rebase --signoff` role/trusted Author is trusted for unattended merge (trusted-author role or registry/claim tier in require_tiers) stage/050-review-pending Review swarm requested; awaiting a verdict for the current head stage/070-fixing Hive-authored PR: CI red, changes requested or needs rebase; a hive agent is fixing it and removed stage/050-review-pending Review swarm requested; awaiting a verdict for the current head labels Nov 19, 2026
@hivecommons-hive

hivecommons-hive Bot commented Nov 19, 2026 •

Copy link
Copy Markdown
Contributor

Hive status — updated in place; edits do not notify. Full history is in the Activity Monitor.

ℹ️ Sentinel: informational, author is trusted (allow-listed bot), merge is not blocked. Head 3b9bcaccc4ba matched:

  • sensitive_path: changes 4 sensitive path(s) (.github/workflows/build.yml, .github/workflows/execute-release.yml, .github/workflows/promote-testing-to-main.yml, .github/workflows/sync-main-to-testing.yml)

No sentinel-alert label was added. The finding is recorded in the dashboard Security tab and /api/sentinel; set sentinel.trusted_authors_block: true to block trusted authors too.

@hivecommons-hive hivecommons-hive Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

This bump is one line short, and that is why contract is red.

tests/test_release_trigger.py:522-526 asserts that execute-release.yml's execute job uses the SHA stored in RETAG_NAMES_VERIFIED_AT (scripts/release-trigger.py:98). This PR moves the job to 60c9845 but leaves the constant at 75348af:

AssertionError: '60c9845049b89b668a5704ca472b165845a253d0' != '75348afb3a34c6006a3d3da51e51c9a3818b2616'

The guard is doing its job. Per the comment at release-trigger.py:95-97, someone has to re-check the job and step names before moving it. I did that check. In projectbluefin/actions .github/workflows/reusable-execute-release.yml, name: Promote release (line 185) and - name: Promote digests to target tags (line 239) are identical at 75348af and 60c9845. The only change to that file in the range is the testsuite e2e pin at line 177. So the fix is safe:

-RETAG_NAMES_VERIFIED_AT = "75348afb3a34c6006a3d3da51e51c9a3818b2616"
+RETAG_NAMES_VERIFIED_AT = "60c9845049b89b668a5704ca472b165845a253d0"

scripts/release-trigger.py is not in this diff, so I could not attach this to the line. It needs a commit on the Renovate branch or a follow-up PR. Everything else in the bump looks correct. The upstream range is 2 fast-forward commits that only bump third-party SHA pins at patch level and fix the consumer-contract checker.

Confidence: 3/5 (needs attention) — 1 medium finding; 1 perspective requested changes

-- hive: agent=reviewer-2 backend=claude model=claude-opus-5-5 effort=medium claude=2.1.327

@hivecommons-hive

hivecommons-hive Bot commented Nov 19, 2026 •

Copy link
Copy Markdown
Contributor

🐝 Possible duplicate

This PR changes exactly the same files as #1277, which was opened first:

Evidence — identical changed-file set (4 file(s)):

  • .github/workflows/build.yml
  • .github/workflows/execute-release.yml
  • .github/workflows/promote-testing-to-main.yml
  • .github/workflows/sync-main-to-testing.yml

This is a suggestion, not a verdict. Hive will not close, label, approve or merge anything here — a human decides.

It was produced by comparing changed-file sets across open PRs, which is a candidate generator: PRs that share a file are not necessarily the same work. Here the patches DIFFER, so this is the weaker tier: dependency-bump PRs that edit one shared manifest, and unrelated fixes to one busy file, both land in it. Read the diffs before acting.

@hivecommons-hive hivecommons-hive Bot added the stage/stalled In its current stage longer than expected label Nov 19, 2026
@mergeraptor mergeraptor Bot changed the title chore(deps): update projectbluefin/actions digest to 60c9845 chore(deps): update projectbluefin/actions digest to 2463703 Nov 20, 2026
@mergeraptor
mergeraptor Bot force-pushed the renovate/projectbluefinactions branch from a2d1498 to 1a7f6da Compare November 20, 2026 00:29
@hivecommons-hive hivecommons-hive Bot removed the stage/stalled In its current stage longer than expected label Nov 20, 2026

@hivecommons-hive hivecommons-hive Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Summary: This automated update moves the project's build and release pipelines to a newer version of the shared workflow library they borrow from. The new version itself looks safe: it only bumps a few helper tools. But one safety check still records the old version, so the automated tests fail and the update cannot merge as it is.

What I need from you: Bump one constant on main (diff below); the bot's next run will carry it into this PR.


Re-review of head 1a7f6da (delta since a2d1498). The delta re-points the same five uses: pins to 2463703. The testsuite pin (570922f) and the wallpapers digest come in from main, not from this PR.

correctness

Previous finding - RETAG_NAMES_VERIFIED_AT not bumped: still present.

  • scripts/release-trigger.py:98 still says 75348afb….
  • .github/workflows/execute-release.yml:127 now pins reusable-execute-release.yml@2463703f….
  • tests/test_release_trigger.py:526 compares the two values. The contract job on this head (Validate manifests step) fails with:
    AssertionError: '2463703fd33dc4f11924ea9a99d98b0cb1b88838' != '75348afb3a34c6006a3d3da51e51c9a3818b2616'

I checked the job and step names at 2463703: execute: is still name: Promote release (line 185), and the step is still Promote digests to target tags (line 239). These match RETAG_JOB/RETAG_STEP (scripts/release-trigger.py:99-100), so bumping the constant is safe. Apply this on main:

-RETAG_NAMES_VERIFIED_AT = "75348afb3a34c6006a3d3da51e51c9a3818b2616"
+RETAG_NAMES_VERIFIED_AT = "2463703fd33dc4f11924ea9a99d98b0cb1b88838"

Lasting fix: have Renovate bump this constant in the same group as the projectbluefin/actions pin, so every digest PR does not hit this test.

Upstream 75348af..2463703 changes only pinned helper actions (taiki-e/install-action v2.90.6, oras-project/setup-oras v2.0.4) and the testsuite pin inside reusable-execute-release.yml. It adds no new permissions, secrets or triggers.

No findings from: security, intent-alignment, style, docs-currency.

Confidence: 3/5 (needs attention) — 1 medium finding; 1 perspective requested changes

-- hive: agent=reviewer backend=claude model=claude-opus-5-5 effort=medium claude=2.1.327

@mergeraptor mergeraptor Bot changed the title chore(deps): update projectbluefin/actions digest to 2463703 chore(deps): update projectbluefin/actions digest to 3ab4328 Nov 20, 2026
@mergeraptor
mergeraptor Bot force-pushed the renovate/projectbluefinactions branch from 1a7f6da to 3b9bcac Compare November 20, 2026 01:58
@hivecommons-hive hivecommons-hive Bot added the stage/stalled In its current stage longer than expected label Nov 20, 2026

This branch has not been deployed

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

Labels

no-dco A commit is missing Signed-off-by — run `git rebase --signoff` role/trusted Author is trusted for unattended merge (trusted-author role or registry/claim tier in require_tiers) stage/stalled In its current stage longer than expected stage/070-fixing Hive-authored PR: CI red, changes requested or needs rebase; a hive agent is fixing it

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants