Repository navigation
Your pipeline passed yesterday. Today it fails. Test what changed.
This Action update defaults to the published, checksum-verified WorldBisect engine 1.2.1 on Linux AMD64 and ARM64. The Action and engine use separate release versions.
- uses: ClusterPilot-System/worldbisect@db6b33f891779cf8e636393cf0b6afb242f6a282 # action-v1.0.1
with:
mode: ci
command: '["./ci/check.sh"]'
files: |
ci/check.sh
config/app.confRun successfully on the default branch first. A later failed check can retrieve compatible selected inputs and test changes on the current runner. Select only safe files: their raw contents are retained, for seven days by default. If the failure cannot be reproduced, the result says so.
Default compare mode remains available for existing explicit-workspace integrations. Both implementations are pinned to reviewed commit 1ef4595f36e5153a1f4c072b6d115e4104d00dba.
- Merged change and validation
- Engine 1.2.1 binaries, checksums and release notes
- Run the first diagnosis
- CI setup, permissions and retention
- Proof boundary
The actual 1.2.1 demo reports PROVEN for a deliberately changed configuration file in nine experiments. Both released-engine architectures, root compare mode and required CI checks passed. This is tested evidence from a controlled regression, not a customer adoption or performance claim.
The team report hub remains an experimental source-built preview. This release does not announce a managed SaaS.
Existing immutable tags and engine assets are unchanged.
Verified on the release commit: successful baseline → automatic dispatcher → separate controlled failure. The test observed PROVEN and preserved the original failing outcome and exit code. Live OIDC verification also passed.