Skip to content

fix(desktop): hold the Clerk canary until it can actually build - #11

Merged
sheehanmunim merged 1 commit into
mainfrom
fix/clerk-canary-revert
Aug 19, 2026
Merged

sheehanmunim merged 1 commit into
mainfrom
fix/clerk-canary-revert

Conversation

@sheehanmunim

Copy link
Copy Markdown
Member

What changed

Reverted the Clerk canary bump that arrived with upstream's passkey fix:

  • @clerk/electron back to 0.0.24, @clerk/electron-passkeys (and its platform packages) back to 0.0.3
  • Dropped electronPasskeys.test.ts, which exercises the conditionalUI argument only the 0.0.4 SDK has. It returns with the bump.

Why

Two independent blockers, both fatal to a desktop build:

  1. The published natives are empty. @clerk/electron-passkeys-darwin-arm64@0.0.4-canary.v20260819050620 is a 1 KB tarball containing package.json and LICENSE — no .node. Staging fails with ClerkPasskeyNativePackageMissingError and the Mac build dies.
  2. The repo's own supply-chain policy rejects them. All six canary packages were published inside the minimumReleaseAge window, so pnpm install refuses the lockfile on every fleet machine.

@clerk/electron@0.0.34-canary peer-requires the broken passkeys build, so pinning only the natives was not enough. Upstream's actual behavioural fix — the pinned __internal_clerkUIVersion — is a runtime string and stays.

Checks

  • Targeted typechecks (web, desktop) clean
  • @clerk/electron-passkeys-darwin-arm64@0.0.3 resolves its .node again, which is what the desktop build stages

Upstream's passkey fix brought @clerk/electron 0.0.34-canary and passkeys
0.0.4-canary. Neither can build here: the published native tarballs are 1 KB
with no .node binary, and all six canary packages fall inside the repo's
minimumReleaseAge policy, so pnpm install refuses the lockfile on every fleet
machine.

Pins back to @clerk/electron 0.0.24 and passkeys 0.0.3, and drops the test
that uses the 0.0.4-only conditionalUI argument. Upstream's actual fix - the
pinned __internal_clerkUIVersion - is a runtime string and stays.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@sheehanmunim
sheehanmunim merged commit 2593735 into main Aug 19, 2026
4 of 9 checks passed
@sheehanmunim
sheehanmunim deleted the fix/clerk-canary-revert branch August 19, 2026 17:22
@github-actions github-actions Bot added vouch:trusted PR author is trusted by repo permissions or the VOUCHED list. size:M labels Aug 19, 2026
sheehanmunim added a commit that referenced this pull request Sep 10, 2026
MIT permits redistribution under other terms, so the work as a whole is now
Apache-2.0. What MIT does not permit is dropping its copyright notice: T3
Code's code is most of this repository and its notice has to travel with it,
so upstream's MIT text stays as LICENSE-MIT and NOTICE records why both files
are here.

The comparison table now lists only differences. Nine rows had a tick in both
columns, which is not a comparison — drag-to-reorder, PDF attachments, cookie
import, tool-activity grouping, composer drawers, preview viewport, file-chip
reveal, macOS editor discovery and pull request stacks. Every one of those
except the stacks already runs T3 Code's implementation rather than the
fork's; the sidebar drag modules, in particular, are byte-identical upstream.

Also restores `electronPasskeys.test.ts`, dropped in #11 when the Clerk canary
could not build and never brought back after the catalog caught up. With it
there is no upstream file this fork is missing.

Also removes what should never have been committed, by this repository's own
rules: `.github/pr-assets/`, three agent scratch files, and an `undefined/`
directory a cookie-import test wrote a Firefox profile into.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:M vouch:trusted PR author is trusted by repo permissions or the VOUCHED list.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant