Updates

Agentina is updated by promoting signed builds to a channel. Your license is pinned to a channel; the agent learns about a newer release on the next heartbeat and surfaces a hint. Installation is always operator-initiated — the agent does not auto-replace its own binary.

Channels

Channel	Audience	Cadence
`stable`	Most customers	Every 1–2 weeks
`beta`	Early adopters	~2 days behind `main`
`enterprise-lts`	Procurement-gated rollouts	Quarterly with backports
`dev`	Internal only	Per commit

Which channel you're on is baked into your license. Check it with agentina status.

How updates flow

Engineering tags a release and publishes a signed tarball to the channel.
An operator promotes the build via the admin panel. Release notes are authored alongside the promotion.
Every agent on that channel sees an update_available hint on its next heartbeat (default cadence: 60s).
agentina status shows the available version and the release notes title.
The operator (or you, depending on how you run the fleet) runs agentina upgrade.

Upgrading an agent

The fastest path uses the manifest URL the install was wired with:

bash

sudo agentina upgrade --manifest <manifest-url>

What happens:

Fetch the new manifest. Verify the cosign signature against the trusted public key.
Fetch the new tarball. Verify its signature.
Extract to /opt/agentina/<new-version>/.
Swap the current symlink to the new version (atomic).
Run a smoke check against the new binary. On failure: swap the symlink back, exit non-zero.
Restart the service. If the new version fails to start: swap the symlink back, restart the old version, exit non-zero.

Two-level rollback: a binary that runs but misbehaves is caught by the smoke check; a binary that won't even start is caught by the service-restart step. In both cases you end up back on the previous version with no manual intervention.

Manual rollback

If you need to revert after a successful upgrade (e.g. a bug surfaces in production after a clean smoke check):

bash

sudo agentina upgrade --manifest <previous-manifest-url>

Old versions live under /opt/agentina/<version>/ until you garbage-collect them. The installer keeps the most recent 3 installed by default; older ones are deleted on the next upgrade.

Signature verification

Every manifest and every tarball is signed with cosign. The agent installs with the verification public key baked in at install time (/opt/agentina/keys/agentina-internal-release.pub). Builds signed with the dev key are refused unless you pass --allow-dev-builds — useful in test environments, not for production.