Skip to content

Installer: install the latest release from the web, not main (#371) - #379

Merged
rbardaji merged 1 commit into
mainfrom
feature/371-default-release-tag
Oct 23, 2026
Merged

rbardaji merged 1 commit into
mainfrom
feature/371-default-release-tag

Conversation

@rbardaji

Copy link
Copy Markdown
Collaborator

Closes #371.

What

  • Default ref. Piped installs (bash <(curl …/install.sh)) now resolve the newest release tag and clone it instead of main.
    • Tags are vX.Y.Z, sorted with sort -V; pre-releases are skipped.
    • The run prints Installer version: vX.Y.Z (latest release).
    • A re-run moves an existing checkout to the newest release.
  • --ref <tag|branch> is a new documented flag.
    • EP_REPO_REF still works; when both are given, the flag wins.
    • setup.sh (NDP-EP) pins its version with EP_REPO_REF, so it is unaffected.
  • Fallbacks.
    • A repository with no release falls back to main, with a warning.
    • If the releases cannot be listed, the run stops with a message naming --ref.
  • Record. INSTALLER_VERSION (git describe) is written to .env.install-state. The version is also in the install log header (0.34.59).

Tests

  • New install/tests/test_default_release_ref.py: 13 tests against a local repository with releases, a pre-release and newer commits on main. 11 of them fail on main.
  • Real test: a piped install from GitHub resolved v0.34.60, cloned it, built it, and the Endpoint answered healthy.

Release 0.34.61.

@rbardaji
rbardaji merged commit b5e0bbe into main Oct 23, 2026
2 checks passed
@rbardaji
rbardaji deleted the feature/371-default-release-tag branch October 23, 2026 14:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Installer: piped installs track main by default, so a published install can drift

1 participant