Allowlist carabiner ampel-bootstrap@v1.2.1 (fix transitive-failures canary)#1037
Merged
Merged
Conversation
…anary) The scheduled 'Check for transitive failures' workflow has been failing every run because the composite probes carabiner-dev/actions/install/download-and-verify @f882fa9e (v1.2.1), whose action.yml pulls carabiner-dev/actions@94f29392 (v1.2.1) -- a transitive dependency that was not on the allowlist. GitHub's org-wide policy then blocks the whole composite from loading: The action carabiner-dev/actions@94f29392... is not allowed in apache/infrastructure-actions The v1.2.1 bump (94f29392) had been added for ampel/verify, install/ampel and install/bnd, but this transitive ampel-bootstrap ref was missed (it is not a directly-probed step, so the update job never learned about it). Add ampel-bootstrap@94f29392 (v1.2.1) with a 12-week expiry, matching how the other manually-added transitive carabiner refs are managed. It is the same commit already trusted via three sibling subpaths, so no new trust surface. approved_patterns.yml regenerated to match (composite unchanged -- the entry carries an expiry so it is not a dependabot-update candidate). Generated-by: Claude Opus 4.8 (1M context) via Claude Code
raboof
approved these changes
Jul 14, 2026
| # completes the v1.2.1 (94f29392) approval so the transitive-failures canary resolves. | ||
| 94f29392187fe5082d1195a7d4cae3a7ddf09d9c: | ||
| tag: v1.2.1 | ||
| expires_at: 2026-10-05 |
Member
There was a problem hiding this comment.
why does this entry need an expiration?
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
2 participants
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.
Problem
The scheduled Check for transitive failures canary has been failing on every run (all day 2026-07-12). The composite probes
carabiner-dev/actions/install/download-and-verify@f882fa9e(v1.2.1), whoseaction.ymlpullscarabiner-dev/actions/install/ampel-bootstrap@94f29392(v1.2.1) -- a transitive dependency that was not on the allowlist -- so GitHub's org policy blocks the whole composite from loading:Root cause
The v1.2.1 bump (
94f29392) was allowlisted forampel/verify,install/ampelandinstall/bnd, but the transitiveinstall/ampel-bootstrap@94f29392ref was missed. It isn't a directly-probed step (it's reached viadownload-and-verify@f882fa9e), so theupdatejob never learned about it and it had to be added by hand -- like the other transitive carabiner refs inactions.yml.Traced chain confirming it's the only gap:
download-and-verify@f882fa9e(v1.2.1, probed) ->ampel-bootstrap@94f29392(v1.2.1) <- was missingampel/verify@94f29392->install/{ampel,bnd}@2a11d59a->download-and-verify@6022a065->ampel-bootstrap@...) resolves entirely through already-allowlisted SHAs.Fix
Add
ampel-bootstrap@94f29392(v1.2.1) with a 12-week expiry (the gateway's standard for transitive refs), and regenerateapproved_patterns.yml. It's the same commit already trusted via three sibling subpaths, so no new trust surface. The composite is unchanged -- the entry carries an expiry, so it's not a dependabot-update candidate.Once this syncs to the org allow list, the canary should go green on its next run.
🤖 Generated with Claude Code