Fix reflex-hosting-cli on v0.7.6.post

[masenf]

Logic was comparing PEP 440 versions, which had an unintended effect for pre and post release version markers. The new "release" based check ignores pre/post/alpha releases and only compares against the version tuple (0, 7, 7).

Verified empirically with published version numbers.

[greptile-apps]

Greptile Summary

The PR changes hosting CLI export compatibility detection to compare the installed Reflex release tuple against 0.7.7, preventing post-release markers such as 0.7.6.post1 from selecting the wrong callback signature.

• Uses the six-argument export callback for release tuples before 0.7.7.
• Uses the seven-argument callback beginning with the 0.7.7 release tuple.
• Adds a bugfix news entry.

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains.

Important Files Changed

Filename	Overview
packages/reflex-hosting-cli/src/reflex_cli/v2/cli.py	Replaces full PEP 440 ordering with release-tuple comparison for both backend and frontend export callback selection.
packages/reflex-hosting-cli/news/6963.bugfix.md	Documents restored compatibility with Reflex 0.7.6.post1.

_{Reviews (2): Last reviewed commit: "Fix version comparison bug for reflex-0...." | Re-trigger Greptile}

[cubic-dev-ai]

No issues found across 1 file

_{Re-trigger cubic}

[codspeed-hq]

Merging this PR will not alter performance

✅ 27 untouched benchmarks
⏩ 8 skipped benchmarks¹

---

_{Comparing masenf/reflex-hosting-cli-0.7.6-compat (cb69e69) with main (f7c848f)}

Footnotes

1. 8 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. ↩