Repository navigation
chore(deps): bump debian from 62bd423 to f6b08b0 in /controller - #161
Merged
Merged
Conversation
Bumps debian from `62bd423` to `f6b08b0`. --- updated-dependencies: - dependency-name: debian dependency-version: 13.7-slim dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
There was a problem hiding this comment.
Approved. Cursor Bugbot was not present after the first check poll, so that signal was skipped; remaining evidence is a digest-pinned controller Debian 13.7-slim bump with a matching managed-image record and no findings that need human review.
Sent by Cursor Approval Agent: Pull Request Router and Approver
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.


Bumps debian from
62bd423tof6b08b0.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)Verified the new Debian index digest against Docker Hub, including the Linux amd64 and arm64 manifest and config hashes.
Documentation impact is limited to adding the reviewed controller digest and base-config creation date to
docs/MANAGED-IMAGES.md. Previous review records are retained.No standalone configuration-template change is needed because this controller base-image refresh changes no configuration contract or adoption steps.
Current source is
163595373288c8500a739439462d0a9b3fb5def1, reconciled once with actual merged main8fcefb898a9cc386376a8cd38b36f81659fb1f8e. Its tree is0c75073efd82007d8f48506f2777aa08e6618e6c; ordered merge parents are the published PR161 source065c2cb6fe5145756ca767b6c8da9010c3a90e2dand actual main. Published history is preserved.Against that base, only
controller/Dockerfileanddocs/MANAGED-IMAGES.mddiffer, with two additions and one deletion. The Dockerfile bytes are identical to the approved controller Dockerfile. The only merge conflict was the managed-image table; resolution retains all merged runner records and historical rows, plus the unchanged approved controller row. Every other file and mode matches the actual base.Focused documentation-link, whitespace, commit-convention, PR-title and committed-secret checks passed for the new source. The existing independent review approved
065c2cbagainst4c30089; its unchanged digest, documentation and registry evidence is retained. The existing direct independent exact-source/base binding approved this reconciled source, base and tree with no findings on 2026-11-07. Its durable technical review receipt has SHA2565fac3b93c82b74da8ab9bec7c837d922ce9088a5c7329312ba664aa4f32d1b49. This is source approval only, not a submitted human GitHub approval or required validation pass; no additional panel or registry review was needed.The controller image build, module verification and Go tests passed earlier at
71f2d8d23e76417cf0d5c8d220bd538230bcf6e3. That historical log is retained and does not establish validation of the final candidate or inherited main changes. The earlier owner-reported runtime smoke has no separate retained raw log.PR161's own normal required native run 42354925731, attempt 1 passed all eight stages for this exact source/base/tree and admitted policy merge
9a2845d1a6f5ed453d401bb88a2ae9bcb9854c74. Expected skips are empty. Original test inventories and all 22 plain-OK Python summaries were verified, including 22 executor controls.The official nine-file ZIP matches GitHub's published SHA256
38cfcd9dff5945ea810b13f78f86067163c974eaa8971f92ab23711811fbb803. All stage-report/log bindings and 12 worker export files were verified. The complete cache, uncached/cached managed-image identity and outage paths passed. Official-to-worker result byte equality was unavailable after Actions removed its temporary copy and is not claimed.Fleet closed the native transaction with verified exports, scoped credential/grant cleanup, restored baseline executor
689c7c0and passed final role/idle/protected-state admission. The closed receipt has SHA256d93e82ba6a790da6aeeb28255e2a95a5e5a1bf0ec3f895eb23f1b5b5653a7a80. The source owner independently verified all 85 terminal payload sizes/hashes and raw archive/log bindings before normal merge gates.Both required build and convention jobs passed on their actual assigned runners. No prior PR check, historical build, skipped optional check or unavailable bot supplied acceptance. Worker reservation, private image promotion, live-worker recovery and app-route release remain separate.