Skip to content

Packaging: one fix removes half of this list, and the rest is Linux #562

Closed

Description

@PathGao

@alecdotdev @LargeModGames

Markpad ships eleven artifacts across six channels, and the packaging issues open against them are not eleven separate problems. This is what they reduce to, what has already been fixed without needing anyone's decision, and the three things that are genuinely yours to decide.

Long evidence is folded into the <details> blocks. The top level is the part worth reading.


The whole problem in one table

Every channel has to answer three questions:

channel installs can update itself trusted by the OS
Windows *-setup.exe ✅ ✅ ❌ #334 #466
Windows portable .exe ✅ ❌ ❌
Chocolatey ✅ ✅ ❌
macOS .dmg ✅ ✅ ❌ #209 #505 #557
Linux AppImage ⚠️ #182 #498 ✅ —
Linux .deb ✅ ❌ —
Linux .rpm ✅ ❌ —
Linux snap ✅ 💀 dead since June —

The third column is one cause, not four. Every ❌ there is the same missing thing — a code-signing identity. It accounts for five open issues and needs zero lines of code.

Once that column is green, everything left is Linux. The only exception in the list is #84 (custom install path on Windows), an ordinary feature request rather than part of this.

How many people are behind each row

GitHub publishes per-asset download counts. v2.7.2, three days after release:

Windows  x64 installer     540  ┐
         x64 portable      245  │  818 = 91%
         arm64 installer    17  │
         arm64 portable     16  ┘
macOS    universal.dmg      37  =  4%
Linux    AppImage           26  ┐
         .deb               15  │   44 =  5%
         .rpm                3  ┘

Chocolatey's feed reports 6–22 installs per version. The Snap Store publishes nothing — that is structural, and the snap section below explains why. The ratio holds across v2.7.0 and v2.7.1 too, so it is not an artefact of a three-day window.

These are downloads, not users, and they say nothing about who is already installed and updating in place. But the shape is stark enough to order the work:


1. Signing — @alecdotdev

One action, five issues, no code, and 91% of downloads on the Windows half. It is the highest-value item here by a wide margin and the only one nobody can implement without you.

Windows may be free. SignPath Foundation gives OSS projects free OV code signing through a managed pipeline. Their conditions: OSI-approved licence with no commercial dual-licensing, no proprietary components, actively maintained, already released in the form to be signed. Markpad appears to meet every line. Approval takes days to weeks.

The judgement call is not technical: artifacts would be signed on a third-party managed platform. That is the same class of question raised in #500 about what sits next to TAURI_SIGNING_PRIVATE_KEY.

macOS is $99/year and has history. In #209 you said you would look into the Apple Developer Program; I said not to take the cost on purely for cross-platform development, and that my own lapsed membership might be an option later. It is still needed, so that offer stands — but who the releasing identity is belongs to you, and I do not want to decide it by implementing it.

Why signing and not a workflow fix — the mechanism
macOS      ad-hoc signature, no Developer ID, not notarized
           → macOS cannot bind a persistent TCC grant to this identity
           → #209, #505, #557: the folder-permission prompt returns forever
           → Gatekeeper refuses first launch; the dialog offers only
             Cancel and Move to Trash

Windows    no Authenticode signature
           → SmartScreen "unrecognized app"
           → #334 "the windows installer has a trojan virus"
           → #466 VirusTotal heuristic on the portable exe

tauri.conf.json still carries "signingIdentity": null and "entitlements": null, and there is no notarization step. Neither symptom is reachable from application code or from CI.

The paid Windows alternative is Azure Trusted Signing at $9.99/month, but it is limited to verified US/CA/EU/UK businesses and self-employed individuals — identity validation is the gate rather than the price.

Until either lands, the release notes' "sign it yourself in Keychain Access" workaround (thanks @nashv, #209) is the ceiling, and it has to be redone after every update.

What I need: yes/no on applying to SignPath for Windows, and separately whether macOS signing is something you want to own, want me to explore with my own Developer ID, or want left documented as a known limitation.


2. Linux should have one channel that can update itself — @LargeModGames

Four Linux artifacts today: one is dead, two cannot update, one is structurally fragile. Adding more — AUR, Flatpak, winget — is the wrong instinct, because the channel count is the complexity. The target is one line that can update itself, plus the others being honest about what they are:

keep one          AppImage  or  Flatpak       ← pick one, not both
say the truth     .deb / .rpm: installs, does not auto-update
retire            snap

Keep it proportional while reading this: Linux is 5% of downloads, and within it the split is AppImage 26, .deb 15, .rpm 3 per release. The AppImage is already the channel most Linux users pick.

AppImage or Flatpak is the real question. AppImage self-updates but carries libraries that must come from the host, which is what #182 and #498 both were — fixed twice by hand, and CI can never catch the next one, because the runner's Mesa is the one the libraries were copied from. #498 had to be found by a user on Arch. Flatpak takes the graphics stack and WebKitGTK from the runtime, so that class of bug does not arise.

The honest summary of Flatpak, with the costs measured below: it would be a better-behaved AppImage, not a categorically safer package. The sandbox has to be opened up anyway for a file editor, and the in-app updater has to be patched out. That is still worth having — a better-behaved AppImage is exactly what #498 asked for — but it should not be sold as more.

Flatpak: what it costs, measured against a Tauri app already on Flathub

Read off flathub/in.cinny.Cinny — Cinny Desktop is Tauri v2 with both npm and cargo dependencies, the same shape as Markpad, and live on Flathub today — plus the Flathub requirements.

One-time

item size in Cinny's repo notes
manifest 3.0 KB runtime org.gnome.Platform 50, finish-args, build commands
appdata.xml 4.7 KB mandatory AppStream metainfo, must pass validation. Markpad has none
.desktop 0.4 KB must be named after the app ID
Flathub PR — fork, new-pr branch, review rounds, then push access to our own flathub/<id> repo

The app ID has to be decided first. Flathub requires reverse-DNS on a domain we control, or a code-hosting prefix with at least four components. com.alecdotdev.markpad does not qualify unless alecdotdev.com is ours. Either dev.sftwr.Markpad (matches the existing website) or io.github.sftwrdotdev.Markpad (needs no domain). It becomes the desktop-file name, the metainfo ID and the Flathub URL, so it is worth picking once, deliberately.

Per release, and it is automatable. Flathub builds with no network access, so every npm and cargo dependency is vendored into the manifest: cargo-sources.json 331 KB, node-sources.json 1.27 MB, regenerated on every upstream release. Cinny automates it — a weekly cron in the Flathub repo runs flatpak-external-data-checker, re-runs the two generators, and opens a PR; automerge-flathubbot-prs: false keeps a human in the loop. Steady state is reviewing one bot PR per release, plus non-release maintenance: Cinny's log shows a GNOME 48→50 bump and three libvips bumps in three months.

Three costs specific to Markpad, which are what make the answer non-obvious:

  1. The in-app updater has to be disabled in the Flatpak build. /app is read-only in the sandbox. Cinny carries 0001-disable-tauri-updater.patch for exactly this. Flatpak would join .deb/.rpm/snap in "updates come from the channel".
  2. The sandbox is largely surrendered anyway. Cinny's manifest is candid: "Tauri does not yet support the Freedesktop.org File Transfer portal, so this is needed to support the drag and drop files" → --filesystem=home; and Tauri writes <a download> targets straight into XDG_DOWNLOAD_DIR instead of using the File Chooser portal. Markpad opens arbitrary paths for a living and would need at least the same.
  3. Cinny ships x11-only — --socket=wayland commented out, reason recorded: "Wayland has title bar color related issues."
The snap: dead since June, and that is worse than not having one

api.snapcraft.io for markpad: stable / amd64 / revision 15 / version 2.6.11 / released 2026-06-03. Six versions behind. The build has failed every time since:

Environment validation failed for part 'markpad': 'rustup' not found and part
'markpad' does not depend on a part named 'rust-deps' that would satisfy the
dependency.

That line is from the successful 2.7.2 run — continue-on-error turned it into a green check. #561 fixed the build and removed the swallowing.

Nobody reported it, and that is not evidence nobody is affected — it is what the failure looks like from outside:

no snap at all   →  user downloads .deb / AppImage, knows updates are manual
a dead snap      →  snapd checks daily and tells them they are current.
                    They do not have #463, #498, #544, #548, #546 — and they
                    have no reason to suspect it.

Auto-update is the only thing a snap buys over the .deb, and that is exactly what broke.

Cost, measured. On 2026-06-03, the last run where it built, the snap step took 16m31s of a 26m18s Linux job. Since it broke, the same job is 12m57s. snapcraft.yaml runs a full npm ci + cargo build --release inside LXD and reuses nothing from the Build Linux step above it — same binary, compiled twice.

Reach. snapd ships by default essentially only on Ubuntu; Fedora, Arch and openSUSE need it installed by hand, and Mint blocks it. Fit. The home interface does not cover hidden paths under $HOME, and removable-media is absent and would not auto-connect. We spent this cycle on macOS permission prompts; the snap builds a similar wall on Linux by design.

The Snap Store publishes no install counts, and that is structural rather than an oversight: .snap, snapd and the Snap Store are one vendor's stack and the store server is not open source, so there is no second place to look and no public API. Weekly active devices and installs-by-distro are in the snapcraft dashboard's Metrics tab, visible only to whoever holds SNAPCRAFT_STORE_CREDENTIALS. (Both other channels answered on the first try: GitHub exposes per-asset download counts, Chocolatey exposes them in its OData feed.)

For scale when reading that number: all four Linux channels together account for 44 GitHub downloads per release.

dashboard shows do this
three figures or more keep it. #561 already fixed the build; then add removable-media and stop recompiling
two figures or fewer retire it — but not by deleting the workflow. Existing installs would sit on 2.6.11 forever. It needs one last upload whose description points at the .deb/AppImage, and the sudo snap install markpad line removed from README and the release template

The tombstone is the only part of "drop it" that is real work, and the part that is easy to forget.

What I need: from @LargeModGames, AppImage or Flatpak, and whether you would want to hold a Flathub repo — "nobody wants to own it" is a fine answer, and better said now than after a Flathub PR is open. From @alecdotdev, roughly what the snapcraft dashboard says.


3. One more question, and two things that need nobody's permission — @alecdotdev

Would you want the release action itself reduced to one command? Today, cutting a release is: edit version in package.json, edit it again in src-tauri/Cargo.toml, commit, tag, push, then open Actions and dispatch the workflow. Six steps, two of which are the same fact written twice — scripts/releaseWorkflow.test.ts guards them against drifting, a test that exists because the drift is easy.

npm run release 2.7.3 would collapse five of the six. Two preferences I would want from you before writing it, because they are yours rather than facts:

  1. Should pushing a tag trigger the release build, or should dispatching stay manual? A tag trigger is fewer steps; a manual dispatch means an accidental tag push cannot start a release. I lean toward the tag trigger, since the actual gate is still clicking Publish on the draft — but you are the one who would be surprised by it.
  2. Should it touch the changelog? 2.7.3 release notes — what changed since 2.7.2 #556 suggests release notes are their own work. I would default to stopping at the version bump.

This is the only item here that pays off on every future release rather than once.

Not questions, just not done yet:


Already fixed, no decisions involved

#561 Chocolatey and the Snap Store are published from release: published, not from inside the build matrix. markpad-app 2.7.2 had been pushed at 15:37 UTC on 2026-08-07 by a run that then failed and produced no release. Both continue-on-errors removed; the snap build fixed (rust-deps)
#566 The workflow_dispatch recovery path stopped reporting a Chocolatey failure that meant nothing; README and RELEASING.md stopped telling .deb/.rpm users they get updates
#570 → #573 .deb, .rpm and snap installs were offered an update and then failed to install it — __TAURI_BUNDLE_TYPE is not patched into the Linux binary, so every Linux package took the AppImage install path. Now they are told where updates actually come from
#572, #574 CI: cargo caching, bounded to one set written on master, after the first attempt was measured saving two seconds

