Skip to content

Sync upstream v0.21.0 + fix sync-upstream workflow - #10

Merged
dogmar merged 9 commits into
mainfrom
claude/fix-merge-push-S0fV8
Apr 22, 2026
Merged

dogmar merged 9 commits into
mainfrom
claude/fix-merge-push-S0fV8

Conversation

@dogmar

@dogmar dogmar commented Apr 21, 2026

Copy link
Copy Markdown
Collaborator

Summary

Manually recovers the v0.21.0 upstream sync (previously stranded as the orphan sync/v0.21.0-20260420 branch with no PR) and fixes the sync-upstream workflow bug that caused the orphan state.

Root cause

From the 20260420 run log:

pull request create failed: GraphQL: Resource not accessible by integration (createPullRequest)

gh CLI inside a fork checkout defaults its "base repo" to the parent (TanStack/pacer). gh pr create was trying to open the PR against upstream where GITHUB_TOKEN has no write access → 403. The branch was already pushed at that point, leaving it stranded without a PR. gh pr list earlier in the workflow had the same bug silently — always querying the wrong repo.

Changes

  • .github/workflows/sync-upstream.yml — add GH_REPO: ${{ github.repository }} to the Check for existing PR and Create PR steps so gh targets the fork. 5 lines.
  • Merge upstream/main (8428657) — recovers the v0.21.0 release:
    • pacer: v0.20.1 → v0.21.0
    • angular-pacer: v0.22.1 → v0.23.0
    • pacer-devtools: v1.2.1 → v1.3.0
    • preact-pacer: v0.21.1 → v0.22.0
    • preact-pacer-devtools: v0.6.1 → v0.6.2
    • react-pacer: v0.21.1 → v0.22.0
    • react-pacer-devtools: v0.6.1 → v0.7.0
    • solid-pacer: v0.20.1 → v0.21.0
    • solid-pacer-devtools: v0.6.1 → v0.6.2

After merging

  • The publish-fork workflow will republish the packages whose versions changed.
  • The stale sync/v0.21.0-20260417 and sync/v0.21.0-20260420 orphan branches can be deleted — their content is already in this PR.

https://claude.ai/code/session_01XftXTi67nbf71Y9wNZ833A

renovate Bot and others added 7 commits April 1, 2026 04:32
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…#202)

* feat: upgrade tanstack store versions with useSelector hook

* changeset
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@dogmar dogmar changed the title Fix sync-upstream workflow to check for existing branches Sync upstream v0.21.0 + fix sync-upstream workflow Apr 22, 2026
gh CLI inside a fork checkout defaults its base repo to the parent
(TanStack/pacer). That meant gh pr create was trying to open the PR
against upstream where GITHUB_TOKEN has no access, failing with:

  pull request create failed: GraphQL: Resource not accessible by
  integration (createPullRequest)

The branch was already pushed by then, leaving it stranded without a
PR. The gh pr list check earlier in the workflow had the same bug
silently — it was querying the parent, not the fork.

Setting GH_REPO on both steps forces gh to target the fork.
@dogmar
dogmar force-pushed the claude/fix-merge-push-S0fV8 branch from 067d04c to 6fabe7d Compare April 22, 2026 04:13
@dogmar
dogmar merged commit d308cb8 into main Apr 22, 2026
3 checks passed
@dogmar
dogmar deleted the claude/fix-merge-push-S0fV8 branch April 22, 2026 04:21
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