Skip to content

NOTO v1.1.5

Choose a tag to compare

@github-actions github-actions released this 25 Aug 17:37
· 124 commits to main since this release

The Android APK, published on the download page at last.

1.1.3 and 1.1.4 shipped the desktop applications without it. Two faults in the
release pipeline were responsible, both fixed here, and neither was ever a
problem with the Android application itself.

Android

The download page now offers an Android build for phones running Android 7.0
or later. The recommended download is the 64-bit APK, which every phone made
since roughly 2016 wants; a 32-bit build is published alongside it for older
hardware.

It is a 16 MB download. The generated Android project would have made it 104
MB for an application whose JavaScript is 2.2 MB: one APK carrying native code
for four processor architectures, stored uncompressed, three of which no
single phone can run. Each APK now carries one architecture, unreachable code
is stripped from the release build, and the native libraries are compressed.

Noto is not on Google Play yet, so Android asks you to permit the install once
— that prompt is expected for anything from outside the store. Open the file
after it downloads and confirm.

Every APK is signed with Noto's own upload key rather than the debug key that
ships with the Android SDK and is byte-identical on every machine. The pipeline
fails outright when that key is absent instead of falling back to the debug
key, which is why 1.1.3 published without an APK rather than with an unsafe one.

Documents on the phone are stored in on-device SQLite, the same local-first
arrangement as every other platform. There is no account, and no sync: notes
written on the phone stay on the phone for now.

Why it took three releases

The first fault was an ordering one. Publishing waited for the desktop and web
builds but not for the mobile one, so it ran the moment the desktop packages
were ready — about eighteen minutes in, while the Android build still had five
minutes to go. The APK was built correctly and then simply arrived too late to
be attached, every time. Publishing now waits for mobile, while still refusing
to let a skipped or failed mobile build withhold the desktop packages.

The second was subtler. Stamping the release version rewrites six manifest
files, and the command that generated the native Android project was scoped to
one workspace package — so the package manager reconciled node_modules to
that narrow scope first, removing 133 packages that the rest of the build
needed. The generation step then hung silently until the job timed out
forty-five minutes later. It runs unscoped now, and every long-running build
step has its own deadline, so a stall costs minutes and says what happened
rather than taking a release down without explanation.

Known limitations

Unchanged: the desktop installers are unsigned, so Windows SmartScreen and
macOS Gatekeeper warn on first launch — verify your download against
SHA256SUMS.txt. macOS auto-update needs a signed build, and Windows ARM64 is
installer-only. iOS is not published. Cloud sync is not enabled on any
platform.


Downloads

Windows

Package File
Installer (x64) Noto-1.1.5-win-x64.exe
Installer (ARM64) Noto-1.1.5-win-arm64.exe

macOS

Package File
Disk image (Apple Silicon) Noto-1.1.5-mac-arm64.dmg
Disk image (Intel) Noto-1.1.5-mac-x64.dmg
Archive (Apple Silicon) Noto-1.1.5-mac-arm64.zip
Archive (Intel) Noto-1.1.5-mac-x64.zip

Linux

Package File
AppImage (x64) Noto-1.1.5-linux-x64.AppImage
Debian package (x64) Noto-1.1.5-linux-x64.deb
RPM package (x64) Noto-1.1.5-linux-x64.rpm

The web application needs no download and is always at the latest version.


Verifying a download

Checksums for every asset are published as SHA256SUMS.txt.

sha256sum --check --ignore-missing SHA256SUMS.txt

Updating

Windows and macOS installations update themselves: Noto checks for a new version on startup, downloads it in the background, and applies it on the next restart.

On Linux, replace the AppImage or install the new .deb/.rpm through your package manager.


System requirements

Platform Requirements
Windows Windows 10 or later, x64 or ARM64, 4 GB RAM, 500 MB storage
macOS A supported modern macOS version, Apple Silicon or Intel, 4 GB RAM, 500 MB storage
Linux x64, 4 GB RAM, 500 MB storage
Web A current version of Chrome, Edge, Firefox or Safari

Full details: System requirements

What's Changed

Other Changes

  • fix(mobile): stop the version stamp from gutting node_modules before … by @utkarsh032 in #1
  • Merge pull request #1 from utkarsh032/main by @utkarsh032 in #2

Full Changelog: v1.1.4...v1.1.5