You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Pin the documented install path to a PyPI release instead of the main branch #7
`install.sh` defaults `SOURCE` to `git+https://github.com/Zipstack/unstract-cli@main\`, and the README's `curl | sh`, `uv tool install` and `uvx` lines all point at the same unpinned branch. Every install gets whatever `main` holds at that moment: no version pin, no reproducibility, and any bad commit on `main` is live for new installers immediately.
Once the first release is published to PyPI:
default `SOURCE` in `install.sh` to the PyPI package name
change the README install lines to a version-pinned install
keep the `UNSTRACT_CLI_SOURCE` override for branch or local-checkout installs
Resolved by #10: install.sh defaults to the PyPI package (2471f1d), README install lines point at PyPI instead of the main branch, and UNSTRACT_CLI_SOURCE still overrides for branch/local installs. Installs now resolve to released artifacts rather than whatever main holds. Remaining nicety — dropping the prerelease flag from the documented lines — lands with the first stable release.
Activity
chandrasekharan-zipstack commentedon Sep 17, 2026
Resolved by #10: install.sh defaults to the PyPI package (2471f1d), README install lines point at PyPI instead of the main branch, and UNSTRACT_CLI_SOURCE still overrides for branch/local installs. Installs now resolve to released artifacts rather than whatever main holds. Remaining nicety — dropping the prerelease flag from the documented lines — lands with the first stable release.