Skip to content

chore(renovate): delay third-party actions, split release-workflow pins - #1133

Merged
hivecommons-hive[bot] merged 1 commit into
mainfrom
chore/renovate-release-pins
Nov 10, 2026
Merged

hivecommons-hive[bot] merged 1 commit into
mainfrom
chore/renovate-release-pins

Conversation

@Danathar

Copy link
Copy Markdown
Contributor

Summary: three Renovate changes so that more dependency updates in testsuite merge without a person, safely:

  1. Third-party GitHub Actions automerge only once a release is 3 days old (the same decision as finpilot#645).
  2. Action bumps to the three release workflows get their own PR, so the hive's pin-only exception can apply to them.
  3. The VM jobs stay on Ubuntu 24.04.

It also corrects a misleading description that caused the hive's reviewer to hand a routine bump to a person.

Why

  • Release-workflow pins always waited for a person. The hive merges a pure pin bump to e2e.yml, build-runner.yml or build-kde-runner.yml without a person, but only when every file in the PR is one of those three (hive src/pkg/intent/pin_only.go: "a mixed PR must not acquire a pin-only exception"). Renovate groups all projectbluefin/actions bumps into one PR that also touches other workflows and the composite action (for example chore(deps): update projectbluefin/actions digest to 4199208 #1127), so the exception could never apply here.
  • Third-party actions land the moment they're released. A 3-day minimumReleaseAge gives a compromised release time to be spotted and pulled upstream, and nobody has to review each bump. First-party projectbluefin/** actions aren't delayed.
  • Ubuntu 24.04: ci(e2e): run the VM jobs on ubuntu-24.04 #1131 pinned the VM jobs to ubuntu-24.04 because bootc's loopback install fails on 26.04. This keeps Renovate from proposing the major runner bump back to 26.04.
  • Misleading description: the first rule said "digest, patch, minor require human review under the supply-chain gate", but the inherited org rules automerge them. The hive's reviewer cited that line when it parked chore(deps): update registry.fedoraproject.org/fedora-minimal:latest docker digest to 4aaf5db #1120 for a person, which wasn't needed.

After merge

On its next run, Renovate should split #1127 into a release-workflow PR (e2e.yml only) and the rest. The release-workflow PR is the first real test of pin-only in testsuite.

Checks

  • renovate.json is valid JSON and uses only options already used in the org and in finpilot's config.
  • testsuite has no Renovate config check in CI. If the config were invalid, Renovate would open a "Fix Renovate Configuration" issue rather than act on it.
  • docs/skills/ci-ops/contributing/references/reviewing-and-merging.md describes the new rules.

🤖 Generated with Claude Code

- Third-party GitHub Actions automerge only once their release is three
  days old, the same decision as finpilot#645. First-party
  projectbluefin/** actions are not delayed.
- Action bumps in the three release workflows (e2e.yml, build-runner.yml,
  build-kde-runner.yml) get their own PR. The hive's pin-only exception
  only applies when every file in a PR is a release workflow, so while
  these bumps were grouped with other workflows (#1127) they always
  waited for a person.
- Keep the VM jobs on Ubuntu 24.04: no major runner bump (#1131).
- Correct the first rule's description: it said digest, patch and minor
  updates need human review, but the inherited org rules automerge them,
  and the hive's reviewer cited that line when it parked #1120.

Assisted-by: Claude Opus 5.5 via Claude Code
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Danathar <Danathar@users.noreply.github.com>
@hivecommons-hive hivecommons-hive Bot added author/clanker A contributor's own hive authored this PR under their login dco All commits are DCO signed-off 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/095-pre-merge-soak Lane admitted; the pre-merge soak window is running before the merge is attempted and removed stage/050-review-pending Review swarm requested; awaiting a verdict for the current head labels Nov 10, 2026
@hivecommons-hive
hivecommons-hive Bot merged commit 05e6ae5 into main Nov 10, 2026
7 checks passed
@hivecommons-hive

Copy link
Copy Markdown
Contributor

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

Evidence bundle `#113320477ac` sha256:8b2de2e8bddaf2bd78440dcccd586d7ed5267a3c731bcadbc114ebe414da728f — download from the dashboard or `hivectl review evidence #1133`.

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

Labels

author/clanker A contributor's own hive authored this PR under their login dco All commits are DCO signed-off role/trusted Author is trusted for unattended merge (trusted-author role or registry/claim tier in require_tiers) stage/095-pre-merge-soak Lane admitted; the pre-merge soak window is running before the merge is attempted

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant