Skip to content

Add signed apt and dnf repositories for the Linux packages - #338

Merged
stevyhacker merged 7 commits into
masterfrom
claude/gracious-curran-ac50b7
Oct 20, 2026
Merged

stevyhacker merged 7 commits into
masterfrom
claude/gracious-curran-ac50b7

Conversation

@stevyhacker

@stevyhacker stevyhacker commented Oct 20, 2026 •

Copy link
Copy Markdown
Owner

Summary

The Linux alpha will ship fixes often, but a .deb or .rpm installed from the release page never updates. This adds signed apt and dnf repositories at pkg.lokalbot.com, published by the release, and has the .deb and .rpm add them the way Chrome's and VS Code's packages do. Install the downloaded file once, and after that sudo apt upgrade or sudo dnf upgrade brings each stable release.

Nothing goes live until the owner does the one-time setup below: the job skips without its secrets, and the packages add the repository only once its public key is committed.

Workflow (.github/workflows/linux-repos.yml, called by a new linux-repos job in release.yml for stable tags only)

  • Runs on GitHub-hosted runners only. The ready job skips with a notice when a LINUX_REPO_* secret is missing. It fails instead if the public key is already committed, because that release's packages point at the repository.
  • publish downloads the release's .deb and .rpm, checks their .sha256 and versions, imports the key, and checks that the key is in the committed keyring. It warns 180 days before the key expires. It then copies the published packages from R2 and runs LinuxWindows/scripts/linux-repos.sh. The signing key is deleted before the upload step.
  • Upload order: packages and hash-named indexes first (immutable), then the signed indexes (Cache-Control: no-cache), then deletion of pruned packages. Last, it checks that pkg.lokalbot.com serves what was uploaded.
  • gh workflow run linux-repos.yml -f tag=vX.Y.Z publishes a release that is already out.
  • On PRs that touch the repository or packaging files, it runs the container check below, with no secrets.

LinuxWindows/scripts/linux-repos.sh

  • apt: built with apt-ftparchive (suite stable, component main, amd64, SHA-256 only). Has Acquire-By-Hash, so a cached index can't mismatch, plus a signed InRelease and Release.gpg.
  • dnf: built with createrepo_c, with repomd.xml.asc. RPMs are signed with rpmsign.
  • A version that is already published is never replaced. The newest 3 versions are kept.
  • Every signature is checked against the public key before anything is uploaded.

Packaging (package-linux-distros.sh, +37 lines): once packaging/linux/lokalbot-archive-keyring.asc exists, the packages ship the repository files below. The Arch package is unchanged. The script also gains three env overrides, used only by the check.

Package Repository file Key
.deb /etc/apt/sources.list.d/lokalbot.sources (deb822, conffile) /usr/share/keyrings/lokalbot-archive-keyring.gpg
.rpm /etc/yum.repos.d/lokalbot.repo (%config(noreplace), gpgcheck=1, repo_gpgcheck=1, skip_if_unavailable=True) /etc/pki/rpm-gpg/RPM-GPG-KEY-lokalbot

