SRE-800: Auto-bump hashintel/.github workflow pins#80
Draft
claude[bot] wants to merge 1 commit into
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Requested via Slack thread
Closes SRE-800
Before
After a merge to
hashintel/.github, every consuming repo's "🚀 Dependency Updates" dashboard holds the reusable-workflow digest bump (branchdeps/gha/hashintel-.github-digest, dephashintel/.github) under Pending Approval until someone ticks the checkbox in each repo — as happened with #76 on 2026-07-11, when zero bump PRs appeared until the boxes were ticked manually. The globaldependencyDashboardApproval: truein this shared preset gates them, and thegithub-actionsrule's"schedule": ["before 2am on saturday"]plus the globalminimumReleaseAge: "14 days"would delay them further even once approved.After
Renovate opens the bump PRs in all consuming repos on its next 2-hourly run with no approval step, and the existing global
automerge: true(+automergeSchedule) takes them in once CI is green.How
Adds a
packageRuletorenovate-config.json— the shared preset every hashintel repo extends viagithub>hashintel/.github:renovate-config, so this applies org-wide:{ "description": "Automatically bump the org's own reusable-workflow pins without dashboard approval", "matchManagers": ["github-actions"], "matchPackageNames": ["hashintel/.github"], "matchUpdateTypes": ["digest"], "dependencyDashboardApproval": false, "minimumReleaseAge": "0 days", "schedule": ["at any time"] }github-actionsrule — Renovate mergespackageRulesin order, so the later rule overrides that rule's Saturday-onlyschedulefor these pins while inheriting itscommitMessageTopic, branch prefix, and assignees.matchUpdateTypes: ["digest"]limits the override to the SHA-pin bumps of our own reusable workflows; ordinary third-party action updates keep the existing approval + Saturday schedule."at any time"so bumps go out on the next Renovate run after a merge here rather than waiting for Saturday;minimumReleaseAge: "0 days"explicitly defeats the global 14-day cooldown.npx renovate-config-validator(renovate 43.243.2, the version pinned in this repo): "Config validated successfully against 1 file(s)".