release
Orchestrate a new Freenet release. Determines next version, shows changelog, confirms with user, and triggers the release pipeline via GitHub Actions. Use when the user says "do a release", "new release", "release", or "/release".
freenet · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add freenet/freenet-agent-skills --skill releaseAbout this skill
name: release description: Orchestrate a new Freenet release. Determines next version, shows changelog, confirms with user, and triggers the release pipeline via GitHub Actions. Use when the user says "do a release", "new release", "release", or "/release". user_invocable: true license: LGPL-3.0
Freenet Release Skill
Overview
This skill orchestrates a complete Freenet release. The release pipeline runs entirely in GitHub Actions — your job is to determine the version, confirm with the user, trigger the workflow, watch it complete, then verify the cascade (gateway updates, announcements, network health).
The workflow handles all of: version bump → release PR → CI gate → crates.io publish → GitHub release → cross-compile binaries. The release.published event then auto-triggers gateway-update.yml (HMAC-POSTs each gateway's release-agent) and release-announce.yml (Matrix + River posts via release-agent).
Arguments
- If an argument is provided (e.g.,
/release 0.2.65), use it as the target version. - If no argument is provided, auto-detect: increment the patch of the version currently in
crates/core/Cargo.toml. If unreleased PRs have already bumped it past the last tag, use the current Cargo.toml version as-is rather than incrementing again — that's the version those PRs were intended for.
Step 1: Determine Version and Show Changelog
cd ~/code/freenet/freenet-core/main
git pull origin main # MUST pull first
LAST_TAG=$(git describe --tags --abbrev=0)
CARGO_VERSION=$(grep "^version" crates/core/Cargo.toml | cut -d'"' -f2)
echo "Last release tag: $LAST_TAG"
echo "Cargo.toml says: $CARGO_VERSION"
echo
echo "Commits since $LAST_TAG:"
git log --oneline "$LAST_TAG"..HEAD
Pick the target version (see Arguments above). Present the user with current version, target version, and a categorized changelog. Confirm before triggering.
Step 2: Trigger the Release Workflow
gh workflow run release.yml --repo freenet/freenet-core --field version=X.Y.Z
Available inputs (see gh workflow view release.yml --yaml):
version— required for explicit version; leave blank to auto-patch-bump from the latest crates.io release.skip_tests— skip pre-release local tests (CI still runs on the PR).dry_run— show what would happen without publishing.
Confirm the run started:
sleep 5
gh run list --workflow release.yml --repo freenet/freenet-core --limit 1 \
--json databaseId,status,event,createdAt
Step 3: Watch the Release Run
The workflow takes ~20–30 minutes (version-bump → release PR → merge_group full-suite CI → crates.io → GitHub release → cross-compile binaries). Use gh run watch in a backgrounded Bash call so the harness notifies on completion — never manually poll.
RUN_ID=$(gh run list --workflow release.yml --repo freenet/freenet-core --limit 1 --json databaseId -q '.[0].databaseId')
gh run watch "$RUN_ID" --repo freenet/freenet-core --interval 30 --exit-status
If the run fails, inspect the failing job:
gh run view "$RUN_ID" --repo freenet/freenet-core --log-failed | tail -100
Common failure modes are below (Step 5).
Step 4: Verify the Release Artifacts
After the release workflow succeeds, the release.published event fires and the downstream cascade runs automatically. Verify each piece landed:
VER=X.Y.Z
# crates.io
cargo search freenet --limit 1 # should show new version
cargo search fdev --limit 1 # should show bumped fdev
# GitHub release + binaries
gh release view "v$VER" --repo freenet/freenet-core
gh release view "v$VER" --repo freenet/freenet-core --json assets --jq '.assets[].name'
Required platform binaries (all must be attached before the cascade is healthy):
freenet-x86_64-unknown-linux-musl.tar.gzfreenet-aarch64-unknown-linux-musl.tar.gzfreenet-x86_64-apple-darwin.tar.gzfreenet-aarch64-apple-darwin.tar.gzfreenet-x86_64-pc-windows-msvc.zipfreenet.exe- corresponding
fdev-*archives SHA256SUMS.txt
Check the downstream cascade fired (these auto-trigger on release.published):
gh run list --workflow gateway-update.yml --repo freenet/freenet-core --limit 1
gh run list --workflow release-announce.yml --repo freenet/freenet-core --limit 1
Both should show recent runs initiated after the release. If either is missing, the RELEASE_PAT secret may have expired (see freenet-core's AGENTS.md "Release Workflow & RELEASE_PAT" section).
Step 5: River Compatibility Smoke Test
Before relying on the auto-announcements, verify River clients can still talk to the gateway. Protocol changes (new wire variants, streaming defaults, serialization changes) can silently break River even when all freenet-core tests pass.
The current Freenet Official room owner VK lives in the river-official-room skill — do NOT hardcode it here; it rotates when the room is recreated.
ROOM_VK=$(...) # from river-official-room skill
cd ~/code/freenet/river/main
cargo run -p riverctl -- member list "$ROOM_VK"
If this fails with a bincode deserialization error: STOP. A protocol or serialization change broke River compatibility. Roll back the release (see "Rollback" below), file an issue, and rebuild River against the new stdlib before retrying.
(v0.2.11 incident: enabling WebSocket streaming by default broke riverctl pinned to stdlib 0.1.40 — StreamHeader/StreamChunk variants weren't deserializable. This smoke test catches that class of regression.)
Step 6: Post-Release Network Verification
Wait 10–15 min for gateways to auto-update via the release-agent HMAC POST, then verify:
- Gateway versions — each gateway is running the new version. Use the
freenet-gateway-opsskill for SSH'd version + log checks on nova / vega / technic. - Gateway logs clean — no new error patterns, no ra