Repository navigation
RatioLab 0.1.12
RatioLab 0.1.12 adds a complete desktop update flow: manual checks, a persistent automatic-check preference, cancellable downloads and release-checksum verification. It is built from commit 3277a09984ac95c273fca2d9da9a36d564ea117d. See the changelog.
Changes since 0.1.11
- Check for updates manually and see progress, up-to-date results or errors. Manual checks work with automatic checking disabled and can show skipped releases, while respecting update policy and GitHub rate limits.
- Download compatible packages inside the application, cancel downloads, and verify them against
SHA256SUMSfrom the same release before preparing an installation handoff. - Update now prepares Linux per-user bundle or Windows Setup updates and offers the normal Save / Discard / Cancel protection before closing. macOS opens the verified DMG; Debian packages use the system installer. Source, Python and unmarked portable installations retain manual updates.
Install 0.1.12 using the appropriate download below to get the new update flow.
Downloads
- Windows 11 x86-64:
RatioLab-0.1.12-windows-x86_64-setup.exe. - macOS 15+: choose
RatioLab-0.1.12-macos-arm64.dmgfor Apple Silicon orRatioLab-0.1.12-macos-x86_64.dmgfor Intel. - Ubuntu 24.04+ / compatible x86-64 Linux: use
ratiolab_0.1.12_amd64.deb,RatioLab-0.1.12-linux-x86_64.runorRatioLab-0.1.12-linux-x86_64.tar.gz. Linux requires glibc 2.39+.
Python, GTK and required runtime libraries are included; graphics drivers come from the operating system. A compatible desktop OpenGL driver is required. Windows Setup is unsigned. macOS applications use ad-hoc signing without Apple notarization; systems may warn or block launch.
Verification and limits
Native CI and Python distribution CI completed successfully for the exact release commit. All eight native artifact ZIPs matched their GitHub SHA-256 digests and sizes before bounded, CRC-verified extraction. All six binaries matched their included CI checksums. SHA256SUMS contains independently recalculated binary hashes; build-evidence.json records the actual jobs, package checks and installed GUI/MCP results without private runner paths.
Linux CI installed and uninstalled the .run package, passed the installed GUI and MCP checks, and passed a runtime self-test from an extracted Debian package. It did not perform a system Debian package installation. Windows CI installed and uninstalled Setup and passed installed runtime and MCP checks, but the hosted runner could not create an OpenGL context: Windows GUI rendering remains unverified by this CI. Both macOS architectures mounted the DMG, copied the application, and passed runtime, GUI, MCP and strict deep code-signature verification checks.
Linux using Mesa software rendering and both macOS architectures using Apple Software Renderer passed installed GUI checks for all ten model families, six feature groups and workspace export. Installed MCP checks passed both supported protocols on all four platforms. These self-tests do not exercise an actual update from an older native installation, and do not establish performance or compatibility on every computer. Windows/macOS updater installation acceptance remains unperformed.
The local repository suite completed 797 tests with four GUI failures, no errors and no skips; all 92 updater tests passed. Diameter-refresh and theme failures were reproduced on unchanged 0.1.11. The backlash and divider classes passed unchanged on both baseline and candidate when rerun as complete classes. GUI timing/focus instability remains a recorded limitation; the full local suite was not clean.
Gear geometry, measurements and motion remain nominal/theoretical. General interference checks and measurements use sampled surfaces. Read unresolved results and calculation-report limits before using exported models; these checks do not certify manufacturing, strength, service life or standards conformity.