Skip to content

fix(ci): run the StackPack validator in CI - #33

Merged
VioletCranberry merged 1 commit into
mainfrom
run-stackpack-validator
Oct 12, 2026
Merged

VioletCranberry merged 1 commit into
mainfrom
run-stackpack-validator

Conversation

@VioletCranberry

Copy link
Copy Markdown
Contributor

The validate job ran stackstate-server instead of the validator, so it exited 0 without validating anything. This applies the fix from StackVista/suse-stackpacks#26: run the validator through its entrypoint on a digest-pinned current image, add an invalid fixture the job must reject, and publish only after packaging succeeds.

Validation: run locally with the pinned image, all three StackPacks pass and the fixture is rejected with the expected error. Shellcheck and actionlint pass.

The validate job started stackstate-server instead of the validator,
which printed usage and exited 0, so StackPacks shipped unvalidated.
Run the validator through its own entrypoint on a digest-pinned
current image, reject an invalid fixture so a silent no-op fails, and
require successful packaging before image publication.
@VioletCranberry
VioletCranberry force-pushed the run-stackpack-validator branch from 05870d9 to d873421 Compare October 12, 2026 13:37
@VioletCranberry
VioletCranberry merged commit 1b6b01a into main Oct 12, 2026
12 checks passed
@VioletCranberry
VioletCranberry deleted the run-stackpack-validator branch October 12, 2026 13:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants