Repository navigation
Release 2.3.0 (fix stable version label) - #122
Merged
Merged
Conversation
…#121) Compile stable from its own tag, verify the tag matches NullifyPDF.py, and show Beta only for prereleases.
github-actions
Bot
added
type:docs
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
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.
Release 2.3.0 (re-release)
The first v2.3.0 stable was promoted from the beta.3 build and therefore showed
2.3.0-beta.3/ "AI Privacy Beta" in the About dialog. This PR brings the fix tomainso the stable release can be compiled from its own tag.vX.Y.Ztag; the workflow checks the CHANGELOG entry and thatNullifyPDF.pydeclares exactly that version with no prerelease suffix.[2.3.0]entry,[Unreleased]stays empty).After merge
Delete the v2.3.0 release and tag, then re-tag
v2.3.0on the newmainmerge commit to build and publish the stable release.