Repository navigation
fix(ci): qualify governance against the current Runner source - #130
Merged
Merged
Conversation
Review source hashes for the immutable platform Runner pin, retain the existing governance assertions, and verify non-empty folder descriptions are rejected. Run the complete native Plan/Application/governance contract in PR validation before release packaging. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
lweberru
marked this pull request as ready for review
October 21, 2026 13:00
lweberru
requested review from
BackInBash,
Breeless,
JoshSTACKIT,
LembDo and
dweezl
as code owners
October 21, 2026 13:00
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
1 participant
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.
The Dev release stopped before deployment because its strict governance source receipt still named the previous Accelerator commit, while the platform Runner uses
9e7fb46c329aca32e878ce1f0ea3b944ea240354. Requalify the actual current source and run the complete native Plan contract in ordinary PR validation so this mismatch is caught before a release attempt.Update the reviewed root/governance hashes against that immutable Runner commit. Retain the revision-equality/hash guards and all existing role, owner, parent and duplicate-assignment assertions. Add a negative plan for the current native rejection of non-empty folder descriptions. Document pin qualification and CI coverage in English and German. Native infrastructure, Runner pins and runtime behavior are unchanged.
Completed local validation of the whole affected release section:
npm run test:plan: real saved-plan summary/text checks, 16 Application-root plans, 9 workload-module plans and 4 governance plans, with mocked cloud providers and no customer inputs.package.shwith hosted/platform/Application flags: immutable source fetches, native validation, provider mirror, verified QCOW2, package/disk budget, 12 supported native plans, 2 boundary plans plus missing-PSK rejection, real Vault/STACKIT bootstrap-provider loopback checks, and 3 targeted package tests (128 unrelated/gated skips).check-staged-runner.mjs; both were below 384 MiB (198548152 and 250536424 bytes).The failed Dev release is retained as evidence. After independent review and merge, the already requested Dev exception release can resume with the Assistant enabled and
runner_pool_size=1.Final CI passed on
7d601c4bce79eb69e7a5c439d12c3b13f6fe7530: Validate Configurator, including the newly added complete native Plan/Application/governance check and the full browser suite. Unchanged native formatting/lint/validation suites are scope-skipped; all applicable checks succeeded. Ready for independent review.