Repository navigation
Releasing
nodemode-ai edited this page Nov 4, 2026
·
2 revisions
- Land the work on main with CI green (interface build, engine selfcheck and MCP probe, skill references in step, text lint, shell syntax,
cargo checkof the desktop shell). - Bump the version in every site in one commit (see
.docs/BRANCHING.md). - Push a branch named
compile_vX.Y.Zfrom that commit, for examplegit push origin HEAD:compile_v0.51.1. CI runs on it. The name must match the version insrc-tauri/tauri.conf.json, or formcompiler refuses it and says why. - formcompiler (
nodemode-dev/formcompiler) finds the branch on its next watch run (every 8 hours), or at once when its watch is run by hand. Once CI has passed on that commit, it builds macOS arm64, Linux x64 and Windows x64 bundles and opens a draft releaseformvfx-vX.Y.Zon its release page. - Signing: the Apple Developer ID, Windows code signing and Tauri updater key secrets are set in formcompiler's repository, never in this one. Updater signatures also publish
latest.jsonin theformvfx-updatesfeed. Setplugins.updater.pubkeyinsrc-tauri/tauri.conf.jsonto the matching public key to turn update checks on. - Check the draft release's assets on formcompiler's release page, then publish it there. Compile branches are kept as the record of what was built.