Skip to content

update.md

Latest commit

 

History

History
82 lines (56 loc) · 3.34 KB

update.md

File metadata and controls

82 lines (56 loc) · 3.34 KB
Raw

Updating FoxxyCode Agent

Use foxxycode update to download official release binaries from GitHub Releases and replace the foxxycode executable you are running.

What gets installed

CI publishes one archive per platform on each SemVer tag X.Y.Z:

Archive Platform
foxxycode_X.Y.Z_linux_amd64.tar.gz Linux x86_64
foxxycode_X.Y.Z_linux_arm64.tar.gz Linux arm64
foxxycode_X.Y.Z_windows_amd64.zip Windows x86_64 (foxxycode.exe)
foxxycode_X.Y.Z_darwin_amd64.tar.gz macOS Intel
foxxycode_X.Y.Z_darwin_arm64.tar.gz macOS Apple Silicon

Each binary is built with http, ui, scheduler, and memory (same as make build TAGS="http ui scheduler memory" and the default Docker image). See Build from source for the release pipeline.

Which file is replaced

foxxycode update resolves os.Executable() (symlinks followed) and overwrites that path. Examples:

  • After make install as a regular user, that is usually ~/.local/bin/foxxycode.
  • When you run ./build/foxxycode update, it updates build/foxxycode in the repo.

This differs from make install, which always copies to ~/.local/bin or /usr/local/bin. To update the binary on PATH, invoke the same foxxycode that which foxxycode prints.

Commands

Check for a newer release (exit 0 if up to date, 1 if a newer X.Y.Z exists):

foxxycode -v
foxxycode update --check

Install the latest release (prompt [y/N] unless -y):

foxxycode update
foxxycode update -y

Install a specific tag:

foxxycode update --version 0.9.3
foxxycode update --version 0.9.3 -y

Override the GitHub repository (default hijera/foxxycode-agent):

foxxycode update --repo hijera/foxxycode-agent

All flags:

foxxycode update --help

Version comparison

foxxycode -v may show a git describe string (for example 0.9.2-5-gb6b7d31-dirty). foxxycode update compares the leading X.Y.Z prefix to the release tag. A local dev build is treated as older than any published SemVer release.

Other upgrade paths

Method When to use
foxxycode update You already have a release binary on disk and want the next (or a specific) GitHub release.
make install You built from a clone and want build/foxxycode on PATH.
make build TAGS="..." You need custom tags or local changes not in releases.
Docker docker compose pull / image tag X.Y.Z on GHCR.
go install ...@latest Quick install without release assets; default module tags only (no http / UI unless you build from source).

Limitations

  • Only platforms listed in the release table are supported; others get a clear error.
  • On Windows the running process may lock the executable; close other foxxycode instances if replace fails.
  • foxxycode update needs outbound HTTPS to api.github.com and the asset CDN (GitHub release downloads).
  • Config under $FOXXYCODE_HOME is not modified; only the binary is replaced.