v1.2.4

The installer updates the godrop you already have

An install could leave two binaries: the new one in ~/.local/bin and an older
one in /usr/local/bin, earlier in the PATH. The wizard that ran was the new
one and the godrop that answered afterwards was the old one, which is a
confusing way to be out of date.

The new binary now lands on top of the installation in use when that directory
can be written to. When it cannot, it says which copy is shadowing it and how
to remove it:

⚠ another godrop is earlier in your PATH: /usr/local/bin/godrop
  that is the one that answers when you type godrop

      sudo rm /usr/local/bin/godrop   # then the new one takes over

--version

godrop --version answers, because that is what people type. godrop version
still says more.

A fresh install starts the newest image

Setup ran docker compose up -d with whatever :latest already meant on the
machine, so a host that had run GoDrop before started an old release and the
setup that had just verified it said everything was fine. It pulls first now,
as the update path does.

Install

curl -fsSL https://godrop.sh/install.sh | sh

Or with Docker:

docker run -d --name godrop --restart always -p 8747:8747 \
  -e GODROP_TOKENS=$(openssl rand -hex 16) \
  -v godrop-data:/data ghcr.io/fatihbaltaci/godrop:v1.2.4

Debian and RPM packages are attached below; they set up the systemd service
for you. Every archive's checksum is listed in SHA256SUMS.