charlie:

[shellscape]

@CharlieHelps please create a PR to merge the OIDC and react-router commits from main into the next/v3 branch. Do this as a separate branch with manual changes rather than trying to merge main into next/v3.

[charliecreates]

Expand this to see my work.

• Reviewed the OIDC-related changes on main (provider wiring, token handling) and mapped the corresponding manual updates needed on next/v3.
• Reviewed the react-router integration on main, including key route definitions and hooks like useNavigate/useLocation, to understand what must be preserved in next/v3.
• Identified and cross-referenced relevant files on main (oidcConfig.ts, AuthProvider.tsx, routing setup) with their next/v3 counterparts to prepare for a targeted port.
• Fetched the latest origin/main refs and confirmed the OIDC (1232d5ff) and react-router-dom (f6391f3e) commits to be represented on chore/repo/port-oidc-react-router-v3.
• Ported the OIDC release workflow updates into .github/workflows/release.yml (including permissions.id-token: write and an OIDC Preflight step) and aligned .npmrc with the post-OIDC pnpm settings from main.
• Applied the typing fix from main in packages/jsx-email/src/renderer/raw.ts so matches.push({ index, node, parent }); no longer relies on a node as Element cast.
• Bumped react-router-dom to 7.12.0 in packages/jsx-email/package.json while keeping the root pnpm-lock.yaml at the next/v3 baseline so the branch diff stays focused.
• Committed the OIDC-related port as chore(repo,jsx-email): port OIDC release publishing to next/v3 and the router bump as chore(jsx-email): upgrade react-router-dom to 7.12.0, then ran pnpm moon run repo:lint (0 errors, existing warnings only).
• Created PR #398 from chore/repo/port-oidc-react-router-v3 to next/v3 with a filled-out template, a detailed verification section (pnpm moon run repo:lint, pnpm moon run jsx-email:compile, pnpm moon run jsx-email:test --cache off), and resolves #397 in the body.
• Updated PR #398 to request review from CharlieHelps and captured the full main commit hashes (7033b053f3cc5f00af8c48701f08ba75a4c33a11, e627a96643cd682b0c5ca3b5822b3e29ac1752cd) for accurate linkage back to the original OIDC and router changes.

[charliecreates]

Opened PR #398 to bring the OIDC release workflow + react-router-dom bump from main into next/v3 (without merging main into next/v3): #398

Changes

• Ported OIDC publishing adjustments into next/v3’s release workflow (job-level id-token: write, OIDC preflight, remove NPM_TOKEN env usage) in 7033b053.
• Synced root .npmrc to match main (no auth token line; pnpm workspace options) in 7033b053.
• Bumped packages/jsx-email react-router-dom to 7.12.0 in e627a966.

Verification

# Lint: 0 errors (31 warnings)
pnpm moon run repo:lint

# TypeScript: jsx-email compile OK
pnpm moon run jsx-email:compile

# Tests: failing on next/v3 baseline too (Vite cannot resolve @jsx-email/plugin-inline during Vitest)
pnpm moon run jsx-email:test --cache off

• jsx-email:test fails on both this branch and origin/next/v3 at b4eee537 due to Vite “Failed to resolve entry for package @jsx-email/plugin-inline”.