Materialize changelogs for reflex v0.9.6 and friends#6679
Conversation
Build the pending news fragments into CHANGELOG.md for the framework and the modified subpackages. Each version is the next dot bump from the package's latest release tag: - reflex 0.9.5.post2 -> 0.9.6 - reflex-base 0.9.5.post2 -> 0.9.6 - reflex-components-core 0.9.5 -> 0.9.6 - reflex-components-moment 0.9.1 -> 0.9.2 - reflex-components-plotly 0.9.2 -> 0.9.3 - reflex-hosting-cli 0.1.67 -> 0.1.68 Also strip the issue link embedded in the #6617/#6621 fragment text so towncrier renders each link exactly once. Dependency pin updates (reflex-components-core's reflex-base >= 0.9.5.post2.dev0 dev pin, and the root reflex-base floor) are intentionally left out: they pin to as-yet-unpublished versions and must land after reflex-base 0.9.6 is published, matching the established two-wave release flow. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017ELfV78gRoQiknTTEXctPs
Merging this PR will not alter performance
Comparing 
Footnotes
|
Greptile SummaryThis is a changelog-only materialization PR that converts pending news fragments into
Confidence Score: 4/5Safe to merge after correcting the hosting-cli version header — all other changelogs are accurate and no source code is touched. The reflex-hosting-cli CHANGELOG labels the new release as v0.1.67 with a date of 2026-06-17, which duplicates the already-published tag. Publishing with this header would produce a confusingly identical entry to the existing release; the correct label is v0.1.68 (2026-06-25). All other five changelogs correctly match their intended next-version bumps and the shared build date. packages/reflex-hosting-cli/CHANGELOG.md — version header needs to change from v0.1.67 to v0.1.68 and the date from 2026-06-17 to 2026-06-25. Important Files Changed
Reviews (2): Last reviewed commit: "Update changelog for version reflex-host..." | Re-trigger Greptile |
v0.1.67 was released without actually publishing the changelog, so publishing it now.
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
4 participants
Builds the pending news fragments into
CHANGELOG.mdfor the framework and the modified subpackages, ahead of the next release. Each version is the next dot bump from the package's latest release tag.reflex(framework)reflex-basereflex-components-corereflex-components-momentreflex-components-plotlyreflex-hosting-cli already release 0.1.67 last week without updating the changelogs, so updating those now.
27 fragments consumed into 6 changelogs (3 updated, 3 newly created). Also strips the issue link embedded in the
#6617/#6621fragment text so towncrier renders each link exactly once.Scope: changelogs only
This PR is intentionally
.md-only (nopyproject.tomlchanges).min_depsignores**/*.md, so it stays green, and dependency-pin bumps are deferred to a post-publish follow-up — matching the established two-wave flow (cf. #6645 → #6646).Release ordering notes
reflex-components-coreis the only package with a dev pin (reflex-base >= 0.9.5.post2.dev0), soreflex-base0.9.6 must publish beforecore0.9.6. The publish gate rejects the dev pin until it is re-pinned to a publishedreflex-base.reflex-base+reflex(together), plus the simple componentsreflex-components-moment,reflex-components-plotly.reflex-base0.9.6 is on PyPI):reflex-components-core— re-pinreflex-base >= 0.9.6(and bump the rootreflex-basefloor for internal consistency), then release.reflex-baseandreflex-components-coreare the delicate ones — cut0.9.6a1pre-releases and validate before promoting to final.🤖 Generated with Claude Code
https://claude.ai/code/session_017ELfV78gRoQiknTTEXctPs
Generated by Claude Code