2.4 KiB
Cliphoard release procedure
Run releases from the repository root. The current Git remote stores source and tags, but no binary-upload destination is configured.
Prepare
git switch main
git pull --ff-only
git status --short
Choose the next semantic version, for example 1.1.0, and tag it v1.1.0.
Update the version in Cargo.toml, the root cliphoard package in
Cargo.lock, packaging/debian/control, packaging/build-deb.sh, and the
versioned .deb names in README.md.
Verify and build
cargo fmt --all -- --check
cargo test --locked --all-features
cargo clippy --locked --all-features -- -D warnings
cargo build --release --locked --features gui
CLIPHOARD_VERSION=1.1.0 packaging/build-deb.sh
dpkg-deb --info target/cliphoard_1.1.0_amd64.deb
dpkg-deb --contents target/cliphoard_1.1.0_amd64.deb
sha256sum target/cliphoard_1.1.0_amd64.deb target/release/cliphoard
The Docker workflow from the README provides an isolated test, release-build, and package-build path:
docker build -t cliphoard-builder .
docker run --rm -v "$PWD/target:/out" cliphoard-builder
Commit and tag
Only commit after the gates pass:
git diff --check
git status --short
git add Cargo.toml Cargo.lock README.md packaging/debian/control packaging/build-deb.sh src .agents RELEASING.md
git commit -m "Release Cliphoard 1.1.0"
git tag -a v1.1.0 -m "Release Cliphoard 1.1.0"
Replace 1.1.0 and v1.1.0 with the actual version.
Sync
git show --stat --oneline HEAD
git show --no-patch --decorate HEAD
git push origin main
git push origin v1.1.0
If another commit landed remotely after the initial pull, stop and resolve it before pushing. Never force-push release history.
Publish the Gitea release and binary
Pushing Git does not upload target/*.deb: target/ is ignored and the
binary is not committed. Create a Gitea release for the pushed tag, include a
summary of commits and changes, explicitly call out breaking changes, and
attach the .deb, release binary, and checksum file. The release must include
the plaintext-database deletion note and commands from README.md.
Final smoke check
On a clean machine or disposable environment, install the exact .deb, start
Cliphoard, create/unlock the encrypted database, and confirm the tray, popup,
autostart, and passphrase flows. Keep the release commit, tag, artifact name,
checksum, and test results together.