Overview - Virtual

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
mintaka-rig-2213-virtual-ci
83f6f10c ci: fail closed when the test gate fails or skips (RIG-2213) The `CI` aggregator used a bare `needs: [test]` (default `if: success()`), so when `test` fails GitHub marks `CI` `skipped`, not `failure` — and branch protection treats a skipped required check as passing. That would let a red `test` merge, defeating the gate on exactly the failure it exists to catch. Run the aggregator with `if: always()` and fail explicitly unless `needs.test.result == success`, so the required `CI` check reports red whenever `test` is not green. Spec-impact: none
by mintaka
Succeeded
mintaka-rig-2213-virtual-ci
f1f8ff9e ci: scope PR preview publish to upstream owner on the fork (RIG-2213) The `preview` job in pr.yml runs `pkg-pr-new publish`, which needs an NX_CLOUD_ACCESS_TOKEN / registry creds we don't hold on the fork and publishes no artifact the monorepo consumes (we pull @tanstack/virtual-core from npm). It shares pr.yml with the CI producer and the real `test` gate, so it can't be file-disabled. Guard it with the same `if: github.repository_owner == 'TanStack'` idiom the fork's own release.yml already uses, so it skips cleanly on RigelBuild instead of reddening every PR. Spec-impact: none
by mintaka
Succeeded
mintaka-rig-2213-virtual-ci
b06ae97f Merge 4e8c807666afdcc80cf40295cb07ed613d9e215e into e9874f033c74afd3251eeb9f3e60b2530cc7ae88
by mintaka-agent
Failed
marko-virtual-ts
2dcec335 Merge 51369ffade84fcf432cca950b67396f84f71eb0c into f13ecb6ad1af086b413f72aeb0784ce821ee5263
by defunkt-dev