Completes the 0.1.1242 release, which finished only halfway. During the 2026-08-17 GitHub incident the release job published every npm package and created the git tag, then failed creating the GitHub release: HTTP 503: No server is currently available to service your request. (https://api.github.com/repos/veryfront/veryfront/releases) Everything after that step was skipped, including "Trigger server deploy", "Trigger job-runner deploy" and "Trigger sandbox deploy". So npm carries 0.1.1242 while no GitHub release exists and no deploy ever fired. The job cannot be re-run: it creates the tag before the release, so a rerun stops at its own guard -- "Tag v0.1.1242 already exists on source repo. Bump deno.json before releasing." Bumping is the remedy the guard prescribes, and it is safer than hand-assembling a public release with seven binaries and their checksums. Consumers split by install source, so only one is actually blocked: veryfront-agent installs from npm -> unblocked, already on 0.1.1242 veryfront-server installs the compiled -> blocked, needs this release binary from the GitHub release No code changes beyond the version. Contents are 0.1.1242 plus whatever landed on main since, and still include the fixes this chain exists to ship: #3817, #3818 (issue-inbox#548) and #3820/#3821/#3826 (issue-inbox#549).

Uh oh!

Commits

Commits on Aug 17, 2026

release: v0.1.1243