Release 2.0.7: Python 3.13 migration + beta/stable CI pipeline - #88
Merged
Conversation
…without rebuild - new beta-release.yml builds on v*-beta.* tags and publishes a prerelease - release.yml no longer rebuilds: it downloads the latest beta's tested artifacts and republishes them as the stable release - fix mypy step using 'head' under pwsh on windows-latest (was silently no-op due to || true) - add concurrency groups and fail-fast: false to the build matrices
Bump the required Python runtime from 3.12 to 3.13. PyMuPDF 1.28.0 publishes abi3 wheels (cp310-abi3) that are forward-compatible with Python 3.13, removing the previous compatibility constraint. - Update requirements.txt comments to reflect Python 3.13 support - Update CI/CD workflows (test_build.yml, beta-release.yml) to build with Python 3.13 - Update all documentation (README, DEVELOPMENT, ARCHITECTURE, CONTRIBUTING, TROUBLESHOOTING, USER_GUIDE, GUIDA_UTENTE) and setup_env.py - Version bumped to 2.0.7 in NullifyPDF.py - Release notes added to CHANGELOG.md Verified in an isolated environment (separate worktree/venv, Python 3.13.13): - pip install -r requirements.txt: no dependency conflicts - pytest tests/: 11/11 passed - mypy: 16 pre-existing warnings, no regressions - Full PyInstaller build: NullifyPDF_v2.0.7_Windows.exe generated successfully - presidio-analyzer PII detection pipeline: functional
- build_local.py appends the beta suffix (from NULLIFYPDF_BETA_SUFFIX) to output artifact filenames, keeping package metadata (RPM/DEB Version) on the base version - beta-release.yml derives the suffix from the beta tag (e.g. v2.0.7-beta.3 -> beta.3) before building - release.yml strips the beta suffix from downloaded filenames before republishing as stable, so stable naming stays unchanged
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.
Summary
NullifyPDF_v2.0.7-beta.3_Windows.exe); the stable promote workflow strips that suffix before republishing, so stable naming is unchangedTest plan
v2.0.7-beta.Ntag from develop, confirm beta prerelease assets are named with the beta suffixv2.0.7tag from main, confirm the promoted stable release has clean filenames (no beta suffix)