TanStack
OSS
pacer
Sign in / Sign up
Open main menu
pacer
GitHub
Overview
Runs
Analytics
Loading workspace stats
Loading workspace insights...
Statistics interval
7 days
30 days
Latest CI Pipeline Executions
Status
Fix filter
Filter
Fuzzy
Filter range
Sort by
Sort by
Start time
Sort ascending
Sort descending
Succeeded
main
f8d4d576 fix(publish-fork): derive repository.url from current repo for provenance The script rewrote repository.url to a hardcoded dogmar/pacer, left over from before the repo moved to the klink-ing org. npm --provenance signs an attestation from the GitHub OIDC token, and the registry rejects the publish (E422) unless repository.url matches the repo that produced it — so every package failed with dogmar/pacer != klink-ing/pacer. Derive the slug from GITHUB_REPOSITORY (the Actions context) so it tracks the real repo and won't drift on a future rename, falling back to the fork slug for local runs.
by Claude
C
Succeeded
claude/fix-publish-provenance-repo-url
6f4d0bb5 fix(publish-fork): derive repository.url from current repo for provenance The script rewrote repository.url to a hardcoded dogmar/pacer, left over from before the repo moved to the klink-ing org. npm --provenance signs an attestation from the GitHub OIDC token, and the registry rejects the publish (E422) unless repository.url matches the repo that produced it — so every package failed with dogmar/pacer != klink-ing/pacer. Derive the slug from GITHUB_REPOSITORY (the Actions context) so it tracks the real repo and won't drift on a future rename, falling back to the fork slug for local runs.
by Claude
C
Succeeded
main
4cd6a7e3 ci(sync-upstream): treat closed sync PRs as existing A closed (not merged) sync PR means the version was deliberately rejected. The prior open-only check let it through, but gh pr create refuses a second PR for a head that already has one, so the recovery path still wedged. Match PRs in any state so a closed PR skips the sync.
by Claude
C
Succeeded
claude/peaceful-euler-eEY69
b2f0d495 ci(sync-upstream): treat closed sync PRs as existing A closed (not merged) sync PR means the version was deliberately rejected. The prior open-only check let it through, but gh pr create refuses a second PR for a head that already has one, so the recovery path still wedged. Match PRs in any state so a closed PR skips the sync.
by Claude
C
Succeeded
claude/peaceful-euler-eEY69
847fcaaf ci(sync-upstream): keep zizmor.yml and CODEOWNERS deleted on sync The fork removed .github/workflows/zizmor.yml and .github/CODEOWNERS, both of which still exist upstream. An upstream edit to either surfaces as a modify/delete conflict (same as release.yml), which previously fell through to the manual-review path and aborted the merge. Resolve them back to 'deleted' automatically so the fork's removals are preserved.
by Claude
C
Succeeded
main
88591ffd ci(sync-upstream): bump actions/checkout to v6.0.2 Resolves Node.js 20 deprecation warning by upgrading to the Node.js 24 compatible release, matching the other workflows in the repo.
by Claude
C
Succeeded
main
36e67175 Switch upstream sync from cherry-pick to merge strategy Cherry-picking fork commits onto upstream/main fails whenever there are conflicts in any individual commit. Instead, branch from origin/main and merge upstream/main in, which is more robust and produces a single merge commit that's easier to resolve if conflicts do arise. https://claude.ai/code/session_01QCPv9A7pkCeR42zoJ9fujU
by Claude
C
Previous page
Previous
Next
Next page