Release Healer Man 0.1.3

DEPLOYMENT.md

@@ -176,17 +176,28 @@ schema-compatible with Healer Man and must not be copied over the new one.
 
 ## Update workflow
 
-For a code update that includes a new APK, choose the next version first. The
-example below upgrades `0.1.0` to `0.1.1`; replace `2` if it is not the next
-unused Android `versionCode`. Then run these commands in **Windows PowerShell**
+For a code update that includes a new APK, the visual workflow in
+`RELEASE_RUNBOOK.md` is recommended. For a manual release, choose the next
+version first. The example below upgrades `0.1.2` to `0.1.3`; replace `1003` if
+it is not greater than every prior Android `versionCode`. Then run these
+commands in **Windows PowerShell**
 on the development PC. Stop if any test or build fails:
 
 ```powershell
 Set-Location F:\Projects\HealerMan
 
-$VersionName = '0.1.1'
-$VersionCode = 2
+$VersionName = '0.1.3'
+$VersionCode = 1003
 npm version $VersionName --no-git-tag-version
+$ReleaseVersion = [ordered]@{
+  versionName = $VersionName
+  versionCode = $VersionCode
+} | ConvertTo-Json
+[IO.File]::WriteAllText(
+  (Join-Path $PWD 'release-version.json'),
+  "$ReleaseVersion`n",
+  [Text.UTF8Encoding]::new($false)
+)
 
 npm run content:test
 npm run server:test
@@ -298,17 +309,17 @@ Gitea release/tag, and upload both attachments with:
 
 ```powershell
 powershell.exe -NoProfile -ExecutionPolicy Bypass -File scripts/publish-gitea-release.ps1 `
-  -VersionName 0.1.1 `
-  -VersionCode 2 `
+  -VersionName 0.1.3 `
+  -VersionCode 1003 `
   -ReleaseNotes 'Healer Man client update.'
 ```
 
 The result contains:
 
 ```text
-Tag: v0.1.1
-APK: healer-man-0.1.1-release.apk
-Checksum: healer-man-0.1.1-release.apk.sha256
+Tag: v0.1.3
+APK: healer-man-0.1.3-release.apk
+Checksum: healer-man-0.1.3-release.apk.sha256
 ```
 
 Obtainium should monitor: