Skip to content

Submit Lagebuch to winget-pkgs #209

Closed

Description

@DeepDiver1975

Goal

Get Lagebuch installable via `winget install`. No code-signing requirement for submission (confirmed against Microsoft's docs) — this can proceed independently of the SignPath work.

Plan

  1. Hand-write the 3 manifest files (version/installer/locale) for `manifests/c/CodeForFire/Lagebuch/0.3.0/` in a fork of microsoft/winget-pkgs — `wingetcreate` isn't available cross-platform so this is manual.
  2. Compute SHA256 of the released MSI (`lagebuch-0.3.0-x64.msi`), fill in silent-install info (MSI default, no custom switches needed).
  3. Push to a branch on the fork, open a PR against microsoft/winget-pkgs.
  4. Note: MSI is unsigned — allowed, but SmartScreen reputation will still build up gradually for users installing via winget until a cert is in place ([[SignPath issue]]).

Status

In progress — this issue will be updated with the PR link once opened.

Activity

  1. DeepDiver1975 commented on Sep 4, 2026

    @DeepDiver1975
    ContributorAuthor

    Result: PR opened

    microsoft/winget-pkgs#429479: microsoft/winget-pkgs#429479

    • Manifests hand-written for manifests/c/CodeForFire/Lagebuch/0.3.0/ (PackageIdentifier CodeForFire.Lagebuch, schema 1.12.0) — wingetcreate isn't available on Linux, so no auto-generation tool was used.
    • InstallerSha256 computed from the actual downloaded release asset (lagebuch-0.3.0-x64.msi, v0.3.0): 23184DD667E24DBBA219121BB039643F61A16589E074A0026B1E9F10AD89714D
    • Used AppsAndFeaturesEntries.UpgradeCode (the fixed WiX UpgradeCode from Lagebuch.wxs) instead of ProductCode, since the MSI's ProductCode is auto-generated per build (Package/@Id="*") and would break upgrade detection across versions.
    • Verification: no Windows machine available to run winget validate/winget install locally, so all three manifest files were validated against the official 1.12.0 JSON schemas (pulled from microsoft/winget-cli) with Python jsonschema — all three pass. Flagged this substitution explicitly in the PR checklist rather than falsely checking boxes for tools that weren't run.
    • Flagged in the PR description that the MSI is currently unsigned (SignPath application tracked in Apply to SignPath Foundation for free OSS code signing #208) in case winget-pkgs' review bot or a human reviewer raises it.

    Next

    This now waits on winget-pkgs maintainer/bot review (automated validation pipeline + manual approval). Future releases will need a new manifest version folder per release — worth automating from release.yml once the process is proven out once manually.

  2. self-assigned this
    on Sep 4, 2026
  3. DeepDiver1975 commented on Sep 5, 2026

    @DeepDiver1975
    ContributorAuthor

    0.4.0 has been release meanwhile ....

  4. DeepDiver1975 commented on Sep 5, 2026

    @DeepDiver1975
    ContributorAuthor

    Update: v0.4.0 released while #429479 is pending

    v0.4.0 shipped on 2026-09-05, so the submitted manifests (0.3.0) are already
    one version behind. PR microsoft/winget-pkgs#429479 is unaffected by
    this — it's a brand-new PackageIdentifier (CodeForFire.Lagebuch), all 10
    automated validation stages are green, and it's now sitting in the
    "requires moderator approval" queue. Nothing to do there but wait.

    Decision: don't touch #429479 and don't submit v0.4.0 in parallel — two
    competing versions of a not-yet-established package identity would likely
    just confuse moderators. Instead:

    1. Wait for #429479 to merge as v0.3.0.
    2. Once merged, submit a clean follow-up PR adding
      manifests/c/CodeForFire/Lagebuch/0.4.0/, reusing the same fork and the
      same fixed WiX UpgradeCode (so winget treats it as an upgrade, not a new
      package), with a freshly computed InstallerSha256 for
      lagebuch-0.4.0-x64.msi.
    3. Update this issue with the new PR link once opened.

    Also carrying forward from the previous update: manifest generation should
    eventually be automated from release.yml — this version-drift is exactly
    the kind of busywork that motivates it, and it'll recur every release until
    that's done.

  5. DeepDiver1975 commented on Sep 17, 2026

    @DeepDiver1975
    ContributorAuthor

    Status, 2026-09-17.

    Upstream submission: microsoft/winget-pkgs#429479, open since 2026-09-04. It passed all ten validation stages and has been waiting for a moderator ever since — community pull requests there need one, and they are volunteers.

    It has now been refreshed from 0.3.0 to 0.5.0, since 0.3.0 was three releases behind: current installer URL and SHA-256, the MSI's ProductCode, and an added de-DE locale so winget show speaks German to the people this is for. The four manifests validate against the published 1.12.0 JSON schemas; upstream validation is re-running.

    Automation: #378 adds a winget job to the release workflow. It runs winget-releaser (komac) over a published release and opens the upstream PR from the fork. Full releases only — winget has no notion of a pre-release — and continue-on-error, so it cannot redden a release that already shipped. It needs a WINGET_TOKEN secret, and it refuses to run until the package exists upstream, so #429479 has to land first.

    Left to do here: the WINGET_TOKEN secret, and once the package is in the catalogue, the README install line plus a CHANGELOG entry. Then this closes.

  6. DeepDiver1975 commented on Sep 17, 2026

    @DeepDiver1975
    ContributorAuthor

    Correction to the automation half above: #378 no longer adds a CI job.

    Komac needs a classic token with public_repo scope — its README says fine-grained tokens can create the commit but fail to open the pull request — so automating from CI would mean keeping a token with write access to every public repository its owner has in this repository's secrets. And the action that wraps komac, vedantmgoyal9/winget-releaser, last released in January 2025 and pulls cargo-bins/cargo-binstall@main unpinned.

    So submission stays a manual step at release time, run from a laptop with komac token add --token="$(gh auth token)" — no new credential, nothing stored here. #378 now only documents it in docs/releasing.md, including a by-hand manifest recipe for when komac is unavailable.

  7. added
    enhancementNew feature or request
    packagingRelease, distribution and code-signing infrastructure
    on Sep 21, 2026
  8. DeepDiver1975 commented on Oct 16, 2026

    @DeepDiver1975
    ContributorAuthor

    Done. CodeForFire.Lagebuch is live in winget-pkgs (https://github.com/microsoft/winget-pkgs/tree/master/manifests/c/CodeForFire/Lagebuch — 0.8.0 and 0.8.1), and the README documents winget install CodeForFire.Lagebuch. A winget install runs the MSI silently and raises no SmartScreen dialog, which was the point of milestone v0.10. The per-release submission is documented in docs/releasing.md#winget-windows-package-manager.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementNew feature or requestpackagingRelease, distribution and code-signing infrastructure

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions