Flatpak
This builds the Git revision pinned in the manifest inside the GNOME 51 SDK. Rust and Node dependencies are pinned by the existing lockfiles and downloaded before the sandboxed, offline build. The shared-modules submodule supplies the Ayatana tray libraries.
ArkHost repository
HelixNotes is distributed through ArkHost's signed Flatpak repository at
https://repo.arkhost.com/flatpak/, served by Shiny. Install using
HelixNotes.flatpakref.
The public catalog advertises version 1.3.8.
The application ID is com.helixnotes.HelixNotes; the repository collection ID is
com.arkhost.Flatpak. Keep both stable so installed applications receive future
updates from the same repository.
Signing fingerprint: B66171BA8BBE0F590D067B86D02631809E3F7AE2.
The initial publication was checked using a separate temporary Flatpak store:
the install descriptor, catalog version, signatures and package download passed.
That check did not deploy or launch the application.
prepare-repository.py imports a built bundle, prepares AppStream metadata and
static deltas, and signs the application and repository metadata with an OpenPGP
key. It exports only the public key. The signing key stays in the local keyring.
Keep an offline backup of that permanent signing identity.
After building the bundle, prepare a fresh signed output:
python3 packaging/flatpak/prepare-repository.py \
src-tauri/target/flatpak/HelixNotes_1.3.8_x86_64.flatpak \
--output /path/to/arkhost-flatpak-1.3.8 \
--gpg-key FULL_OPENPGP_FINGERPRINT
The script uses the ostree command when available, or the system's OSTree
GObject bindings to initialize repositories. This Fedora workstation already
has those bindings. For subsequent releases, add
--previous-directory /path/to/previous-output to preserve the publication
history. Always choose a new output directory.
If the signing identity is not ready, --unsigned can replace --gpg-key for a
local preview. The output will be visibly marked as unsigned and will contain no
install descriptors.
The signed output contains:
repo/ Application repository and update metadata
arkhost.flatpakrepo Adds the ArkHost remote
HelixNotes.flatpakref Adds the remote and installs HelixNotes
Unsigned staging omits install links and is not a publishable repository. Keep the previous signed output when preparing an update so repository history and delta updates are retained.
Publish the prepared public files under
/srv/www/repo.arkhost.com/flatpak/ on Shiny using the existing repository
deployment workflow. The publisher prepares local files; it does not connect to
Shiny or change its web configuration. Serve the tree over HTTPS with HTTP
keep-alive enabled. Keep repository summaries and install descriptors fresh in
any HTTP cache; content-addressed objects can be cached longer.
Keep updates scoped to this flatpak/ subtree. APT/RPM deployments must preserve
it, and Flatpak deployments must preserve the other repository subtrees.
HelixNotes and its updates come from ArkHost. The shared GNOME runtime continues
to come from its existing upstream repository. Users install through
HelixNotes.flatpakref and receive updates through Discover, GNOME Software or
flatpak update.
Build
Run from the repository root:
git submodule update --init packaging/flatpak/shared-modules
flatpak install --user flathub org.flatpak.Builder org.gnome.Platform//51 org.gnome.Sdk//51 org.freedesktop.Sdk.Extension.node24//26.08 org.freedesktop.Sdk.Extension.rust-stable//26.08
flatpak run org.flatpak.Builder --user --force-clean --collection-id=com.arkhost.Flatpak --state-dir=src-tauri/target/flatpak/state --repo=src-tauri/target/flatpak/arkhost-origin src-tauri/target/flatpak/build packaging/flatpak/com.helixnotes.HelixNotes.yml
flatpak build-bundle src-tauri/target/flatpak/arkhost-origin src-tauri/target/flatpak/HelixNotes_1.3.8_x86_64.flatpak com.helixnotes.HelixNotes stable --runtime-repo=https://dl.flathub.org/repo/flathub.flatpakrepo
The commands require a user-local Flathub remote. If only a system remote exists, add the user remote first:
flatpak remote-add --user --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo
Install and run
flatpak install --user https://repo.arkhost.com/flatpak/HelixNotes.flatpakref
flatpak run com.helixnotes.HelixNotes
Choose vault folders using the folder picker. Flatpak grants access to the chosen folders through its document portal; the package does not request access to the whole home directory. Its settings are separate from native installations. The document portal does not forward external file-change notifications, so this build checks visible notes and notebooks about every two seconds in small vaults. The interval grows with scan cost in larger vaults to limit background CPU use. It compares file size and precise modification/change timestamps, including changes made while preserving a note's modification time. Attachments and hidden app data are excluded from these scans; note contents are read only when a change is detected.
The build sets HELIXNOTES_INSTALL_TYPE=flatpak, which suppresses the in-app
updater. Discover, GNOME Software or flatpak update handle updates for installs
from the ArkHost repository. The bundle references Flathub for its runtime, which
is installed separately.
Refresh dependencies
Regenerate both source lists whenever their lockfiles change. The initial lists
were generated with flatpak-builder-tools commit
9d86d336a39b9af38b86f114b6ce5820fe260f91:
uv run --project /path/to/flatpak-builder-tools/node python -m flatpak_node_generator --no-requests-cache --pnpm-store-version v11 --node-sdk-extension org.freedesktop.Sdk.Extension.node24//26.08 -o packaging/flatpak/node-sources.json pnpm pnpm-lock.yaml
uv run /path/to/flatpak-builder-tools/cargo/flatpak-cargo-generator.py -o packaging/flatpak/cargo-sources.json src-tauri/Cargo.lock
Keep the pinned pnpm archive/version in the manifest in step with
package.json's packageManager. pnpm 11 uses the v11 store; the generator's
default v10 store does not work with it.
The offline install uses --trust-lockfile for this reviewed, pinned lockfile.
Flatpak verifies the downloaded sources against the generated checksums. This
keeps pnpm from querying registry metadata and attestations during the offline
build; it does not grant network access to the build sandbox.
The store developer is Yuri Karamian. The Flatpak build overrides Tauri's identifier only for this package; native packages retain their existing ID.
Version 1.3.8 is published in the ArkHost Flatpak repository with stable package
metadata dated 2026-11-16. GitLab release tags and other platform channels are
managed separately. The manifest pins the tested application revision 962f330
and supplies the release MetaInfo as a separate, version-controlled source file.
This keeps the application code identical to the tested packages while including
the matching store metadata and refreshed offline dependencies.
The published package targets x86_64. The earlier test bundle in Nextcloud uses
the com.helixnotes.app ID and has not been overwritten. Install through the
public link once to use the permanent ID and receive repository updates. The new
ID has a separate Flatpak profile; select the same notes folder through the system
picker.
Optional Flathub submission
The separate Flathub submission draft has not been checked with Flathub's build wrapper or linter. See the submission guide and current requirements.
The Flathub repository needs these files at its root:
com.helixnotes.HelixNotes.ymlcargo-sources.jsonnode-sources.jsonflathub.json- The MetaInfo file referenced by the manifest
- The
shared-modulesGit submodule, pinned to6be1f986ac28a2b7d745e5ff45a3f8a2d3345083
Desktop and icon files are installed from the pinned application source. The MetaInfo file is supplied separately by the manifest. Use the release's prepared submission patch as a complete set of inputs; it includes its referenced metadata file. The source pin identifies the tested 1.3.8 application code, not the later packaging-only synchronization commit.
Use a branch based on flathub/flathub's new-pr branch. Preserve the upstream
submission template. Author the submission description and any review replies
yourself, following Flathub's current requirements. This preparation does not
create a GitHub pull request or publish an application.