Skip to content

1.0.0-rc.5 - #40

Merged
sean-e-dietrich merged 4 commits into
mainfrom
release/1.0.0-rc.5
Sep 30, 2026
Merged

sean-e-dietrich merged 4 commits into
mainfrom
release/1.0.0-rc.5

Conversation

@sean-e-dietrich

@sean-e-dietrich sean-e-dietrich commented Sep 30, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Prepares 1.0.0-rc.5, published as a GitHub pre-release once this merges and the tag is pushed.

After merge

git tag -a 1.0.0-rc.5 -m 1.0.0-rc.5 <merge-commit> && git push origin 1.0.0-rc.5

Testing

  • build/check-versions.sh --release 1.0.0-rc.5: all agree

  • build/release-notes.sh 1.0.0-rc.5: extracts the section

  • Unit tests (267)

  • build/build-zip.sh: produces basic-firewall-1.0.0-rc.5.zip, scope check OK

  • Was AI used in this pull request?

Every stated version says 1.0.0-rc.5. [Unreleased] becomes [1.0.0-rc.5]
-- the early-path diagnostics and fail-open logging from #39 -- with a
release-candidate lead and a fresh [Unreleased] above it, and readme.txt's
changelog gets a matching entry.
main merged cleanly; everything since rc.4 now sits under [1.0.0-rc.5]. The
release-candidate lead and readme.txt's entry described #39 alone, so both
now cover the diagnostics additions, the secrets work and the autoloader
order as well.
#58 merged first, so rc.5 now ships kanopi/firewall 2.35.1 as well. Only
CHANGELOG.md conflicted: the rc.5 heading and lead against #58's new
"What changes on upgrade" section. The heading comes first, the upgrade
section follows it, and the lead and readme.txt entry now mention 2.35.1
and its behaviour changes.
@sean-e-dietrich
sean-e-dietrich merged commit cf6a38e into main Sep 30, 2026
14 checks passed
@sean-e-dietrich
sean-e-dietrich deleted the release/1.0.0-rc.5 branch September 30, 2026 21:24
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