Keep current
Updates that are visible, verifiable, and easy to publish.
OYAMA Scribe can check your public update feed without blocking the manuscript. Releases are prepared locally, then copied to the `/store` folder on your server.
For people using the app
After startup, the app checks https://www.jamesnox.com/store/latest.json in the background. You can also use File → Check for updates. If a newer version exists, the banner shows the release notes and download size.
- Choose Download update. The current manuscript remains open.
- Wait for the progress bar to finish. The installer is checked against the manifest size and SHA-256 hash.
- Choose Install now or Install when I close.
- Confirm any unsaved changes. Windows Installer may show a UAC confirmation for the per-machine MSI.
For release operators
Run publish-software.bat from the repository. It builds the regular MSI and creates a versioned folder under Published-software with:
Regular-build— the complete self-contained Windows build.Server-upload\store— the MSI, checksum, and generatedlatest.json.READ-ME-FIRST.txt— the upload order and hash.
Upload the MSI and checksum first. Upload latest.json last. The manifest is the public signal that a release is ready.
What the manifest contains
{
"version": "1.55.6586",
"url": "https://www.jamesnox.com/store/OyamaScribe-1.55.6586-x64.msi",
"sha256": "…64 hexadecimal characters…",
"size": 123456789,
"notes": "Faster manuscript loading.",
"signatureRequired": false
}
Until Authenticode signing is configured, the app reports that size and SHA-256 were verified and explains that publisher signing is not yet enabled. When a signing certificate is available, the same release script sets signatureRequired automatically.