Verified customer releases
Release 0.2.0 bundles the runner and standalone sample agent. Use Linux, Node.js 24+, Docker, curl and OpenSSL 3+.
1. Pin the release key
Before your first install, confirm this SHA-256 fingerprint of the public PEM file with your Fleetnook administrator through a separate trusted channel. Save the key and fingerprint for future upgrades.
596fbf3978ac924f35d38c88ce77295f7a9993bffd0a7a686c875e4be977e7bfA fingerprint copied only from this website depends on the website’s security. A signature does not establish independent trust in the first key or prove that the software is safe.
2. Verify and unpack
After confirming the fingerprint, run this block from a working directory where the new download directory does not exist. A failed command stops the chain before extraction. An interrupted download can be retried in a new empty directory; preserve any existing runner state.
mkdir -m 700 fleetnook-download-0.2.0 &&
cd fleetnook-download-0.2.0 &&
curl --proto '=https' --tlsv1.2 -fS https://fleetnook.com/downloads/release-key.pem -o release-key.pem &&
printf '%s release-key.pem\n' '596fbf3978ac924f35d38c88ce77295f7a9993bffd0a7a686c875e4be977e7bf' | sha256sum -c - &&
curl --proto '=https' --tlsv1.2 -fS https://fleetnook.com/downloads/releases/0.2.0/fleetnook-0.2.0.tar.gz -o fleetnook-0.2.0.tar.gz &&
curl --proto '=https' --tlsv1.2 -fS https://fleetnook.com/downloads/releases/0.2.0/fleetnook-0.2.0.tar.gz.sig -o fleetnook-0.2.0.tar.gz.sig &&
openssl pkeyutl -verify -pubin -inkey release-key.pem -rawin -in fleetnook-0.2.0.tar.gz -sigfile fleetnook-0.2.0.tar.gz.sig &&
tar -xzf fleetnook-0.2.0.tar.gz &&
cd fleetnook-0.2.0 &&
node fleetnook-runtime.mjs --version3. Enroll on the customer host
From the extracted fleetnook-0.2.0 directory, follow the runner guide to check Docker, enroll, configure local Temporal credentials and start one supervised controller. The enrollment token is pasted at the prompt.
Upgrade an existing runner
Verify the new bundle using the key you previously pinned. Compare the intended release version before extraction; a valid old signature is not proof that a release is current. Stop the runner service, preserve its existing state and agent.env, point the service at the verified runner, then restart it with the same absolute HARBOR_RUNTIME_DIR and service user. Confirm the environment returns to Online. Stopping the controller leaves the agent container running.
Keep the prior runner file for recovery. Do not reset signing state, re-enroll, or run two controllers against one state directory. This release does not change runner state format. Future state migrations require their own reviewed recovery procedure; do not assume arbitrary downgrades are safe.
These signatures cover Fleetnook’s downloadable bundle. They do not sign your agent image, enforce network egress, or automate Temporal workflow upgrades. The signing key is kept off the Cloudflare serving environment; builds verify retained signatures without that private key.