Use reviewed workflow channel for documentation image builds #58

Merged
gitchegumi merged 1 commit from kiyi/documentation-image-channel into main 2026-10-17 12:44:33 -05:00
Member

Documentation image run 337 attempt 1 failed before building or publishing an image: the v1.24.0 source scan rejected changed upstream Semgrep rules. Switch only the image caller to the reviewed Homelab/workflows@stable-v1 adapter and omit optional library_ref. On 2026-10-17 this channel selected v1.44.2 (snapshot c010d2e350531b949146412e977415542482c8e6).

All existing workflow/job names, manual dispatch inputs, runner labels, worker-pod networking, registry/signing settings and actor gates are preserved. Record the failure and actual caller state in the documentation. The older bundle/deploy callers still need review before the next bundle release.

Validation: npm run check passed; caller YAML comparison confirmed only uses/library_ref changed; git diff --check passed; Gitleaks 8.30.1 scanned staged changes using default rules with full redaction and found no leaks. Published blobs match local validated files; author and committer are kiyi kiyi@gitchegumi.com. npm run build remains blocked locally by the existing Turbopack CSS subprocess failure; hosted site checks are required before merge.

After merge and passing checks, a fresh separately approved Build scanned documentation image dispatch on main is required. No build, publication or deployment was dispatched as part of this PR.

Tracks #56. Failed run: https://git.gitchegumi.com/Homelab/Documentation/actions/runs/337/jobs/1/attempt/1

Documentation image run 337 attempt 1 failed before building or publishing an image: the v1.24.0 source scan rejected changed upstream Semgrep rules. Switch only the image caller to the reviewed Homelab/workflows@stable-v1 adapter and omit optional library_ref. On 2026-10-17 this channel selected v1.44.2 (snapshot c010d2e350531b949146412e977415542482c8e6). All existing workflow/job names, manual dispatch inputs, runner labels, worker-pod networking, registry/signing settings and actor gates are preserved. Record the failure and actual caller state in the documentation. The older bundle/deploy callers still need review before the next bundle release. Validation: npm run check passed; caller YAML comparison confirmed only uses/library_ref changed; git diff --check passed; Gitleaks 8.30.1 scanned staged changes using default rules with full redaction and found no leaks. Published blobs match local validated files; author and committer are kiyi <kiyi@gitchegumi.com>. npm run build remains blocked locally by the existing Turbopack CSS subprocess failure; hosted site checks are required before merge. After merge and passing checks, a fresh separately approved Build scanned documentation image dispatch on main is required. No build, publication or deployment was dispatched as part of this PR. Tracks #56. Failed run: https://git.gitchegumi.com/Homelab/Documentation/actions/runs/337/jobs/1/attempt/1
Use reviewed workflow channel for documentation image builds
All checks were successful
Documentation site checks / validate (pull_request) Successful in 1m37s
Source security / security (pull_request) Successful in 2m23s
Source security / pipeline (pull_request) Successful in 0s
bfb42ea21a
portegumi left a comment

Reviewed the authenticated head bfb42ea21a. The image caller now selects Homelab/workflows/build-container.yml@stable-v1, omits library_ref, and retains the manual dispatch, actor gate, runner labels, worker-pod network, registry and signing inputs in its current source. The README and delivery note separate this caller change from a new scanned image, signed bundle, and deployment; this PR does not itself change UDS routing, policy or deployment resources.

I cannot yet issue a source approval: Forgejo's changed-files response returned no patches for any of the three files, so the base-to-head change could not be independently compared; the authenticated PR tools also do not expose the selected upstream adapter's source/input contract. Public-page retrieval of the base and adapter failed, so the claimed preservation of the prior caller contract and stable-v1 compatibility remains unverified. This is an evidence-delivery gap, not a demonstrated source defect or a request to bypass scans. Please make the exact base-to-head diff and immutable selected adapter contract available for follow-up review. Source security and documentation site checks on this head are pending and remain separate merge gates. No build, release or merge is authorized by this review.

Reviewed the authenticated head bfb42ea21ae20d7e00b741a08505ba0166a2319a. The image caller now selects Homelab/workflows/build-container.yml@stable-v1, omits library_ref, and retains the manual dispatch, actor gate, runner labels, worker-pod network, registry and signing inputs in its current source. The README and delivery note separate this caller change from a new scanned image, signed bundle, and deployment; this PR does not itself change UDS routing, policy or deployment resources. I cannot yet issue a source approval: Forgejo's changed-files response returned no patches for any of the three files, so the base-to-head change could not be independently compared; the authenticated PR tools also do not expose the selected upstream adapter's source/input contract. Public-page retrieval of the base and adapter failed, so the claimed preservation of the prior caller contract and stable-v1 compatibility remains unverified. This is an evidence-delivery gap, not a demonstrated source defect or a request to bypass scans. Please make the exact base-to-head diff and immutable selected adapter contract available for follow-up review. Source security and documentation site checks on this head are pending and remain separate merge gates. No build, release or merge is authorized by this review.
gitchegumi approved these changes 2026-10-17 12:38:20 -05:00
gitchegumi deleted branch kiyi/documentation-image-channel 2026-10-17 12:44:33 -05:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
Homelab/Documentation!58
No description provided.