App (lokalbot-update/src/package.rs, on top of #335): package::owner(), already off the UI thread, also reads /etc/apt/sources.list.d/lokalbot.sources (dpkg) or /etc/yum.repos.d/lokalbot.repo (rpm). When the file is there and not turned off (Enabled: no / enabled=0), the release's lokalbot package routes to the package manager. It is then told "Update LokalBot with your package manager, for example sudo apt upgrade" (or sudo dnf upgrade), using #335's existing string, so no new translations are needed.

Docs

Validation

LinuxWindows/scripts/ci/check-linux-repos.sh ran on the Ubuntu box (own working directory; its containers, network and files removed afterwards). It packages v0.11.0's release binaries as 0.11.0–0.11.3 with a throwaway key. It serves the repository over HTTPS as pkg.lokalbot.com on a private Docker network, with a throwaway CA trusted in the clients. Then, in clean ubuntu:24.04, debian:13 and fedora:latest (Fedora 44) containers:

  • The .deb and .rpm mark the repository files as config files; the Arch package has none.
  • Install 0.11.0 from the file, then apt update/apt upgrade and dnf upgrade to 0.11.1 with an edited repository file (kept, no .dpkg-dist/.rpmnew). Fedora shows the RPM signature RSA/SHA256 … Key ID.
  • A tampered InRelease and a tampered Release (with InRelease removed) are refused by Ubuntu's gpgv (BADSIG) and Debian 13's sqv ("Message has been manipulated"). A tampered repomd.xml is refused by dnf ("Bad PGP signature").
  • Publishing 0.11.2 and 0.11.3 drops 0.11.0 from both repositories.
  • A swapped .deb (apt: unexpected size), a swapped .rpm (dnf: checksum doesn't match) and an unsigned .rpm behind signed metadata (dnf: "The package is not signed") are refused, and the installed version stays 0.11.1. After restoring, all three upgrade to 0.11.3.
  • apt fetched its indexes by hash.
Transcript (NFPM=… scripts/ci/check-linux-repos.sh release/LokalBot-0.11.0-linux-x86_64; gpgv lines and dependency installs trimmed)

=== Publisher and HTTPS server for pkg.lokalbot.com (Ubuntu 24.04, like the release runner)
throwaway key 7412EA961A0F0F1A631F27B56AD0A9B1EB03E02A

=== Packages 0.11.0 0.11.1 0.11.2 0.11.3 with the throwaway key
ok: the .deb and .rpm add the repository as config files; the Arch package does not

=== Publish 0.11.0
added lokalbot_0.11.0-1_amd64.deb
added lokalbot-0.11.0-1.x86_64.rpm
apt: 1 versions; rpm: 1 versions

=== ubuntu:24.04: install 0.11.0 from the downloaded file
Get:3 https://pkg.lokalbot.com/apt stable InRelease [1130 B]
Get:5 https://pkg.lokalbot.com/apt stable/main amd64 Packages [638 B]
lokalbot:
  Installed: 0.11.0-1
  Candidate: 0.11.0-1
  Version table:
 *** 0.11.0-1 500
        500 https://pkg.lokalbot.com/apt stable/main amd64 Packages
        100 /var/lib/dpkg/status
ok: ubuntu:24.04 has lokalbot 0.11.0

=== debian:13: install 0.11.0 from the downloaded file
Get:3 https://pkg.lokalbot.com/apt stable InRelease [1130 B]
Get:4 https://pkg.lokalbot.com/apt stable/main amd64 Packages [638 B]
lokalbot:
  Installed: 0.11.0-1
  Candidate: 0.11.0-1
  Version table:
 *** 0.11.0-1 500
        500 https://pkg.lokalbot.com/apt stable/main amd64 Packages
        100 /var/lib/dpkg/status
ok: debian:13 has lokalbot 0.11.0

=== fedora:latest: install 0.11.0 from the downloaded file
[11/11] Installing lokalbot-0:0.11.0-1. 100% | 190.6 MiB/s | 123.7 MiB |  00m01s
Warning: skipped OpenPGP checks for 1 package from repository: @commandline
 LokalBot (alpha)                       100% |  44.0 KiB/s |   2.2 KiB |  00m00s
Importing OpenPGP key 0xEB03E02A:
 UserID     : "LokalBot repository check (throwaway)"
 From       : file:///etc/pki/rpm-gpg/RPM-GPG-KEY-lokalbot
The key was successfully imported.
 LokalBot (alpha)                       100% |  42.3 KiB/s |   3.2 KiB |  00m00s
Metadata cache created.
ok: fedora:latest has lokalbot 0.11.0

=== Edit the repository files, publish 0.11.1, upgrade
added lokalbot_0.11.1-1_amd64.deb
added lokalbot-0.11.1-1.x86_64.rpm
apt: 2 versions; rpm: 2 versions
Get:2 https://pkg.lokalbot.com/apt stable InRelease [1130 B]
Get:5 https://pkg.lokalbot.com/apt stable/main amd64 Packages [715 B]
1 package can be upgraded. Run 'apt list --upgradable' to see it.
The following packages will be upgraded:
  lokalbot
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Get:1 https://pkg.lokalbot.com/apt stable/main amd64 lokalbot amd64 0.11.1-1 [50.6 MB]
Preparing to unpack .../lokalbot_0.11.1-1_amd64.deb ...
Unpacking lokalbot (0.11.1-1) over (0.11.0-1) ...
Setting up lokalbot (0.11.1-1) ...
ok: ubuntu:24.04 has lokalbot 0.11.1
ok: ubuntu:24.04 kept the edited repository file
Get:4 https://pkg.lokalbot.com/apt stable InRelease [1130 B]
Get:5 https://pkg.lokalbot.com/apt stable/main amd64 Packages [715 B]
1 package can be upgraded. Run 'apt list --upgradable' to see it.
  lokalbot
Get:1 https://pkg.lokalbot.com/apt stable/main amd64 lokalbot amd64 0.11.1-1 [50.6 MB]
Preparing to unpack .../lokalbot_0.11.1-1_amd64.deb ...
Unpacking lokalbot (0.11.1-1) over (0.11.0-1) ...
Setting up lokalbot (0.11.1-1) ...
ok: debian:13 has lokalbot 0.11.1
ok: debian:13 kept the edited repository file
 LokalBot (alpha)                       100% |  43.1 KiB/s |   2.2 KiB |  00m00s
Upgrading:
 lokalbot                                x86_64 0:0.11.1-1                  lokalbot                         123.7 MiB
   replacing lokalbot                    x86_64 0:0.11.0-1                  @commandline                     123.7 MiB
[27/34] lokalbot-0:0.11.1-1.x86_64      100% | 301.9 MiB/s |  48.0 MiB |  00m00s
Importing OpenPGP key 0xEB03E02A:
 UserID     : "LokalBot repository check (throwaway)"
 From       : file:///etc/pki/rpm-gpg/RPM-GPG-KEY-lokalbot
The key was successfully imported.
[34/69] Upgrading lokalbot-0:0.11.1-1.x 100% | 324.7 MiB/s | 123.7 MiB |  00m00s
[54/69] Removing lokalbot-0:0.11.0-1.x8 100% |   1.4 KiB/s |  16.0   B |  00m00s
signature: RSA/SHA256, Tue Oct 20 13:08:51 2026, Key ID 6ad0a9b1eb03e02a
ok: fedora:latest has lokalbot 0.11.1
ok: fedora:latest kept the edited repository file

=== Tampered indexes
  The following signatures were invalid: BADSIG 6AD0A9B1EB03E02A LokalBot repository check (throwaway)
Err:1 https://pkg.lokalbot.com/apt stable InRelease
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://pkg.lokalbot.com/apt stable InRelease: The following signatures were invalid: BADSIG 6AD0A9B1EB03E02A LokalBot repository check (throwaway)
W: Failed to fetch https://pkg.lokalbot.com/apt/dists/stable/InRelease  The following signatures were invalid: BADSIG 6AD0A9B1EB03E02A LokalBot repository check (throwaway)
W: Some index files failed to download. They have been ignored, or old ones used instead.
ok: ubuntu:24.04 refused a tampered InRelease
  Sub-process /usr/bin/sqv returned an error code (1), error message is: Verifying signature:            Message has been manipulated
Err:4 https://pkg.lokalbot.com/apt stable InRelease
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. OpenPGP signature verification failed: https://pkg.lokalbot.com/apt stable InRelease: Sub-process /usr/bin/sqv returned an error code (1), error message is: Verifying signature:            Message has been manipulated
W: Failed to fetch https://pkg.lokalbot.com/apt/dists/stable/InRelease  Sub-process /usr/bin/sqv returned an error code (1), error message is: Verifying signature:            Message has been manipulated
W: Some index files failed to download. They have been ignored, or old ones used instead.
ok: debian:13 refused a tampered InRelease
Ign:3 https://pkg.lokalbot.com/apt stable InRelease
Ign:7 https://pkg.lokalbot.com/apt stable Release.gpg
W: GPG error: https://pkg.lokalbot.com/apt stable Release: The following signatures were invalid: BADSIG 6AD0A9B1EB03E02A LokalBot repository check (throwaway)
E: The repository 'https://pkg.lokalbot.com/apt stable Release' is no longer signed.
ok: ubuntu:24.04 refused a tampered Release
Ign:4 https://pkg.lokalbot.com/apt stable InRelease
Ign:6 https://pkg.lokalbot.com/apt stable Release.gpg
W: OpenPGP signature verification failed: https://pkg.lokalbot.com/apt stable Release: Sub-process /usr/bin/sqv returned an error code (1), error message is: Verifying signature:            Message has been manipulated
E: The repository 'https://pkg.lokalbot.com/apt stable Release' is no longer signed.
ok: debian:13 refused a tampered Release
>>> repomd.xml GPG signature verification error: Bad PGP signature
Failed to download metadata (baseurl: "https://pkg.lokalbot.com/rpm") for repository "lokalbot": repomd.xml GPG signature verification error: Bad PGP signature
ok: fedora:latest refused a tampered repomd.xml
Get:2 https://pkg.lokalbot.com/apt stable InRelease [1130 B]
Get:4 https://pkg.lokalbot.com/apt stable InRelease [1130 B]
 LokalBot (alpha)                       100% |  45.9 KiB/s |   2.2 KiB |  00m00s
ok: restored indexes verify again

=== Publish 0.11.2 and 0.11.3: the oldest version leaves
added lokalbot_0.11.2-1_amd64.deb
added lokalbot-0.11.2-1.x86_64.rpm
added lokalbot_0.11.3-1_amd64.deb
added lokalbot-0.11.3-1.x86_64.rpm
removed lokalbot_0.11.0-1_amd64.deb
removed lokalbot-0.11.0-1.x86_64.rpm
apt: 3 versions; rpm: 3 versions
apt pool: lokalbot_0.11.1-1_amd64.deb lokalbot_0.11.2-1_amd64.deb lokalbot_0.11.3-1_amd64.deb 
rpm: lokalbot-0.11.1-1.x86_64.rpm lokalbot-0.11.2-1.x86_64.rpm lokalbot-0.11.3-1.x86_64.rpm 

=== Swapped and unsigned packages
  File has unexpected size (50630234 != 50630232). Mirror sync in progress? [IP: 10.0.14.2 443]
Err:1 https://pkg.lokalbot.com/apt stable/main amd64 lokalbot amd64 0.11.3-1
E: Failed to fetch https://pkg.lokalbot.com/apt/pool/main/l/lokalbot/lokalbot_0.11.3-1_amd64.deb  File has unexpected size (50630234 != 50630232). Mirror sync in progress? [IP: 10.0.14.2 443]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
ok: ubuntu:24.04 refused a swapped .deb
ok: ubuntu:24.04 has lokalbot 0.11.1
  File has unexpected size (50630234 != 50630232). Mirror sync in progress? [IP: 10.0.14.2 443]
Err:1 https://pkg.lokalbot.com/apt stable/main amd64 lokalbot amd64 0.11.3-1
E: Failed to fetch https://pkg.lokalbot.com/apt/pool/main/l/lokalbot/lokalbot_0.11.3-1_amd64.deb  File has unexpected size (50630234 != 50630232). Mirror sync in progress? [IP: 10.0.14.2 443]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
ok: debian:13 refused a swapped .deb
ok: debian:13 has lokalbot 0.11.1
Package               Arch   Version    Repository      Size
Total size of inbound packages is 48 MiB. Need to download 48 MiB.
>>> Downloading successful, but checksum doesn't match. Calculated: f919e64c176fe597bfe6d234451df5745734c037b23b9648d524093dbac377d8(sha256)  Expected: e3e8b469311a5bd958a7350c17418f344455a5384ee411b9ebef87ae3cb038f3(sha256)  - https://pkg.lokalbot.com/rpm/lokalbot-0.11.3-1.x86_64.rpm
ok: fedora:latest refused a swapped .rpm
ok: fedora:latest has lokalbot 0.11.1
Package               Arch   Version    Repository      Size
Total size of inbound packages is 48 MiB. Need to download 48 MiB.
Transaction failed: Signature verification failed.
OpenPGP check for package "lokalbot-0.11.3-1.x86_64" (/var/cache/libdnf5/lokalbot-9d06a5f6dd0c0b07/packages/lokalbot-0.11.3-1.x86_64.rpm) from repo "lokalbot" has failed: The package is not signed.
ok: fedora:latest refused an unsigned .rpm
ok: fedora:latest has lokalbot 0.11.1
apt: 3 versions; rpm: 3 versions

=== Upgrade to 0.11.3
Get:1 https://pkg.lokalbot.com/apt stable InRelease [1130 B]
The following packages will be upgraded:
  lokalbot
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Get:1 https://pkg.lokalbot.com/apt stable/main amd64 lokalbot amd64 0.11.3-1 [50.6 MB]
Preparing to unpack .../lokalbot_0.11.3-1_amd64.deb ...
Unpacking lokalbot (0.11.3-1) over (0.11.1-1) ...
Setting up lokalbot (0.11.3-1) ...
ok: ubuntu:24.04 has lokalbot 0.11.3
Get:4 https://pkg.lokalbot.com/apt stable InRelease [1130 B]
  lokalbot
Get:1 https://pkg.lokalbot.com/apt stable/main amd64 lokalbot amd64 0.11.3-1 [50.6 MB]
Preparing to unpack .../lokalbot_0.11.3-1_amd64.deb ...
Unpacking lokalbot (0.11.3-1) over (0.11.1-1) ...
Setting up lokalbot (0.11.3-1) ...
ok: debian:13 has lokalbot 0.11.3
 LokalBot (alpha)                       100% |  44.0 KiB/s |   2.2 KiB |  00m00s
Upgrading:
 lokalbot             x86_64 0:0.11.3-1 lokalbot   123.7 MiB
   replacing lokalbot x86_64 0:0.11.1-1 lokalbot   123.7 MiB
[1/1] lokalbot-0:0.11.3-1.x86_64        100% | 144.2 MiB/s |  48.0 MiB |  00m00s
[3/4] Upgrading lokalbot-0:0.11.3-1.x86 100% | 117.3 MiB/s | 123.7 MiB |  00m01s
[4/4] Removing lokalbot-0:0.11.1-1.x86_ 100% |  12.0   B/s |  16.0   B |  00m01s
ok: fedora:latest has lokalbot 0.11.3

=== Files the clients fetched
     14 /apt/dists/stable/InRelease
      6 /apt/dists/stable/main/binary-amd64/by-hash/SHA256/<sha256>
      2 /apt/dists/stable/Release
      2 /apt/dists/stable/Release.gpg
      2 /apt/pool/main/l/lokalbot/lokalbot_0.11.1-1_amd64.deb
      4 /apt/pool/main/l/lokalbot/lokalbot_0.11.3-1_amd64.deb
      1 /rpm/lokalbot-0.11.1-1.x86_64.rpm
      6 /rpm/lokalbot-0.11.3-1.x86_64.rpm
      8 /rpm/repodata/repomd.xml
      8 /rpm/repodata/repomd.xml.asc
      5 /rpm/repodata/<sha256>-primary.xml.gz

All repository checks passed.

Also:

  • App change on the Ubuntu box: cargo clippy -p lokalbot-update -p lokalbot-app --all-targets --locked -- -D warnings is clean, and cargo test -p lokalbot-update -p lokalbot-app --locked passes (37 and 51 tests). The new tests:
    • package::tests::release_packages_with_the_repository_file_update_from_it reads the shipped lokalbot.sources/lokalbot.repo. It covers turned-off files, the other manager's file and the Arch package.
    • updates::tests::release_packages_with_the_repository_are_told_to_upgrade.
  • cargo fmt --all -- --check and python3 scripts/sync-localizations.py --check: clean.
  • actionlint 1.7.12 on linux-repos.yml and release.yml: clean.
  • shellcheck -S warning on both new scripts: clean.
  • python3 Scripts/render_web.py --check (on Docs: the .deb and .rpm add the LokalBot repository #339's copy): up to date.

Not verified: the real R2 upload and pkg.lokalbot.com, because the bucket, token and key don't exist yet. The first gh workflow run linux-repos.yml -f tag=v0.11.0 after setup is that test, and its last step compares what the domain serves.

Changed test expectations

None.

Owner's one-time steps

Full commands are in RELEASING.md, "Linux package repositories → One-time setup".

  1. Generate the key on a trusted computer: RSA 4096, signing only, expiring in 3 years, no passphrase (CI can't type one). The backup is what protects it.
    export GNUPGHOME=$(mktemp -d)
    gpg --batch --passphrase '' --quick-generate-key \
      'LokalBot package signing <stevyhacker@users.noreply.github.com>' rsa4096 sign 3y
    FPR=$(gpg --with-colons --list-secret-keys | awk -F: '$1 == "fpr" {print $10; exit}')
    gpg --armor --export-options export-minimal --export "$FPR" > LinuxWindows/packaging/linux/lokalbot-archive-keyring.asc
    gpg --armor --export-secret-keys "$FPR" | gh secret set LINUX_REPO_GPG_PRIVATE_KEY --repo stevyhacker/lokalbot
    Keep the secret key export and $GNUPGHOME/openpgp-revocs.d/$FPR.rev in 1Password, then run rm -rf "$GNUPGHOME". Don't commit the .asc yet (step 5).
  2. Cloudflare:
    • Create the R2 bucket lokalbot-packages.
    • Under Settings → Custom Domains, connect pkg.lokalbot.com. Cloudflare adds the DNS record. Leave r2.dev off.
    • Create an R2 API token with Object Read & Write on that bucket only.
    • No cache rule is needed: every object carries its own Cache-Control.
  3. Secrets: gh secret set for LINUX_REPO_R2_ACCOUNT_ID, LINUX_REPO_R2_ACCESS_KEY_ID and LINUX_REPO_R2_SECRET_ACCESS_KEY.
  4. After merging, run gh workflow run linux-repos.yml -f tag=v0.11.0, then curl -fsS https://pkg.lokalbot.com/apt/dists/stable/InRelease. 0.11.0's packages don't add the repository, so nobody depends on it yet.
  5. Commit lokalbot-archive-keyring.asc into Docs: the .deb and .rpm add the LokalBot repository #339 (or ask me to, with the file), and merge Docs: the .deb and .rpm add the LokalBot repository #339. The next release's .deb and .rpm add the repository. From then on, a missing secret fails the release's linux-repos job.

Merging this PR publishes nothing and changes no installed package until steps 1–5 are done. Step 5 merges #339 with the key.

Risk / rollout notes

  • App advice (builds on Tell Linux package installs to update through their package manager #335): a release .deb/.rpm counts as "from the release" (told to install the downloaded package) only while it has no enabled repository file. The 0.11.0 installs, the Arch package and anyone who sets Enabled: no/enabled=0 keep the install command.
  • dnf picks up a new version within metadata_expire=6h (dnf upgrade --refresh sooner). apt sees it on the next apt update. The first dnf upgrade asks to import the key, the standard dnf prompt for a third-party repository. dnf5 asks twice: once for the signed metadata, once for the packages.
  • openSUSE: zypper doesn't read /etc/yum.repos.d, so the .rpm there still only gets the in-app notice. The docs say so. Adding /etc/zypp/repos.d/lokalbot.repo would be a small follow-up.
  • Overlaps:
  • Old indexes stay: by-hash/ and rpm/repodata/ keep older indexes (a few KB per release), so a client or cache holding the previous index still finds its files. Everything else in the bucket that the job didn't produce is deleted.

The .deb and .rpm from the release page never updated. Stable releases now
publish to apt and dnf repositories at pkg.lokalbot.com (Cloudflare R2), and
once the repository key is committed the packages add them themselves
(deb822 sources + keyring; yum .repo with gpgcheck and repo_gpgcheck + key),
so apt upgrade and dnf upgrade bring later versions.

- linux-repos.yml: called by release.yml for stable tags, or by hand for a
  published one. GitHub-hosted only; skips without the LINUX_REPO_* secrets
  (fails once the key is committed). Signs with rpmsign and gpg via
  scripts/linux-repos.sh, keeps the newest 3 versions, uploads with rclone
  in a cache-safe order and checks what the domain serves.
- On pull requests, scripts/ci/check-linux-repos.sh packages the latest
  release's binaries with a throwaway key and checks install, upgrade, kept
  edits and refusal of tampered or unsigned files in Ubuntu 24.04, Debian 13
  and Fedora containers.
- Docs: Linux README, RELEASING.md (setup, expiry, rotation, leaks), READMEs
  and the system requirements page.
…tories on

The README and website copy says the .deb and .rpm add the LokalBot
repository, which is only true once its key is committed. It moves to its
own pull request, merged with that key, so master never promises updates
the current packages can't give.
…ran-ac50b7

# Conflicts:
#	LinuxWindows/scripts/package-linux-distros.sh
#	RELEASING.md
@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Oct 20, 2026 •

Copy link
Copy Markdown

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Preview URL Updated (UTC)
✅ Deployment successful!
View logs
lokalbot 04a021d Commit Preview URL

Branch Preview URL
Oct 20 2026, 01:49 PM

…f upgrade

The release's own lokalbot package was always told to download and install
the next package. Once a .deb or .rpm has added LokalBot's repository
(/etc/apt/sources.list.d/lokalbot.sources, /etc/yum.repos.d/lokalbot.repo,
not turned off with Enabled: no or enabled=0), package::owner() marks it
as having a repository, so it routes to the package manager and is told
"sudo apt upgrade" or "sudo dnf upgrade". The Arch package, and a .deb or
.rpm from before the repository, keep the install command. The check reads
the shipped repository files in its tests and runs off the UI thread with
the package lookup.
@stevyhacker
stevyhacker marked this pull request as ready for review October 20, 2026 13:48
@stevyhacker
stevyhacker enabled auto-merge October 20, 2026 14:10
@stevyhacker
stevyhacker merged commit bb9cfcf into master Oct 20, 2026
26 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant