Repository navigation
fix(deps): bump devantler-tech/.github/.github/workflows/apply-signed-fixes.yaml from 14.0.0 to 17.0.0 - #804
Conversation
…-fixes.yaml Bumps [devantler-tech/.github/.github/workflows/apply-signed-fixes.yaml](https://github.com/devantler-tech/.github) from 14.0.0 to 17.0.0. - [Release notes](https://github.com/devantler-tech/.github/releases) - [Commits](d513d00...84f4cdd) --- updated-dependencies: - dependency-name: devantler-tech/.github/.github/workflows/apply-signed-fixes.yaml dependency-version: 17.0.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
Code coverage overviewLanguages: Go Go / code-coverage/test
Go / code-coverage/go
View coverage of the 1 most impacted file.
ℹ️ Calculations represent line coverage. Results may change as calculations are updated. Updated |
Blocker: none Cleared 2026-10-29: Both CI repairs shipped through protected PR 801 at 737bb3b, verified main CI 40869787030 and published v17.0.1. Issues 800 and 802 are closed with acceptance evidence. Refresh the bot branch, then require fresh-head CI and the full release-range assessment before merge. Previous record (historical): |
The shared CI repairs are merged and verified on main. This branch contains only the original Dependabot commit and has no authored adaptation to discard. Refresh it against the repaired base; fresh current-head CI, substantive review and the complete release-range assessment remain required before merge. @dependabot rebase |
…-github/dot-github/workflows/apply-signed-fixes.yaml-17.0.0
The bot refresh request produced no acknowledgement or branch movement. After rechecking ownership and the unchanged original bot head, I used the expected-head base update. GitHub verifies signed merge The branch now includes both verified runner-tool repairs and the merged finite lint-job headroom change. Fresh CI and a complete release-range assessment remain required; earlier red checks and prior-head reviews are not clearance. No auto-merge or review request was added by this run. |
Bumps devantler-tech/.github/.github/workflows/apply-signed-fixes.yaml from 14.0.0 to 17.0.0.
Release notes
Sourced from devantler-tech/.github/.github/workflows/apply-signed-fixes.yaml's releases.
... (truncated)
Commits
84f4cddfeat(todo)!: retire the temporary vendor exclusion switch (#799)7a209dcfix(recovery): retire the verified rollout switch (#796)d46f985feat(todos)!: exclude conventional vendor roots by default (#795)d3c754cfix(ci): isolate explicit public evidence read credentials (#798)582f136fix(actions)!: bind catalogue components to defining source (#792)8e2dfbdfix(release): publish existing tags without a creation target (#791)7b18478perf(ci): compare Go runner capacity policies (#789)ba60525fix(governance): record provider adoption decisions (#790)0b13751fix: prove release recovery writer capability through GitHub (#788)3c142abfix(deps): bump devantler-tech/.github/.github/workflows/apply-signed-fixes.y...Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)