v1.0.0 release plan: PR merge order and beta tagging

[netchampfaris]

Planning doc for cutting v1.0.0. Captures which open PRs gate the release, the merge order, and when to tag beta.

v1-track (must land before/with beta)

• feat(tokens)!: adopt espresso v2 tokens + codemod migration #727 — feat(tokens): sync espresso v2 from Figma + rebuild foundations docs. The foundation everything else sits on (tokens v2, Pill primitive, focus-ring, elevation).
• fix(Combobox, Select): pin #footer outside scrollable viewport, add footer slot props (#717) #726 — Combobox #footer slot fix (draft, small). Easy companion.
• chore: deprecated warning message for Autocomplete #472 — Autocomplete deprecation warning. Aligns with the deprecated-components plan (Popover, Toast, Autocomplete).
• feat(editor): Editor molecule #718 — editor molecule family. Large (~19k adds). Land after feat(tokens)!: adopt espresso v2 tokens + codemod migration #727 so it rebases onto the new tokens.

Safe small fixes to bundle in the beta cycle

• fix: accept common CSV MIME types for uploads #673 — accept common CSV MIME types
• fix(tailwind): do not manipulate img in dark mode #630 — do not manipulate img in dark mode
• feat(createResources): abort method to cancel ongoing fetch requests #494 — abort method for createResource
• fix(createResource): onError() called thrice #488 — onError called thrice

All tiny, all safe, batch them into a single beta bump.

Defer past v1.0.0 (do NOT block on these)

• feat: setup formatting #613 — oxlint formatting. ~6k/5k churn; do this after beta when the API surface is frozen, otherwise every other PR will conflict.
• frappe/client — data-fetching v3 #610 — data-fetching v3. Separate track, ship as 1.1 or under a frappe/* subpackage bump.
• refactor: Link Control for frappe #704 — Link Control refactor. Separate track.
• feat: improved table #561 feat: add resizable layout primitives #542 fix: tables menus, size handler and copy pasting to new tab #538 feat: Add attachment support to TextEditor (fixes #527) #530 feat: enhance TextEditor add underline option in the texteditor menu #526 feat: add skeleton component #524 feat: add hovercard component #523 feat: Add context menu component #522 Making list group header span dark mode comp. #414 feat: useBulkUpdate #393 fix: Autocomplete component Disabled State #377 feat: Add "Text Justify" in the TextEditor component #328 feat: ability for alternative auth in useList & useDoc #323 — community / older PRs. Most are superseded, untouched in months, or land in surfaces being deprecated (Autocomplete, old TextEditor). Triage in a separate pass; do not let them gate beta.
• feat(wip): automations #505 — automations (WIP draft).

Suggested merge / tag order

1. Merge feat(tokens)!: adopt espresso v2 tokens + codemod migration #727 → cut v1.0.0-beta.0. "Tokens are locked" milestone — what consumers need a stable pin for.
2. Rebase feat(editor): Editor molecule #718 onto new main, merge → beta.1.
3. Bundle fix(Combobox, Select): pin #footer outside scrollable viewport, add footer slot props (#717) #726 chore: deprecated warning message for Autocomplete #472 fix: accept common CSV MIME types for uploads #673 fix(tailwind): do not manipulate img in dark mode #630 feat(createResources): abort method to cancel ongoing fetch requests #494 fix(createResource): onError() called thrice #488 → beta.2.
4. Land feat: setup formatting #613 formatting → beta.3 (after API surface settles, before final).
5. Tag v1.0.0 once a real consumer (Gameplan / CRM / Helpdesk) has been on beta.N for ~1 week without surprises.

Beta timing

Tag after #727 lands, not before. Tagging from current main would force every consumer to switch their pin the moment #727 merges, which defeats the point of having a beta.

Distribution

• Publish to npm under the beta dist-tag so colleagues install with yarn add frappe-ui@beta instead of frappe/frappe-ui#main.
• Each beta.N bump gets a changelog entry calling out breaking changes explicitly.

Open questions

• Pick the first downstream consumer to dogfood beta.0 (Gameplan?).
• Decide whether frappe/* and drive/* subpath exports follow the same 1.0.0-beta cadence or version independently.
• Confirm 1.0.0 exit criteria (no beta.N regressions for N days? all v1-track PRs merged? deprecated components removed or still warned?).