Sourced from pyo3's releases.
PyO3 0.23.3
This release is a soundness fix for PyO3 0.23.0 through 0.23.2.
In PyO3 0.23.0 the
PYO3_CONFIG_FILE
environment variable used to configure builds regressed such that changing the environment variable would no longer trigger PyO3 to reconfigure and recompile. In combination with workflows using tools such asmaturin
to build for multiple versions in a single build, this leads to Python wheels being compiled against the wrong Python API version.All users who distribute artefacts for multiple Python versions are encouraged to update and rebuild with PyO3 0.23.3. Affected wheels produced from PyO3 0.23.0 through 0.23.2 are highly unstable and will crash the Python interpreter in unpredictable ways.
Aside from this fix, PyO3 0.23.3 contains some fixes to link configuration for Python 3.13t on Windows.
Thank you to the following contributors for the improvements:
Sourced from pyo3's changelog.
[0.23.3] - 2024-12-03
Packaging
- Bump optional
python3-dll-a
dependency to 0.2.11. #4749Fixed
- Fix unresolved symbol link failures on Windows when compiling for Python 3.13t with
abi3
features enabled. #4733- Fix unresolved symbol link failures on Windows when compiling for Python 3.13t using the
generate-import-lib
feature. #4749- Fix compile-time regression in PyO3 0.23.0 where changing
PYO3_CONFIG_FILE
would not reconfigure PyO3 for the new interpreter. #4758
b5599dc
release: 0.23.3a423c79
fix PYO3_CONFIG_FILE
env var not requesting rebuilds (#4758)9c862e5
fix another unsafe_op_in_unsafe_fn
trigger (#4753)5c681ca
support python3-dll-a free-threaded generation (#4749)3cb0b87
ci: test debug builds using 3.13.0 (#4750)9714eab
don't link to abi3 dll on windows for free-threaded build (#4733)a752425
add missing CHANGELOG entry for 4589 (#4744)d3f79cf
ci: updates for Rust 1.83 (#4741)42bd0e5
Update class.md (#4739)824ba56
fix clippy beta (#4737)Sourced from clap's releases.
v4.5.23
[4.5.23] - 2024-12-05
Fixes
- (parser) When check
allow_negative_numbers
, allowE
againv4.5.22
[4.5.22] - 2024-12-03
Fixes
- (assert) Catch bugs with arguments requiring themself
Sourced from clap's changelog.
[4.5.23] - 2024-12-05
Fixes
- (parser) When check
allow_negative_numbers
, allowE
again[4.5.22] - 2024-12-03
Fixes
- (assert) Catch bugs with arguments requiring themself
7916028
chore: Release804498d
docs: Update changelogf9721f1
Merge pull request #5695
from epage/valueb04bf72
fix(complete)!: Be consistent in value language0e28259
chore: Releasee55c986
docs: Update changelogc7157df
Merge pull request #5692
from epage/self84252b7
fix(complete): Allow completing '.'eded64a
test(complete): Verify PathCompleter::dirSourced from pest's releases.
v2.7.15
What's Changed
- Band-Aid: fix one of the left recursion bugs (fixes #1047) by
@Tartasprint
in pest-parser/pest#1048- Update
thiserror
to version 2 by@MarkusPettersson98
in pest-parser/pest#1055New Contributors
@MarkusPettersson98
made their first contribution in pest-parser/pest#1055Full Changelog: https://github.com/pest-parser/pest/compare/v2.7.14...v2.7.15
Warning: Semantic Versioning
Note that the node tag feature in 2.6.0 was a technically semver-breaking change even though it is a backwards-compatible / non-breaking change in the meta-grammar. There may be similar non-breaking changes to the meta-grammar between minor versions in the future. These non-breaking changes, however, may translate into semver-breaking changes due to the additional variants propagated from the generated
Rule
enum.This new feature caused issues in some Cargo version resolution situations where Cargo mixed different versions of pest dependencies. For this reason, these "grammar non-breaking but semver-breaking" changes are now available only under the "grammar-extras" feature flag. If you would like to use node tags (or other future grammar features), you can do so by enabling this flag on the pest_derive crate in your Cargo.toml:
... pest_derive = { version = "2.7", features = ["grammar-extras"] }
Sourced from pest_derive's releases.
v2.7.15
What's Changed
- Band-Aid: fix one of the left recursion bugs (fixes #1047) by
@Tartasprint
in pest-parser/pest#1048- Update
thiserror
to version 2 by@MarkusPettersson98
in pest-parser/pest#1055New Contributors
@MarkusPettersson98
made their first contribution in pest-parser/pest#1055Full Changelog: https://github.com/pest-parser/pest/compare/v2.7.14...v2.7.15
Warning: Semantic Versioning
Note that the node tag feature in 2.6.0 was a technically semver-breaking change even though it is a backwards-compatible / non-breaking change in the meta-grammar. There may be similar non-breaking changes to the meta-grammar between minor versions in the future. These non-breaking changes, however, may translate into semver-breaking changes due to the additional variants propagated from the generated
Rule
enum.This new feature caused issues in some Cargo version resolution situations where Cargo mixed different versions of pest dependencies. For this reason, these "grammar non-breaking but semver-breaking" changes are now available only under the "grammar-extras" feature flag. If you would like to use node tags (or other future grammar features), you can do so by enabling this flag on the pest_derive crate in your Cargo.toml:
... pest_derive = { version = "2.7", features = ["grammar-extras"] }