Overview

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
ci/couple-npm-github-releases
23a9d36a ci: gate release on a separate test job, least-privilege permissions GitHub releases are created only by the changesets/action step, and that step has not completed cleanly on any release-triggering run since mid-June (last release: @tanstack/ai-react@0.15.5 on 2026-06-15; npm is now at 0.15.12). The "Version Packages" merge runs (#773, #778, #787, #792, #808, #813) passed the test gate and then FAILED at the "Run Changesets" step: CI ran `changeset publish` and npm advanced, but the step died before the tag-push / GitHub-release phase, so no tags (0.15.6-0.15.12 don't exist) and no releases were created. More recent runs (#814, #825) now fail even earlier, at the test gate (test:kiira). (The exact in-step error is no longer recoverable - those runs' logs have expired.) Changes: - Split into a `test` gate job and a `release` job (needs: test) so a flaky run blocks BOTH npm and GitHub releases together, never one without the other. - Tighten permissions: top-level contents:read; write scoped to the release job.
by Alem Tuzlak
Succeeded
ci/couple-npm-github-releases
23a9d36a Merge 3b16c5c2ae6e3fb8b59e720c386702419260f36d into cefeb5251080653525e0bf3c75ea7de9ca61f729
by Alem Tuzlak
Succeeded
ci/couple-npm-github-releases
c65eedf1 ci: gate release on a separate test job; explicit token + least privilege GitHub releases are created only by the changesets/action step, and that step has not completed cleanly on any release-triggering run since mid-June (last release: @tanstack/ai-react@0.15.5 on 2026-06-15; npm is now at 0.15.12). The "Version Packages" merge runs (#773, #778, #787, #792, #808, #813) passed the test gate and then FAILED at the "Run Changesets" step: CI ran `changeset publish` and npm advanced, but the step died before the tag-push / GitHub-release phase, so no tags (0.15.6-0.15.12 don't exist) and no releases were created. More recent runs (#814, #825) now fail even earlier, at the test gate (test:kiira). (The exact in-step error is no longer recoverable - those runs' logs have expired.) Changes: - Split into a `test` gate job and a `release` job (needs: test) so a flaky run blocks BOTH npm and GitHub releases together, never one without the other. - Set GITHUB_TOKEN explicitly on the changesets step. - Tighten permissions: top-level contents:read; write scoped to the release job.
by Alem Tuzlak
Succeeded
ci/couple-npm-github-releases
c65eedf1 Merge a78389c8d3293deb0a404721a3480608d4ad449e into cefeb5251080653525e0bf3c75ea7de9ca61f729
by Alem Tuzlak
Succeeded
ci/couple-npm-github-releases
014e7f38 ci: keep npm publish and GitHub releases coupled, self-heal release gaps GitHub releases are created only by the changesets/action step, and that step has not completed cleanly on any release-triggering run since mid-June (last release: @tanstack/ai-react@0.15.5 on 2026-06-15; npm is now at 0.15.12). The "Version Packages" merge runs (#773, #778, #787, #792, #808, #813) passed the test gate and then FAILED at the "Run Changesets" step: CI ran `changeset publish` and npm advanced, but the step died before the tag-push / GitHub-release phase, so no tags (0.15.6-0.15.12 don't exist) and no releases were created. More recent runs (#814, #825) now fail even earlier, at the test gate (test:kiira), so the changesets step is never reached. Either way npm and GitHub drift apart. (The exact in-step error is no longer recoverable - those runs' logs have expired.) Changes: - Split into a `test` gate job and a `release` job (needs: test) so a flaky run blocks BOTH npm and GitHub releases together, never one without the other. - Add a self-heal step that enforces "published to npm => GitHub release exists": for any package version on npm without a release it creates the tag + release from the CHANGELOG. Runs even when the changesets step fails mid-way, so gaps self-heal on the next release run - directly covering the failure mode above. - Set GITHUB_TOKEN explicitly on the changesets step and tighten permissions (top-level contents:read; write scoped to the release job).
by Alem Tuzlak
Succeeded
ci/couple-npm-github-releases
014e7f38 Merge 79d0d6dba542cfbe3b8abe3d1a72dac71571c8ce into 92a6d50de4fd7ee9ea954e4ed655cf2379d2db54
by Alem Tuzlak
Succeeded
ci/couple-npm-github-releases
7553f9b4 Merge a9ffa7bdf16544101263e5c8bc2c9ec3ce15b4e6 into c04abd35284d464d830bb9f15129c7a7c2533d3f
by Alem Tuzlak
Succeeded
ci/couple-npm-github-releases
7553f9b4 ci: keep npm publish and GitHub releases coupled, self-heal release gaps GitHub releases are created only by the changesets/action step, and that step has not completed cleanly on any release-triggering run since mid-June (last release: @tanstack/ai-react@0.15.5 on 2026-06-15; npm is now at 0.15.12). The "Version Packages" merge runs (#773, #778, #787, #792, #808, #813) passed the test gate and then FAILED at the "Run Changesets" step: CI ran `changeset publish` and npm advanced, but the step died before the tag-push / GitHub-release phase, so no tags (0.15.6-0.15.12 don't exist) and no releases were created. More recent runs (#814, #825) now fail even earlier, at the test gate (test:kiira), so the changesets step is never reached. Either way npm and GitHub drift apart. (The exact in-step error is no longer recoverable - those runs' logs have expired.) Changes: - Split into a `test` gate job and a `release` job (needs: test) so a flaky run blocks BOTH npm and GitHub releases together, never one without the other. - Add a self-heal step that enforces "published to npm => GitHub release exists": for any package version on npm without a release it creates the tag + release from the CHANGELOG. Runs even when the changesets step fails mid-way, so gaps self-heal on the next release run - directly covering the failure mode above. - Set GITHUB_TOKEN explicitly on the changesets step and tighten permissions (top-level contents:read; write scoped to the release job).
by Alem Tuzlak
Succeeded
ci/couple-npm-github-releases
7387113c ci: keep npm publish and GitHub releases coupled, self-heal release gaps GitHub releases are created only by the changesets/action step, and that step has not completed cleanly on any release-triggering run since mid-June (last release: @tanstack/ai-react@0.15.5 on 2026-06-15; npm is now at 0.15.12). The "Version Packages" merge runs (#773, #778, #787, #792, #808, #813) passed the test gate and then FAILED at the "Run Changesets" step: CI ran `changeset publish` and npm advanced, but the step died before the tag-push / GitHub-release phase, so no tags (0.15.6-0.15.12 don't exist) and no releases were created. More recent runs (#814, #825) now fail even earlier, at the test gate (test:kiira), so the changesets step is never reached. Either way npm and GitHub drift apart. (The exact in-step error is no longer recoverable - those runs' logs have expired.) Changes: - Split into a `test` gate job and a `release` job (needs: test) so a flaky run blocks BOTH npm and GitHub releases together, never one without the other. - Add workflow_dispatch so a maintainer recovers a blocked release by re-running the workflow (publish is idempotent) instead of intervening by hand. - Add a self-heal step that enforces "published to npm => GitHub release exists": for any package version on npm without a release it creates the tag + release from the CHANGELOG. Runs even when the changesets step fails mid-way and on manual re-runs, so gaps self-heal - directly covering the failure mode above. - Set GITHUB_TOKEN explicitly on the changesets step and tighten permissions (top-level contents:read; write scoped to the release job).
by Alem Tuzlak
Succeeded
ci/couple-npm-github-releases
7387113c Merge cda8ae34c091e70c1a86a10ae5e2abd73a93bfec into f3144a6c69d1e8abdbf21bd722c9e68208c8be81
by Alem Tuzlak
Succeeded
ci/couple-npm-github-releases
764fabf9 ci: keep npm publish and GitHub releases coupled, self-heal release gaps GitHub releases are created only by the changesets/action step, and that step has not completed cleanly on any release-triggering run since mid-June (last release: @tanstack/ai-react@0.15.5 on 2026-06-15; npm is now at 0.15.12). The "Version Packages" merge runs (#773, #778, #787, #792, #808, #813) passed the test gate and then FAILED at the "Run Changesets" step: CI ran `changeset publish` and npm advanced, but the step died before the tag-push / GitHub-release phase, so no tags (0.15.6-0.15.12 don't exist) and no releases were created. More recent runs (#814, #825) now fail even earlier, at the test gate (test:kiira), so the changesets step is never reached. Either way npm and GitHub drift apart. (The exact in-step error is no longer recoverable - those runs' logs have expired.) Changes: - Split into a `test` gate job and a `release` job (needs: test) so a flaky run blocks BOTH npm and GitHub releases together, never one without the other. - Add workflow_dispatch so a maintainer recovers a blocked release by re-running the workflow (publish is idempotent) instead of intervening by hand. - Add a self-heal step that enforces "published to npm => GitHub release exists": for any package version on npm without a release it creates the tag + release from the CHANGELOG. Runs even when the changesets step fails mid-way and on manual re-runs, so gaps self-heal - directly covering the failure mode above. - Set GITHUB_TOKEN explicitly on the changesets step and tighten permissions (top-level contents:read; write scoped to the release job).
by Alem Tuzlak
Succeeded
ci/couple-npm-github-releases
764fabf9 Merge 33c9523c96e160779a54bdc502b852286236417d into f3144a6c69d1e8abdbf21bd722c9e68208c8be81
by Alem Tuzlak
Succeeded
ci/couple-npm-github-releases
80e13647 ci: keep npm publish and GitHub releases coupled, self-heal release gaps GitHub releases are created only by the changesets/action step. Since mid-June that step has not completed on any release-triggering run: the "Version Packages" merge runs either failed at the test gate (e.g. test:kiira) before reaching it, or failed inside the changesets step after publishing to npm. Packages still reached npm via manual `changeset publish` from a laptop, which pushes no git tags and creates no GitHub releases - decoupling the two. Changes: - Split into a `test` gate job and a `release` job (needs: test) so a flaky run blocks BOTH npm and GitHub releases together, never one without the other. - Add workflow_dispatch so a maintainer recovers a blocked release by re-running the workflow (publish is idempotent) instead of hand-publishing npm. - Add a self-heal step that enforces "published to npm => GitHub release exists": for any package version on npm without a release it creates the tag + release from the CHANGELOG. Runs even when the changesets step fails mid-way and on manual re-runs, so gaps self-heal. - Set GITHUB_TOKEN explicitly on the changesets step and tighten permissions (top-level contents:read; write scoped to the release job).
by Alem Tuzlak
Succeeded
ci/couple-npm-github-releases
80e13647 Merge 6c08f6d460a50c80d80f890c2a6714f990f29468 into f3144a6c69d1e8abdbf21bd722c9e68208c8be81
by Alem Tuzlak