From 37859554f43a3344062a21a6e7df57329e58612d Mon Sep 17 00:00:00 2001 From: npond Date: Sun, 30 Aug 2026 10:15:33 -0400 Subject: [PATCH] Release 0.1.4: README latest version, and SECURITY.md supported versions The supported-versions section still said n8PDF had not had a numbered public release and that fixes land on main until one happens. Releases began with 0.1.0 and #61 is closed, so it now says what actually holds: a fix lands on main and ships in the next release cut from it, and while the project is pre-1.0 the latest release is the only supported line. The table no longer names a version, so it does not go stale each time. --- README.md | 2 +- SECURITY.md | 12 ++++++------ 2 files changed, 7 insertions(+), 7 deletions(-) diff --git a/README.md b/README.md index 10096f3..f90d947 100644 --- a/README.md +++ b/README.md @@ -28,7 +28,7 @@ cannot tell from Word's own export — and it gets close. ## Installation -`n8PDF` is on [NuGet](https://www.nuget.org/packages/n8PDF) — latest **0.1.3**: +`n8PDF` is on [NuGet](https://www.nuget.org/packages/n8PDF) — latest **0.1.4**: ```bash dotnet add package n8PDF diff --git a/SECURITY.md b/SECURITY.md index 9e2b713..f11f97a 100644 --- a/SECURITY.md +++ b/SECURITY.md @@ -58,15 +58,15 @@ no bug-bounty programme. ## Supported versions -n8PDF has not yet had a numbered public release (see -[#61](https://github.com/nathanpond/n8PDF/issues/61)). Until it does, security fixes land on -`main`. Once releases begin, this table states which lines receive them: +Releases began with `0.1.0` ([#61](https://github.com/nathanpond/n8PDF/issues/61)). A security fix +lands on `main` and ships in the next release cut from it; while the project is pre-1.0 there is a +single supported line — the latest release — and fixes are not backported to earlier ones. | Version | Supported | |---|---| -| `main` (unreleased) | ✅ | -| latest released minor (once releases begin) | ✅ | -| older releases | ❌ — upgrade to the latest minor | +| `main` | ✅ | +| latest release | ✅ | +| older releases | ❌ — upgrade to the latest | ## Hardening a deployment