Repository navigation
fix(ci): budget Runner package inspection and clarify Namespace scope - #132
Merged
Merged
Conversation
10 of 21 tasks
lweberru
marked this pull request as ready for review
October 21, 2026 18:42
lweberru
requested review from
BackInBash,
Breeless,
JoshSTACKIT,
LembDo and
dweezl
as code owners
October 21, 2026 18:42
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 qualified Dev release on merged #131 passed all 118 repeated live Assistant cases and the 13-step continuous journey, then stopped before deployment because the local Runner package-identity test exceeded Vitest's default 5-second budget. The failed source-bound run remains recorded: https://github.com/stackitcloud/stackit-landing-zone/actions/runs/39650742104 .
Give the local Runner test file a bounded 30-second test budget. These cases copy/hash the real Node runtime and perform multiple engine probes, each of which retains its existing 10-second production deadline. Assertions, source/artifact checks, model oracles and all production timeouts are unchanged. The test remains part of the ordinary CI and qualified release checks; there is no retry or skip.
Also clarify the confirmed Namespace boundary in the English/German user guide and execution reference: Accelerator Namespace services have always targeted Platform Kubernetes only. They are excluded from Application project ordering; namespaces in a cluster within an Application Landing Zone belong to its workload. Private/SNA Platform Kubernetes remains deferred under #37. Possible much later Building Blocks layered on Application Landing Zones are a separate product decision, not an acceptance dependency for current Public/Corporate project ordering.
Validation:
npm run checkpasses (lint/types/build and 997 unit tests; 71 environment-gated skips);git diff --checkpasses. Public Dev health/access checks pass and deployed asset hashes are unchanged, confirming the failed release did not deploy. No customer infrastructure operation was performed. The Dev-release authorization already exists; after review/merge, a fresh qualified source-bound release is required.Related: #93, #37; follows #131.
Final GitHub acceptance on
67bb5daa28bb699ccb6c00ac179cc3a8b7ea0a2c: all applicable checks pass, including the complete Application/native/database suites and 312 desktop/mobile browser cases: https://github.com/stackitcloud/stackit-landing-zone/actions/runs/39654012523 . The unchanged native scope detector correctly skips native root-only jobs because no native Terraform sources changed. Protected main still requires independent review before merge.