Skip to content

acfs in the tools image always reports version dev #17

Open

Description

@neurekadev

Problem

The tools image's acfs always reports "version":"dev":

{"version":"dev","revision":"unknown","buildTime":"unknown","protocol":2}

The acfs-builder stage in Dockerfile (line 35) sets the version with the old module path:

-ldflags "-s -w -X go.getarcane.app/acfs/internal/version.Version=v${ACFS_VERSION}"

The module is now kit.getarcane.app/acfs, and the linker silently ignores -X for a package that isn't in the binary. With acfs/v0.7.0 checked out, building ./cmd with each path gives:

-X package acfs version
go.getarcane.app/acfs/internal/version "version":"dev"
kit.getarcane.app/acfs/internal/version "version":"v0.7.0"

Why it matters

Arcane has to tell which helper features a local tools:latest image supports. Installs keep whatever image they have, and Arcane never re-pulls it. The next one is acfs list --limit (getarcaneapp/kit#26, getarcaneapp/kit#27), which Arcane will use only on helpers that support it (getarcaneapp/arcane#4694). While every image reports dev, version-based detection can't work.

Proposal

  • Change the -X path in Dockerfile to kit.getarcane.app/acfs/internal/version.Version, matching acfs/.goreleaser.yaml in getarcaneapp/kit.
  • Optionally also set Revision and BuildTime, as the GoReleaser build does.
  • Once the acfs release with list --limit is out, bump ACFS_VERSION to it.

Drafted with Claude Code (Claude Opus 5.5).

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions