make reflex and reflex base tied#6379
Conversation
Greptile SummaryThis PR removes Confidence Score: 5/5Safe to merge; the only finding is a minor sed-delimiter robustness concern that would cause a workflow failure (not silent data corruption) under highly unlikely tag names. All changes are in CI/release automation. The logic is clean: reflex-base releases automatically carry reflex at the same version, and the publish step pins the dependency before building. The one P2 comment is a theoretical robustness issue with PEP 440-compliant version strings in practice. No files require special attention. Important Files Changed
Sequence DiagramsequenceDiagram
actor Dev
participant Dispatch as dispatch_release.yml
participant Detect as detect.sh
participant Plan as plan.py
participant Publish as publish.yml
participant PyPI
Dev->>Dispatch: trigger (select reflex-base)
Dispatch->>Detect: run with env vars
Detect-->>Dispatch: PACKAGES_JSON (includes reflex-base, excludes reflex)
Dispatch->>Plan: run with PACKAGES_JSON
Plan->>Plan: compute next version for reflex-base
Plan->>Plan: auto-add reflex entry at same version
Plan-->>Dispatch: releases JSON matrix
Dispatch->>Publish: trigger via release tag vX.Y.Z
Publish->>Publish: parse tag → package=reflex, version=X.Y.Z
Publish->>Publish: sed pyproject.toml reflex-base >= * → reflex-base == X.Y.Z
Publish->>Publish: uv build (pinned wheel)
Publish->>PyPI: uv publish dist/*
Reviews (1): Last reviewed commit: "make reflex and reflex base tied" | Re-trigger Greptile |
No description provided.