fix: pin moment-timezone to exact version 0.6.2#6649
Conversation
Greptile SummaryThis PR pins
Confidence Score: 5/5Minimal risk — the change tightens a dependency specifier from a caret range to an exact version with no logic changes. The Python change uses a well-established Reflex pattern that the framework already handles correctly for both JS import generation and package.json resolution. The lock and manifest files are regenerated consistently. No behavioral change is introduced beyond stricter version pinning. No files require special attention. Important Files Changed
Reviews (1): Last reviewed commit: "add changelog fragment" | Re-trigger Greptile |
Merging this PR will not alter performance
Comparing Footnotes
|
Summary
Pin the
moment-timezonedependency ofrx.momentto the exact version0.6.2instead of an unpinned specifier, which previously resolved to a caret range (^0.6.2) in generatedpackage.jsonfiles. This keeps frontend installs reproducible and consistent with the other pinned JS dependencies.Moment.add_importsnow declaresmoment-timezone@0.6.2whentzis setdocs/app/reflex.lockaccordingly