[masenf]

The 0.10 prerelease train needs sibling releases that include the Python 3.11 minimum. Raise every runtime sibling floor to the .dev0 of the sibling's next version, so each dependent's floor lifts to the release an earlier phase publishes. Exclude the earlier hosting CLI alpha that predates the Python floor change, and let the hosting CLI take the SDK's upcoming 0.1.0 train within its cap.

Make publish-last lockstep groups directional:

• Early members (reflex-base) release on their own, from their own baseline, and get their own Dispatch checkbox.
• A publish-last member (reflex) advances from its own baseline and needs every early member tagged at that version. An existing tag is reused; otherwise the early member is planned alongside. Planning checks the exact pin against the declared requirement, so a floor raised past the reusable tag stops the release before any changelog is bumped.
• publish-last members need only the early members, never each other, so pin-exact groups with several late members cannot deadlock.
• A package with an unsatisfiable pin is held back before its version is planned, so an action that does not apply to it cannot stop its siblings. A package whose needed partner is blocked is held back with it; an explicit selection that cannot release fails.
• prepare-publish requires the early members' tags before a late member builds, including for a manual publish dispatch.
• Groups without publish-last keep their symmetric behaviour and shared checkbox.

Release order

This is one valid schedule for the current branch. Component names below omit reflex-components-. Wait for each phase's uploads and tags before materializing the next; when new-prerelease-minor returns a new branch, use that branch for subsequent phases.

Phase	Action	Packages and target versions
1	continued-prerelease	reflex-base 0.10.0a2
2	new-prerelease-minor	reflex-build-sdk 0.1.0a1, reflex-release 0.2.0a1, lucide 1.1.0a1
3	new-prerelease-minor	reflex-hosting-cli 0.2.0a1, sonner 0.10.0a1
4	continued-prerelease	core, gridjs, moment 0.10.0a2
5	new-prerelease-minor	dataeditor, react-player 0.10.0a1
6	continued-prerelease	radix, plotly, recharts 0.10.0a2
7	continued-prerelease	code 0.10.0a2
8	continued-prerelease	markdown 0.10.0a2
9	continued-prerelease	reflex 0.10.0a2, reusing the base tag from phase 1
10	continued-prerelease	reflex-docgen 0.10.0a2

Validation

• The release, min-deps and workflow-gate unit suites pass, with new coverage for tag reuse, the plan-time pin check, independent late members, a blocked dependent held back ahead of an inapplicable action, and explicit selection of a blocked dependent.
• Ruff, pyright, uv lock --check and reflex-release sync --check are clean.
• scripts/check_min_deps.py passes for reflex-hosting-cli and reflex-release. It fails for reflex and the components on this branch because uv does not opt into prereleases for a transitive dev floor (hosting-cli on reflex-build-sdk, core on sonner). Those floors lift to published versions as the phases run, and the check does not run for pull requests into r/pre-*.

Submission checklist

• Followed CONTRIBUTING.md and checked for an existing PR covering this change.
• Added regression tests and verified them locally.
• Updated documentation and package news fragments.
• Linted and formatted the changes.

🤖 Generated with Claude Code

https://claude.ai/code/session_01MZxGmMwCvKGcUJu6TK99jZ

<source media="(prefers-color-scheme: dark)" srcset="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"><source media="(prefers-color-scheme: light)" srcset="https://www.cubic.dev/buttons/review-in-cubic-light.svg"><img alt="Review in cubic" src="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"> <source media="(prefers-color-scheme: dark)" srcset="https://www.cubic.dev/buttons/turn-on-auto-fix-dark.svg"><source media="(prefers-color-scheme: light)" srcset="https://www.cubic.dev/buttons/turn-on-auto-fix-light.svg"><img alt="Turn on auto-fix" src="https://www.cubic.dev/buttons/turn-on-auto-fix-dark.svg">

[greptile-apps]

Confidence Score: 5/5

[High risk] Restructures release workflow and dependency version floors.

No new blocking issue was established; the remaining action-order case belongs to the existing review thread.

What we checked:

• Late builds cannot run ahead: prepare-publish rejects a late member when the required early tag is missing.

Summary

Raises sibling dependency floors for the Python 3.11 release train and lets early members of publish-last groups release separately.

• Adds separate release checkboxes and reuses matching early-member tags.
• Checks exact pins before changing changelogs and requires early-member tags before late builds.
• Adds release-planning tests and isolates the minimum-dependency test from changing workspace floors.
• masenf dismissed the timeout and missing-product findings because those changes came from main, outside this PR.

_{Reviews (6) · Last reviewed commit: "Merge branch 'r/pre-2026.10.05-373789289..." · Reviewed by Greptile}

[codspeed]

Merging this PR will regress 1 benchmark

⚠️ Different runtime environments detected

Some benchmarks with significant performance changes were compared across different runtime environments,
which may affect the accuracy of the results.

Open the report in CodSpeed to investigate

⚡ 2 improved benchmarks
❌ 1 regressed benchmark
✅ 147 untouched benchmarks
⏩ 18 skipped benchmarks¹

Warning

Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

	Benchmark	BASE	HEAD	Efficiency
❌	test_state_access[read_inherited]	40.8 ms	43.2 ms	-5.55%
⚡	test_hydration_metadata[200]	2 ms	1.7 ms	+16.65%
⚡	test_hydration_metadata[20]	215.6 µs	206.9 µs	+4.21%

Tip

Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.

---

_{Comparing codex/reflex-010-prerelease-floors (cfbd93a) with main (8239259)²}

Footnotes

1. 18 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

2. No successful run was found on r/pre-2026.10.05-37378928999 (052ca91) during the generation of this report, so main (8239259) was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩

[cubic-dev-ai]

1 issue found across 33 files

<sub>Reply with feedback, questions, or to request a fix.

Turn on auto-fix | Re-trigger cubic</sub>

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name=".github/workflows/release_from_changelog.yml">

<violation number="1" location=".github/workflows/release_from_changelog.yml:23">
P3: This says each exact-pin member waits for every package in the batch, but `publish-last` members require only early-member tags and can run alongside other late members. Name the required early siblings to avoid implying an unnecessary serial dependency.</violation>
</file>