fr34akyandJohnathan Corgan 66c9638632 ci: publish the pfSense packages as release assets ...

The pfSense packages were kept out of releases by design, as workflow
artifacts, until one had been installed on a real pfSense box. That bar
has been met on the two supported Plus bases: install, boot script
lifecycle, log rotation, DNS through unbound, the package reload path,
reboot, teardown and removal on Plus 26.03.1 and 26.07 in Netgate-installed
VMs, and mesh traffic between the two over the TUN interface under pf;
the README's test record has the details.

The release job now needs the pfsense job as well as build, downloads
its artifact next to the FreeBSD one, and requires all three packages
before publishing instead of failing if a pfSense package is present.
Their checksums join checksums-freebsd.txt and the upload glob already
covers them. A pfSense build failure therefore holds a release the way
a FreeBSD build failure does, which is what a release asset means; on
every other ref the pfsense job's output stays a 30-day artifact.

Not covered by the evidence: physical appliances and CE 2.9.0.

2026-09-18 13:14:02 +00:00

..

scripts

Pin every GitHub Action to a commit SHA, and verify the nak download

2026-08-11 15:44:07 +00:00

workflows

ci: publish the pfSense packages as release assets

2026-09-18 13:14:02 +00:00