From 70977bad84169d794918026169c8cf13abfd74f6 Mon Sep 17 00:00:00 2001 From: "sorokin.oleg.edu" Date: Mon, 26 Oct 2026 00:58:43 +0300 Subject: [PATCH] chore: synchronize 0.5.1 lockfile and release examples --- .gitea/workflows/release.yml | 4 ++-- docs/desktop-release.md | 2 +- docs/gitea-release.md | 30 +++++++++++++++--------------- package-lock.json | 4 ++-- 4 files changed, 20 insertions(+), 20 deletions(-) diff --git a/.gitea/workflows/release.yml b/.gitea/workflows/release.yml index 73bb273..2f90863 100644 --- a/.gitea/workflows/release.yml +++ b/.gitea/workflows/release.yml @@ -1,12 +1,12 @@ name: Linux desktop release -# Manual until a native Linux runner is registered. The current 0.5.0 +# Manual until a native Linux runner is registered. The current 0.5.1 # packages are built locally using the identical gates documented below. on: workflow_dispatch: inputs: tag: - description: Existing stable version tag to package (for example v0.5.0) + description: Existing stable version tag to package (for example v0.5.1) required: true type: string diff --git a/docs/desktop-release.md b/docs/desktop-release.md index cfeb69a..ccf7c4c 100644 --- a/docs/desktop-release.md +++ b/docs/desktop-release.md @@ -1,6 +1,6 @@ # Desktop builds and releases -For this fork’s Linux and Windows 0.5.0 release on Gitea, see [Gitea releases](gitea-release.md). +For this fork’s Linux and Windows 0.5.1 release on Gitea, see [Gitea releases](gitea-release.md). The three-platform GitHub process below documents the upstream reference. ## Platforms diff --git a/docs/gitea-release.md b/docs/gitea-release.md index 567c822..c6f0974 100644 --- a/docs/gitea-release.md +++ b/docs/gitea-release.md @@ -2,7 +2,7 @@ The release destination is https://server2.sorokin-oleg-edu.xyz/replicated/learnharness. -Version **0.5.0 targets Linux x64 and Windows x64**, with each platform built +Version **0.5.1 targets Linux x64 and Windows x64**, with each platform built and verified on its native operating system. The upstream GitHub workflow and three-platform packaging configuration remain available as reference in `.github/workflows/release.yml` and `electron-builder.yml`. @@ -48,18 +48,18 @@ node scripts/smoke-provider-runtime.mjs --standalone dist/linux-unpacked/resourc xvfb-run -a node scripts/smoke-demo-runtime.mjs --standalone dist/linux-unpacked/resources/server/standalone --runtime dist/linux-unpacked/learnharness --browser ``` -The Linux portion of 0.5.0 has these attachments: +The Linux portion of 0.5.1 has these attachments: -- `LearnHarness-0.5.0-x86_64.AppImage` -- `LearnHarness-0.5.0-amd64.deb` +- `LearnHarness-0.5.1-x86_64.AppImage` +- `LearnHarness-0.5.1-amd64.deb` - `latest-linux.yml` - `SHA256SUMS` ## Preparing Windows packages -Use a clean checkout of the same `v0.5.0` tag on Windows x64 with Node 26 and Git +Use a clean checkout of the same `v0.5.1` tag on Windows x64 with Node 26 and Git for Windows. Keep build tools and logs outside the checkout. The Windows -release checkout is `~/Documents/Gitea/learnharness-release-0.5.0`, linked to the +release checkout is `~/Documents/Gitea/learnharness-release-0.5.1`, linked to the existing repository in `~/Documents/Gitea/learnharness`. In PowerShell, stop after any failed command: @@ -85,13 +85,13 @@ node scripts/smoke-demo-runtime.mjs --standalone dist/win-unpacked/resources/ser Windows contributes three attachments: -- `LearnHarness-0.5.0-x64-setup.exe` -- `LearnHarness-0.5.0-x64-setup.exe.blockmap` +- `LearnHarness-0.5.1-x64-setup.exe` +- `LearnHarness-0.5.1-x64-setup.exe.blockmap` - `latest.yml` The combined release has **seven attachments**, including one `SHA256SUMS` covering all six other files. Verify that `latest.yml` names the Windows -installer exactly, reports version `0.5.0`, and matches the installer's actual +installer exactly, reports version `0.5.1`, and matches the installer's actual size and SHA-512. Its gzip blockmap must cover the installer and match every block checksum. Confirm the packaged `resources/app-update.yml` uses the Gitea generic provider. Windows builds follow upstream's unsigned, per-user installer @@ -102,8 +102,8 @@ configuration. Commit and push the release source, then push its exact annotated tag: ```sh -git tag -a v0.5.0 -m 'LearnHarness 0.5.0' -git push gitea main v0.5.0 +git tag -a v0.5.1 -m 'LearnHarness 0.5.1' +git push gitea main v0.5.1 ``` Supply `GITEA_TOKEN` only to the upload command. A token file may remain outside @@ -117,10 +117,10 @@ The tool requires the tag to exist in Gitea, creates or reuses one draft at that tag, uploads missing assets, and downloads every attachment to verify its actual SHA-256 against the local verified build. Existing mismatched attachments and published releases are refused. It never publishes or changes repository -visibility. Release notes come from `docs/release-0.5.0.md`. +visibility. Release notes come from `docs/release-0.5.1.md`. This uploader and its remote verifier enforce a **Linux-only** inventory. They -will refuse a combined Linux/Windows draft. For the combined 0.5.0 release, add +will refuse a combined Linux/Windows draft. For the combined 0.5.1 release, add the verified Windows attachments to the existing draft and replace `SHA256SUMS` with the combined manifest. Keep the Linux installers and feed unchanged. Check all seven attachment names, sizes, and actual downloaded hashes against the @@ -142,12 +142,12 @@ public `latest` feed and in-app automatic updates expose this version. workflow with an existing release tag as input. It requires a native Linux x64 runner labeled `ubuntu-24.04`, the label used by upstream's Linux release job, plus the native Electron dependencies and `xvfb-run`. There were no runners -registered when 0.5.0 was prepared, so its packages are built locally. A tag push +registered when 0.5.1 was prepared, so its packages are built locally. A tag push does not queue a job that cannot run. The workflow uses the repository's ephemeral `GITEA_TOKEN` with release-write permission only in the final upload step. It checks out the requested tag without persisting credentials and leaves the result as a verified draft. Public pull requests cannot trigger this publishing workflow. This workflow remains -Linux-only; the combined 0.5.0 draft was assembled from local native builds. +Linux-only; the combined 0.5.1 draft was assembled from local native builds. Windows has its own standalone payload and smoke checks, as described above. diff --git a/package-lock.json b/package-lock.json index 6a9821d..288fab4 100644 --- a/package-lock.json +++ b/package-lock.json @@ -1,12 +1,12 @@ { "name": "learnharness", - "version": "0.5.0", + "version": "0.5.1", "lockfileVersion": 3, "requires": true, "packages": { "": { "name": "learnharness", - "version": "0.5.0", + "version": "0.5.1", "license": "AGPL-3.0-only", "dependencies": { "@earendil-works/pi-agent-core": "1.4.0",