halo: 2.20.12 -> 2.20.13

[r-ryantm]

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/halo-dev/halo/releases.

meta.description for halo is: Self-hosted dynamic blogging program

meta.homepage for halo is: https://www.halo.run

Updates performed

• Version update

To inspect upstream changes

• Release on GitHub

• Compare changes on GitHub

Impact

Checks done

---

• built on NixOS
• The tests defined in passthru.tests, if any, passed
• found 2.20.13 with grep in /nix/store/phbfm7cgrjdchmxar6nwinmngybx9w2r-halo-2.20.13
• found 2.20.13 in filename of file in /nix/store/phbfm7cgrjdchmxar6nwinmngybx9w2r-halo-2.20.13

---

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

halo

Instructions to test this update (click to expand)

---

Either download from the cache:

nix-store -r /nix/store/phbfm7cgrjdchmxar6nwinmngybx9w2r-halo-2.20.13 \
  --option binary-caches 'https://cache.nixos.org/ https://nixpkgs-update-cache.nix-community.org/' \
  --option trusted-public-keys '
  nixpkgs-update-cache.nix-community.org-1:U8d6wiQecHUPJFSqHN9GSSmNkmdiFW7GW7WNAnHW0SM=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The nixpkgs-update cache is only trusted for this store-path realization.)
For the cached download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.

Or, build yourself:

nix-build -A halo https://github.com/r-ryantm/nixpkgs/archive/2c954c74fd145e310df078479f69d5901217e145.tar.gz

Or:

nix build github:r-ryantm/nixpkgs/2c954c74fd145e310df078479f69d5901217e145#halo

After you've downloaded or built it, look at the files and if there are any, run the binaries:

ls -la /nix/store/phbfm7cgrjdchmxar6nwinmngybx9w2r-halo-2.20.13
ls -la /nix/store/phbfm7cgrjdchmxar6nwinmngybx9w2r-halo-2.20.13/bin

---

Pre-merge build results

We have automatically built all packages that will get rebuilt due to
this change.

This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.

nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review

---

x86_64-linux

✅ 1 package built:

• halo

---

Maintainer pings

cc @wangxiaoerYah for testing.

Tip

As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

---

Add a 👍 reaction to pull requests you find important.

[nixpkgs-ci]

Backport failed for release-24.11, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin release-24.11
git worktree add -d .worktree/backport-370594-to-release-24.11 origin/release-24.11
cd .worktree/backport-370594-to-release-24.11
git switch --create backport-370594-to-release-24.11
git cherry-pick -x 2c954c74fd145e310df078479f69d5901217e145

[nixpkgs-ci]

Backport failed for release-24.11, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin release-24.11
git worktree add -d .worktree/backport-370594-to-release-24.11 origin/release-24.11
cd .worktree/backport-370594-to-release-24.11
git switch --create backport-370594-to-release-24.11
git cherry-pick -x 2c954c74fd145e310df078479f69d5901217e145

[nixpkgs-ci]

Backport failed for release-24.11, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin release-24.11
git worktree add -d .worktree/backport-370594-to-release-24.11 origin/release-24.11
cd .worktree/backport-370594-to-release-24.11
git switch --create backport-370594-to-release-24.11
git cherry-pick -x 2c954c74fd145e310df078479f69d5901217e145

[LeSuisse]

Backport in #371151