release: v0.4.0#83
Merged
Merged
Conversation
Bump version 0.3.0 -> 0.4.0 (single-sourced from Cargo.toml) and finalize the CHANGELOG. v0.3.0 was the PyO3 0.16.6 release; this is the first release of the modernized parser (PyO3 0.29, security fixes, 3.11–3.14 support). Note: includes breaking changes — drops Python 3.7–3.10, str input is now lossless UTF-8, and undecodable bodies raise ParseError. Signed-off-by: yuriyryabikov <22548029+kurok@users.noreply.github.com>
kurok
added a commit
that referenced
this pull request
Jun 12, 2026
Fix every ruff finding on master — import ordering (I001), typing modernization to builtin generics and X|Y unions (UP006/UP007), redundant open mode (UP015), and a long line (E501) — across the package and tests. The public stub now uses list/dict/str|bytes; mypy --strict still passes. Flip the CI ruff step from advisory to blocking (config in ruff.toml) and add `ruff check --fix` to CONTRIBUTING. Also sync Cargo.lock to 0.4.0 (left stale by the version bump in #83). Signed-off-by: yuriyryabikov <22548029+kurok@users.noreply.github.com>
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.
Release prep for v0.4.0 — the first release of the modernized parser. (
v0.3.0was the PyO3 0.16.6 release; the 27 commits since then have been unreleased under a stale version number.)Cargo.toml: version0.3.0→0.4.0(single source; maturin/pyproject read it dynamically — build confirmed it resolves to0.4.0).CHANGELOG.md: finalized the[0.4.0]section (the previous draft mislabeled this work as[0.3.0]).strinput decoded as lossless UTF-8 (was truncating code points).ParseError(were silently empty).Release mechanics (after this merges)
Publishing is triggered by creating a GitHub Release (
publish.yml→ builds wheels → publishes to PyPI via OIDC Trusted Publishing). This requires the PyPI Trusted Publisher to be configured fornamecheap/fast_mail_parser+publish.yml.workflow_dispatchcan build the wheels without publishing as a dry-run.Deferred to a future 0.5.0 (breaking, by decision): #22, #23, #25.