Summary

  1. Signing — @alecdotdev. Five issues, two platforms, no code, 91% of downloads. Do this first even if nothing else happens.
  2. One Linux channel that updates itself — @LargeModGames on AppImage-or-Flatpak; @alecdotdev on the snap number. 5% of downloads: keep it proportional.
  3. The release script — @alecdotdev, two preferences above.

Activity

  1. changed the title [-]Packaging: what #561 fixes, and the three decisions it does not[/-] [+]Packaging: one fix removes half of this list, and the rest is Linux[/+] on Aug 10, 2026
  2. added
    awaiting decisionNeeds a product-direction call from the maintainer before work can start
    dependenciesPull requests that update a dependency file
    on Aug 10, 2026
  3. PathGao commented on Aug 10, 2026

    @PathGao
    CollaboratorAuthor

    @alecdotdev @LargeModGames — the issue above is now the whole thing in one place. It previously grew a trail of comments correcting itself as evidence came in; those are folded into the body and deleted, so there is one version to read rather than four.

    Three answers are what this is waiting on. None of them blocks any of the merged work.

    @alecdotdev

    1. SignPath Foundation for Windows signing — yes or no. Free, and it is 91% of downloads.
    2. Roughly what the snapcraft dashboard Metrics tab says. Nobody else can see that number, and it decides the snap either way.
    3. Whether you want npm run release X.Y.Z — and if so, the two preferences in section 3.

    @LargeModGames
    4. AppImage or Flatpak, and whether you would want to hold a Flathub repo. The costs are measured in the folded block in section 2, and "nobody wants to own it" is a fine answer — better said now than after a Flathub PR is open.

  4. PathGao commented on Aug 12, 2026

    @PathGao
    CollaboratorAuthor

    The snap half of section 2 has moved since I wrote it, in a way that makes the
    decision cheaper rather than more urgent. Sections 1 and 3 are unchanged and
    still need your answers.

    The build works. v2.7.3's publish-packages run
    (31464054514)
    had Chocolatey green and snap red — the rust-deps part #566 added hit a
    GLIBC_PRIVATE symbol lookup, because extensions: [gnome] puts the SDK's
    libc.so.6 ahead of the classic rustup snap's own. #577 drops plugin: rust
    for plugin: nil (nothing in that part had ever used the plugin) and #579 stops
    the snap recompiling Markpad inside LXD — it packages the release's own .deb,
    so it is the same binary, in about a third of the time. snapcraft pack ran
    green twice on pull requests before that file was merged.

    The store is still on 2.6.11. api.snapcraft.io today:
    stable / amd64 / 2.6.11 / revision 15 / 2026-06-03. So whichever way this
    goes, 2.7.4 is the first thing those installs have seen since June.

    Which changes what the Metrics number means. The table in the folded snap
    block says "three figures or more, keep it; two figures or fewer, retire it".
    Read today, that number counts weekly actives on a snap that has been dead for
    three months — it measures who has not uninstalled, not who wants it. Ship
    2.7.4, wait a week, then read it. Same decision, on a number that means
    something, at the cost of one release we are cutting anyway. If the answer
    still comes back small, the tombstone upload described in that block is the
    work, and #566's test keeps it from being done half-way.

    One thing that did not improve: #601 removed the pull-request snap check, so
    snapcraft.yaml is again first executed after a change to it has been merged,
    tagged and published. The file going out with 2.7.4 packed green twice before
    that removal — the next edit to it is the unverified one. Noted here rather
    than argued; it is the arrangement that was in place before 2.7.3 too.

    Nothing above needs a decision before 2.7.4 goes out.

  5. alecdotdev commented on Aug 24, 2026

    @alecdotdev
    Collaborator

    @PathGao

    1. can go ahead with the SignPath. let me know whats needed from my end. apologies for the delay i'm having a busy summer LOL

    2. snapcraft metrics are as follows:

    Image
  6. PathGao commented on Aug 24, 2026

    @PathGao
    CollaboratorAuthor

    Thanks @alecdotdev — that answers 1 and 2. Below: what the Metrics number decides, one thing that has broken since, and the concrete list you asked for on SignPath.


    First, something that needs doing before the snap decision means anything

    v2.7.4 did not reach the Snap Store either. api.snapcraft.io today still says stable / amd64 / 2.6.11 / revision 15 / 2026-06-03. Nobody reported it, for the reason the folded block in section 2 gives: a stale snap and a current one look identical from outside.

    The cause is new, and it is not the build. Run 31775835301:

    Packed markpad_2.7.4_amd64.snap          ← #577 and #579 worked; the build is fine
    gh release upload …                      ← the .snap is on the v2.7.4 release page
    snapcraft push … --release stable
      The 'push' command was renamed to 'upload'.
      exit 64
    

    snapcraft push had been in the workflow since February and last succeeded on 2026-06-03. snapcraft 8 turned the old name into a hard error, and the job runs snap install snapcraft --classic, so the command it calls stopped existing without a commit here. It stayed invisible while the build failed first under a swallowed error; #561 removed the swallowing and #577/#579 fixed the build, so v2.7.4 was the first release to get far enough to hit it.

    #715 changes the one word. After it merges, publish-packages.yml → Run workflow → v2.7.4 uploads the snap already attached to that release; the Chocolatey job sees 2.7.4 on the feed and skips itself.

    Worth naming plainly: this is the third distinct defect found by publishing, in the file whose pull-request check #601 removed. Not re-arguing that here, just recording that the count is now three.


    1 → Metrics: the snap stays

    The figure top-right is cut off at the edge of the screenshot, but the plot puts it near 170, which is the "three figures or more, keep it" row of the table.

    The slope is the stronger half:

    Weekly active devices, by version
         ┌ 100 ────────────────────────────────
    ~170 │            2.6.11 ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓  ← today
    ~140 │      ╭────────────▓
         └──────┴─────────────────────────────┘
              Jun 7                       Aug 22
              last successful upload
    

    It rose about 25% across the three months the channel was dead, on a single flat version band with no churn to explain it. So that is not "people who have not uninstalled", which is what I warned the number would measure — those are new installs, arriving now, landing on a June build. My suggestion to ship 2.7.4 and re-read the number in a week is withdrawn; the shape answers it without waiting.

    So: keep, and the tombstone plan in that block is off the table. #715 also does the follow-up the "keep" row attached — removable-media, since home reaches $HOME and nothing else, so a file on a USB stick was invisible with no way for a user to grant it. The other half of that row, "stop recompiling", was #579.


    2 → SignPath: what is actually yours

    I read signpath.org/terms against Markpad. Eligibility is clean — BSD-3-Clause with no dual licensing, no proprietary components, maintained, already released in the form to be signed, documented on the download page, no security-tooling features, and the installer has an uninstaller. Nothing there needs work.

    What needs you, in order:

    Before applying

    1. MFA on GitHub for everyone with commit access. Their terms require it for both SignPath and the source repository, for all team members. This is the only item that can silently fail the application.
    2. Decide the three roles, which are a SignPath requirement rather than a formality: Authors (commit without review), Reviewers (review everyone else's PRs), Approvers (decide whether a given release may be signed). They can be the same small set, but they have to be written down.

    The application itself — the form at signpath.org/apply. It has to come from you: it is about ownership and control of the repository, and the certificate is issued to SignPath Foundation with their name on our binaries. I can draft every answer if you want to paste rather than compose.

    A "Code signing policy" section, on markpad.sftwr.dev. Required by their terms, on the home page and the download/release pages, using that exact heading, containing:

    • "Free code signing provided by SignPath.io, certificate by SignPath Foundation"
    • the three roles above, as links to GitHub teams or people
    • a privacy line. Ours can be their canned one verbatim, since Markpad has no telemetry: "This program will not transfer any information to other networked systems unless specifically requested by the user or the person installing or operating it."

    The README and the release-body table are mine. The website is yours, and it is the piece nobody else can do.

    And one ongoing cost, before you commit rather than after. Their terms: "Every release needs manual approval for signing." The action submits the built artifact and then blocks the release build waiting for an Approver to click approve, default timeout 600s. So a release stops mid-flight until you (or another Approver) act. That is not a reason against it — it is the same gate as clicking Publish on the draft — but it is a step added to every release, and it is the part that gets discovered at the worst moment.

    Mine: the workflow wiring, the artifact configuration, and the RELEASING.md step. Once approved, the repository needs SIGNPATH_API_TOKEN plus the organization id and two slugs. I will bring that as its own PR with the shape settled, because signing plugs into build.yml between upload and release rather than bolting onto the end, and the NSIS installer and the portable .exe are two artifacts, not one.


    Still open, shortest form

    @alecdotdev

    • macOS signing. You did not answer this one, and it has got cheaper since I asked: ci(macos): a signing identity that outlives a release, so the folder grant does (#209) #707 makes it three repository secrets from a certificate made in Keychain Access in five minutes — no Developer Program, no $99. TCC compares the requirement, not the issuer. The remaining decision is one trade-off, written into RELEASING.md by that PR: a self-signed certificate cannot be revoked, so if the .p12 leaks nobody can invalidate it, and rotating it costs every user their folder permissions. Yes, no, or "use a real Developer ID instead".
    • The release script. This shrank while we waited: chore(release): write the version once, in the three files it lives in #588 shipped npm run release X.Y.Z, which writes the version to all three places it lives — package.json, Cargo.toml and the Markpad entry in Cargo.lock, which is the one that got forgotten and caused the 2.7.2/2.7.3 skew. It deliberately stops before committing. What is left is only the two preferences: (a) should pushing a tag start the release build, or stay a manual dispatch, and (b) should the script touch the changelog. I lean tag-trigger and no-changelog.

    @LargeModGames — section 2's question is unchanged: AppImage or Flatpak, and whether you would want to hold a Flathub repo. "Nobody wants to own it" remains a fine answer.

  7. LargeModGames commented on Aug 24, 2026

    @LargeModGames
    Contributor

    @LargeModGames — section 2's question is unchanged: AppImage or Flatpak, and whether you would want to hold a Flathub repo. "Nobody wants to own it" remains a fine answer.

    I personally have no experience how it would work with publishing on Flathub, im sorry

  8. alecdotdev commented on Aug 25, 2026

    @alecdotdev
    Collaborator

    @PathGao

    • macOS addressed and ready.
    • tag-trigger build sounds good to me. the current changelog setup is good, although the Windows smart screen warning can be removed, it appears its no longer reporting the false positive since reporting it: scan result. also i suppose the warning for macOS can be tweaked accordingly.

    i can also look into flathub

  9. alecdotdev commented on Aug 25, 2026

    @alecdotdev
    Collaborator

    will get on SignPath tomorrow, and website is scheduled for an overhaul to account for all the changes.
    I'll transfer the website repo to this org soon as well.

  10. alecdotdev commented on Aug 25, 2026

    @alecdotdev
    Collaborator

    @PathGao snap v2.7.4 build published successfully!

  11. 2 remaining items

  12. PathGao commented on Aug 26, 2026

    @PathGao
    CollaboratorAuthor

    will get on SignPath tomorrow, and website is scheduled for an overhaul to account for all the changes. I'll transfer the website repo to this org soon as well.

    Have you done SignPath now?

  13. alecdotdev commented on Aug 26, 2026

    @alecdotdev
    Collaborator

    @PathGao getting to that shortly. using https://app.signpath.io how would we sign both portable and installer files?

  14. PathGao commented on Aug 26, 2026

    @PathGao
    CollaboratorAuthor

    using https://app.signpath.io how would we sign both portable and installer files?

    One signing request, not two. SignPath doesn't sign a file, it signs a ZIP — and an artifact configuration says which files inside that ZIP to sign. So all four Windows exes go up in one ZIP, you click approve once, and four signed exes come back.

    build (x64 + arm64)
          │  4 exes → one zip → SignPath
          │
          └──► you click Approve once ──► 4 signed exes come back
                                              │
                                              └──► release page + updater feed
    

    That is the whole answer to your question. The rest is the setup around it.


    What you do in app.signpath.io

    SignPath creates the organization and project themselves when the Foundation application is approved. After that, five things, all in the web UI:

    1. Install the SignPath GitHub App on the sftwrdotdev org and give it access to this repo. Their connector uses it to check the artifact really came from a GitHub Actions run and not from someone holding the API token.
    2. Add the trusted build system "GitHub.com" to the organization and link it to the Markpad project. It's a pre-defined entry, just pick it.
    3. Add an artifact configuration — choose Custom, paste this:
    <artifact-configuration xmlns="http://signpath.io/artifact-configuration/v1">
      <zip-file>
        <pe-file path="Markpad_*_x64-setup.exe"><authenticode-sign/></pe-file>
        <pe-file path="Markpad_*_x64.exe"><authenticode-sign/></pe-file>
        <pe-file path="Markpad_*_arm64-setup.exe"><authenticode-sign/></pe-file>
        <pe-file path="Markpad_*_arm64.exe"><authenticode-sign/></pe-file>
      </zip-file>
    </artifact-configuration>

    Two lines are the installers, two are the portables. The * is the version, so it doesn't need editing per release.

    1. Set the signing policy's approvers — that's the Approvers role from the list I sent, and it's the click that releases each build.
    2. Create a CI user with submitter permission and generate an API token, then add it to the repo as SIGNPATH_API_TOKEN.

    Then send me four strings: organization id, project slug, signing policy slug, artifact configuration slug. That's everything I need to wire the workflow.


    Two things worth knowing before you turn it on

    The release build stops and waits for you. The action submits the ZIP and then blocks until an approver clicks approve — default timeout 10 minutes, after which the job fails. I'll set it to an hour. Practically: after you start a release, the Windows half pauses until you approve it. Nothing is uploaded before that, so a timeout just means re-running one job, not a half-signed release.

    Signing the installer doesn't sign the copy of Markpad it installs. SignPath can sign inside MSI files, but an NSIS installer is just an exe with an archive glued on, so nothing can reach inside it after it's built. What people actually hit — SmartScreen on the downloaded file, and the VirusTotal heuristic on the portable exe (#334, #466) — is on the two files we sign, so this fixes the reported problem. Signing the installed copy too would mean signing before the installer is packed, which is a second approval and a second build pass. Not worth it now; it can be added later if anything complains.

    And one that isn't optional, so you know why this is more than "add a step". Authenticode changes the installer's bytes, and Markpad_x.y.z_x64-setup.exe.sig — the file the auto-updater checks — is a signature over the old bytes. If it isn't regenerated after signing, every Windows install rejects its next update. Same problem the AppImage has after strip-appimage.sh, solved the same way: re-sign, then build latest.json. That's mine, it just decides where signing sits in the workflow.


    Still yours, unchanged from the list above

    • MFA on GitHub for everyone with commit access — the one that fails the application quietly.
    • The three roles written down — Authors, Reviewers, Approvers. Approvers is also step 4 above.
    • The "Code signing policy" section on markpad.sftwr.dev, that exact heading, on the home and download pages. Fits the overhaul you mentioned. I'll draft the text if you want to paste rather than write it.
  15. PathGao commented on Sep 2, 2026

    @PathGao
    CollaboratorAuthor

    @alecdotdev how about this. I found #722 may also caused by this.

  16. alecdotdev commented on Sep 3, 2026

    @alecdotdev
    Collaborator

    @PathGao

    SignPath Strings:

    • Organization Id: 005f9e34-9ae9-453d-998e-d73e2390ce6b
    • Project Slug: markpad
    • Signing PolicySlug: release-signing
    • Artifact Confiruation Slug: initial

    any variables needed to put in the repo secrets? let me know if anything else is needed.

    artifact signs successfully :
    Image

  17. PathGao commented on Sep 4, 2026

    @PathGao
    CollaboratorAuthor

    One secret: SIGNPATH_API_TOKEN — a CI user with Submitter permission on the release-signing policy. The four strings above are not secrets; they go into the workflow as plain values.

    Four things to confirm before the first run. Any one of them missing means the submission is rejected rather than queued, and a successful signing request from the web UI does not cover the first two — those are only checked when the artifact arrives from GitHub Actions.

    1. The SignPath GitHub App is installed on sftwrdotdev and has access to this repository.
    2. GitHub.com is added as a trusted build system and linked to the Markpad project.
    3. initial holds the artifact configuration from my 26 Aug comment — a <zip-file> with the four <pe-file> entries. If it is still SignPath's default, the four-exe ZIP signs nothing.
    4. You are an approver on release-signing. The Windows job stops on that click.

    Then it is one pull request on my side. x64 and arm64 are separate matrix jobs today and each uploads straight to the release page, so the change is: both hand their exes to one signing job, that job submits the single ZIP, and after the signed files come back it regenerates the .exe.sig updater signatures — Authenticode changes the bytes, so the ones tauri build produced no longer match — before anything is written to the release.

    Still yours and unchanged: MFA on GitHub for everyone with commit access, the three roles written down, and the Code signing policy section on markpad.sftwr.dev.

  18. alecdotdev commented on Sep 4, 2026

    @alecdotdev
    Collaborator

    @PathGao

    1. SignPath GH app is added to the org for this repo.
    2. unfortunately it looks like trusted build isnt available without upgrading... cheapest plan looks to be $500 CAD per year.
    Image 3. the artifact config is set to your xml definition, just kept the original slug.

    API token has been added as well.

    my account has MFA, adding code sign policy to site now

  19. PathGao commented on Sep 4, 2026

    @PathGao
    CollaboratorAuthor

    @alecdotdev Don't pay that. The wall is the Free trial's, not the open-source programme's — SignPath's own documentation says trusted build systems are "Available for Advanced Code Signing, Code Signing Gateway. Required for Open Source Code Signing", on both the Trusted Build Systems and Origin Verification pages. It is included in a Foundation subscription because the Foundation certificate's whole promise rests on it: "For each release, SignPath.io verifies the origin of signed files … This verification is automatic and technically enforced."

    The missing step is somewhere else. The Foundation programme is applied for at https://signpath.org/apply, and SignPath creates the account and the organization after they verify the project — the form says so about the name you give it. An organization you sign up for yourself on app.signpath.io is a trial, which is why that feature is behind a wall in this one. Markpad meets the conditions: BSD-3-Clause is OSI-approved, it is released, maintained and documented. On the form, Build System is GitHub and the repository is this one.

    Please delete the SIGNPATH_API_TOKEN secret in the meantime. It points at the trial organization, and without a linked trusted build system the connector rejects the submission rather than queueing it — so with the token present, merging #753 and cutting 2.7.7 fails the Windows half and uploads no Windows assets at all. With the secret gone, #753 is safe to merge: the job uploads what the matrix built, unsigned, and the release notes go on saying so.

    Worth a look while you are in there: which certificate the policy signs with. A trial usually issues a test certificate, which is not chained to a CA any operating system trusts — signing with it would change nothing about SmartScreen even if the submission went through.

    Once the Foundation organization exists, send me the four strings from it and I will swap the three lines in #753; you add the token back. If the application takes longer than the week #752 allows, cut 2.7.7 unsigned as planned.

  20. removed
    awaiting decisionNeeds a product-direction call from the maintainer before work can start
    on Sep 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    dependenciesPull requests that update a dependency file

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions