Release 0.1.4: README version, and correct SECURITY.md supported versions - #298
Merged
Merged
Conversation
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Prepares the 0.1.4 tag, which ships the fix from #296 / #297 (an
FDICTzlib stream escaping the image decoders asZLibExceptionand aborting the whole conversion). NuGet's 0.1.3 still has that hole.latest **0.1.3**→0.1.4, as README: bump latest version to 0.1.3 #295 did for the last one.main". That has been false since 0.1.0 and Publish to NuGet: the release pipeline exists but has never run and has no API key #61 closed, and it is the policy document governing exactly this situation: a security fix being released. It now says what holds — a fix lands onmainand ships in the next release cut from it, and pre-1.0 the latest release is the only supported line, with no backports. The table no longer names a version, so it will not go stale at each release.No code changes; the release workflow takes the version from the tag, not from the csproj.
🤖 Generated with Claude Code
https://claude.ai/code/session_01W69hdtqDC6ewHMXnZdAysZ