Skip to content

[Release] v0.5.5 Linux x86_64 tarball: binary --version reports 0.5.1 #884

@unclecatvn

Description

@unclecatvn

Description

The GitHub release v0.5.5 (RightNow-AI/openfang) includes the asset openfang-x86_64-unknown-linux-gnu.tar.gz, but the openfang binary extracted from that archive prints openfang 0.5.1 when running openfang --version. The Git tag (v0.5.5) and the CLI-reported version (0.5.1) therefore do not match.

This breaks trust in openfang --version as a way to confirm which release is installed, and it causes the official updater (curl -fsSL https://openfang.sh/update | sh) to show “Already up to date: openfang 0.5.1” when the before/after version strings are identical—even after downloading the tarball that GitHub associates with v0.5.5.

Scope of this report: Linux x86_64 artifact from the v0.5.5 release page; other triples were not verified here.

Expected Behavior

  • For release tag v0.5.5, the openfang binary shipped in openfang-x86_64-unknown-linux-gnu.tar.gz should report openfang 0.5.5 (or a version string that clearly and consistently maps to v0.5.5 per project policy).
  • The semver in openfang --version should match the release tag after removing the v prefix (v0.5.50.5.5).
  • After a successful update from an older install to the v0.5.5 artifact, openfang --version should reflect 0.5.5, not 0.5.1, so users and scripts can rely on the CLI for version checks.

Steps to Reproduce

curl -fsSL https://openfang.sh/update | sh
./openfang --version

Observe: output shows openfang 0.5.1 instead of openfang 0.5.5.

OpenFang Version

0.5.5

Operating System

Linux (x86_64)

Logs / Screenshots

Image

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions