Re-pin reflex-base to released 0.9.7#6782
Conversation
reflex-components-core (rx.upload) and reflex-components-radix (rx.segmented_control) now call ArrayVar.map, added in reflex-base 0.9.7 (#6701), so raise their floors to reflex-base >= 0.9.7a1. The alpha lower bound matches the whole 0.9.7 prerelease series (a/b/rc) and the eventual final 0.9.7, so a reflex-base 0.9.7a1 prerelease can be published first and this change's min-deps check resolves green against it. The root reflex floor is bumped too for source accuracy — the publish workflow rewrites it to reflex-base == <version> when building reflex. Second wave of the two-wave release flow (materialize -> publish base -> re-pin), matching #6680 for the 0.9.6 cycle. An alpha pin is not rejected by the check-dev-pins publish gate (only *.dev pins are), so the dependents can also be cut as 0.9.7 prereleases. min-deps stays red until reflex-base 0.9.7a1 is published to PyPI. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KX93fjAHfXYH4UpbSmaSon
Now that the 0.9.7 line is being cut, pin reflex-components-core, reflex-components-radix, and root reflex to reflex-base >= 0.9.7 for the final release, superseding the >= 0.9.7a1 prerelease bound that was used to build the 0.9.7 prereleases from the tagged commit. The min-deps check resolves from PyPI with --no-sources, so this stays red until reflex-base 0.9.7 (final) is published to PyPI. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KX93fjAHfXYH4UpbSmaSon
Greptile SummaryThis PR bumps the
Confidence Score: 5/5Pure dependency metadata update with no runtime code changes; safe to merge once reflex-base 0.9.7 (final) is published to PyPI. All three changed files only update a single version specifier string in pyproject.toml files. No logic, no source files, no lockfile changes. The bump is consistent across sub-packages and correctly reflects the ArrayVar.map requirement introduced in the referenced upstream PR. No files require special attention. Important Files Changed
Reviews (1): Last reviewed commit: "Re-pin reflex-base to released 0.9.7" | Re-trigger Greptile |
Merging this PR will not alter performance
Comparing Footnotes
|
Summary
Second wave of the v0.9.7 release, following the changelog materialization in #6772. Now that the 0.9.7 line is being cut, re-pin the internal
reflex-basefloor to the released version in the packages that callArrayVar.map— added toreflex-base0.9.7 in #6701:reflex-components-corerx.uploadinternalsreflex-base >= 0.9.6→>= 0.9.7reflex-components-radixrx.segmented_controlinternalsreflex-base >= 0.9.5→>= 0.9.7reflex(root)reflex-base >= 0.9.6→>= 0.9.7The root floor is cosmetic — the publish workflow rewrites
reflex-base >= …toreflex-base == <version>when buildingreflex— but is bumped to keep the source honest, matching #6680 for the 0.9.6 cycle.uv.lockis unchanged (workspace members resolve by path), and no packagedsrc/is touched, so no news fragment is required.Note
check-min-depswill be red untilreflex-base0.9.7 (final) is published to PyPI. That job resolves dependencies from PyPI with--no-sources, and a non-prerelease>= 0.9.7bound is not satisfied by the0.9.7a1prerelease. This is expected for the re-pin wave (cf. #6680) and clears once base 0.9.7 ships.All Submissions:
Type of change
Changes To Core Features:
uv lock --checkclean;check-dev-pinspasses — no*.devpins)Generated by Claude Code