Repository navigation
Raise sibling dependency floors to the 0.10.1 dev train - #7662
Conversation
Pin reflex-components-code and reflex-components-dataeditor at >= 0.10.1.dev0, reflex-components-lucide at >= 1.1.1.dev0 and reflex-hosting-cli at >= 0.2.1.dev0, matching the floors already set for reflex-base, moment and radix. In 0.10.1a1 pre-release testing a plain `pip install --pre reflex` satisfied these four siblings with their stable releases, producing a mixed graph of 0.10.1a1 and 0.10.0-era packages. The lifted floors are met by the 0.10.1a1-train alphas and by every workspace build after the latest stable tags, so check-min-deps still passes, and the stale `!= 0.1.73a1` exclusion on reflex-hosting-cli is subsumed by its new floor. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015caj5Fccjk1u36n5F6cn5J
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
There was a problem hiding this comment.
No issues found across 1 file
Tip: Get a Slack DM when cubic finishes reviewing your PRs. Connect Slack
View guided diff | Turn on auto-fix | Re-trigger cubic
 [Medium impact] The dependency floor changes appear safe to merge. SummaryRaises four sibling dependency floors to the next development versions:
Removes the redundant hosting version exclusion. No actionable issues found.
Reviews (1) · Last reviewed commit: "Raise sibling dependency floors to the 0..." · Reviewed by Greptile |
Merging this PR will not alter performance1 warning
Comparing 
|
Requested by Masen · project thread
Type of change
Description
Lifts the root
pyproject.tomlfloors for the four sibling packages that were still pinned at their stable releases, matching the.dev0floors already set forreflex-base,reflex-components-momentandreflex-components-radix:>= 0.10.0>= 0.10.1.dev0>= 0.10.0>= 0.10.1.dev0>= 1.1.0>= 1.1.1.dev0>= 0.2.0, != 0.1.73a1>= 0.2.1.dev0Lucide and hosting-cli follow their own version lines, so their floors are the
.dev0of the version after their latest stable tag (reflex-components-lucide-v1.1.0,reflex-hosting-cli-v0.2.0); each already has a matchinga1tag from the 0.10.1a1 train. The!= 0.1.73a1exclusion is subsumed by the new floor and dropped.During 0.10.1a1 pre-release testing,
pip install --pre reflexsatisfied these four siblings with their stable releases, giving a mixed 0.10.1a1 / 0.10.0-era graph. With the lifted floors the resolver must pick the matching alphas.uv.lockrecords workspace members as editable sources without specifiers, so it is unchanged (uv lockis a no-op). No news fragment: dependency floor bumps are not a user-facing framework change, so this should carryskip-changelog.Generated by Claude Code