Open
Conversation
4276a84 to
1ed5b0f
Compare
80a7346 to
8cbca2c
Compare
8cbca2c to
9218dac
Compare
f82ad6c to
f194f92
Compare
f194f92 to
5e52c02
Compare
c3aa0f9 to
4e4961a
Compare
4e4961a to
26ad2f1
Compare
26ad2f1 to
8653539
Compare
8653539 to
311b94e
Compare
311b94e to
0287349
Compare
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.
This PR contains the following updates:
2.0.0→2.3.41.8.0→1.10.01.92.0→1.95.00.5.15→0.11.7Release Notes
python-poetry/poetry (poetry)
v2.3.4Compare Source
Fixed
v2.3.3Compare Source
Fixed
gitdependencies from annotated tags could not be updated (#10719).VIRTUAL_ENVorCONDA_PREFIXenvironment variables (e.g., afterconda deactivate) would cause Poetry to incorrectly detect an active virtualenv (#10784)..venvwas a file instead of a directory (#10777).poetry publish --no-interaction --buildrequested user interaction (#10769).poetry initandpoetry newcreated a deprecatedproject.licenseformat (#10787).Docs
poetry installandpoetry update(#10713).pyproject.tomlexamples (#10753).poetry cache clearexample (#10749).pipxinstallation instructions (#10783).poetry-core (
2.3.2)platform_releasecould not be parsed on Debian Trixie (#930).project.readme.textin thepyproject.tomlfile resulted in broken metadata (#914).include-groupentries were lost when[tool.poetry.group]also definedinclude-groupsfor the same group (#924).<value> not in <marker>constraints was wrongly treated as always satisfied (#925).>version constraint (#921).0was treated as equal to the corresponding public version (#920).!= <version>constraint wrongly disallowed pre releases and post releases of the specified version (#929).inandnot inconstraints were wrongly not allowed by specific compound constraints (#927).v2.3.2Compare Source
Changed
dulwich>=1.0(#10701).poetry-core (
2.3.1)platform_releasecould not be parsed on Windows Server (#911).v2.3.1Compare Source
Fixed
Docs
v2.3.0Compare Source
Added
pylock.tomlfiles withpoetry-plugin-export(#10677).requires-poetrybefore any other validation (#10593).project.readmewhen runningpoetry check(#10604).poetry cache clearoptional (#10627).--no-cachesolves an issue (#10585).poetry initwhen tryingpoetry newfor an existing directory (#10563).poetry publish --skip-existingfor new Nexus OSS versions (#10603).poetry debug info(#10588).Changed
installer.re-resolvefromtruetofalse(#10622).poetry.utils._compat.metadata, which is sometimes used in plugins, in favor ofimportlib.metadata(#10634).poetry python(#10606).poetry init, only add the readme field in thepyproject.tomlif the readme file exists (#10679).dulwich>=0.25.0(#10674).Fixed
poetry removedid not work for PEP 735 dependency groups withinclude-groupitems (#10587).poetry removecaused danglinginclude-groupreferences in PEP 735 dependency groups (#10590).poetry adddid not work for PEP 735 dependency groups withinclude-groupitems (#10636).poetry-plugin-export(#10667).poetry publishused the metadata of the project instead of the metadata of the build artifact (#10624).poetry env usejust used another Python version instead of failing when the requested version was not supported by the project (#10685).poetry env activatereturned the wrong command fordash(#10696).data-dirandpython.installation-dircould not be set (#10595).virtualenvs.promptcaused an incomprehensible error message (#10648).Docs
~/.netrcfor Poetry credential configuration (#10630).packagesare automatically detected (#10680).poetry-core (
2.3.0)python_full_versionmarkers with pre-release versions were parsed incorrectly (#893).v2.2.1Compare Source
Fixed
poetry self showfailed with a message about an invalid output format (#10560).Docs
poetry-core (
2.2.1)v2.2.0Compare Source
Added
--formatoption topoetry showto alternatively output json format (#10487).Changed
installer.no-binaryandinstaller.only-binaryso that explicit package names will take precedence over:all:(#10278).poetry installwhen a wheel is built from source (#10404).dulwich>=0.24.0(#10492).virtualenv>=20.33again (#10506).findpython>=0.7(#10510).importlib-metadata>=8.7(#10511).Fixed
poetry newdid not create the project structure in an existing empty directory (#10431).poetry-core (
2.2.0)[project.license](#870)..gitignorewere not included in the distribution (#874).v2.1.4Compare Source
Changed
virtualenv<20.33to work around an issue where Poetry uses the wrong Python version (#10491).pyproject.tomlfile (#10471).Fixed
poetry installwas called with--no-plugins(#10405).Docs
poetry addif no version constraint is explicitly specified (#10445).v2.1.3Compare Source
Changed
importlib-metadata<8.7for Python 3.9 because of a breaking change in importlib-metadata 8.7 (#10374).Fixed
--directoryoption did not work if a plugin, which accesses the poetry instance during its activation, was installed (#10352).poetry env activate -vprinted additional information to stdout instead of stderr so that the output could not be used as designed (#10353).poetry-core (
2.1.3)projectsection were treated as non-optional when a source was defined for them in thetool.poetrysection (#857).===were not parsed correctly (#860).extramarkers with a value starting with "in" were not validated correctly (#862).v2.1.2Compare Source
Changed
Fixed
poetry lockwas not deterministic (#10276).poetry env activatereturned the wrong command fortcsh(#10243).poetry env activatereturned the wrong command forpwshon Linux (#10256).Docs
poetry-core (
2.1.2)#846).
extramarkers were not simplified (#842,#845,
#847).
python_versionmarkers was not recognized as empty (#849).python_versionmarkers were not simplified (#848,#851).
v2.1.1Compare Source
Fixed
poetry env use pythondoes not choose the Python from the PATH (#10187).poetry-core (
2.1.1)python_versionmarker resulted in an invalid marker (#838).v2.1.0Compare Source
Added
buildcommand build-system agnostic (#10059,#10092).
--config-settingsoption topoetry build(#10059).config-settingswhen building dependencies (#10129).findpythonto find the Python interpreters (#10097).--no-truncateoption topoetry show(#9580).#10065,
#10126,
#10127,
#10132).
Changed
poetry newdefaults to "src" layout by default (#10135).#10114,
#10138,
#10146).
--priority(#10134).Fixed
#10067,
#10128).
poetry initwas not able to find a package on PyPI while adding dependencies interactively (#10055).@latestdescriptor was incorrectly passed to the core requirement parser (#10069).True(in contrast totrue) were interpreted asfalse(#10080).poetry env activatereported a misleading error message (#10087).poetry add --optionalwould not correctly update the lock file (#10076).pipwas not installed/updated before other dependencies resulting in a race condition (#10102).keyringsimultaneously (#10062).zipapp(#10074).Docs
envcommands (#10027).nameandversionfields are always required if theprojectsection is specified (#10033).project.gui-scripts#10121.#10133).
poetry-core (
2.1.0)__pycache__directory and*.pycfiles were included in sdists and wheels (#835).v2.0.1Compare Source
Added
poetry searchin legacy sources (#9949).poetry source showoutput when PyPI is implicitly enabled (#9974).Changed
Fixed
poetry syncdid not remove packages that were not requested (#9946).poetry checkfailed even though there were just warnings and add a--strictoption to fail on warnings (#9983).poetry update,poetry addandpoetry removewith--onlyuninstalled packages from other groups (#10014).poetry update,poetry addandpoetry removeuninstalled all extra packages (#10016).poetry self updatedid not recognize Poetry's own environment (#9995).poetry installstarted withWarning:instead ofError:(#9945).Command.set_poetry, which is used by plugins, was removed (#9981).poetry build --cleanshowed a malformed short option instead of the description (#9994).Docs
projectsection (#9996).project.readmeandproject.urls(#9948).poetry install --syncwithpoetry syncin the section about synchronizing dependencies (#9944).poetry shellwithpoetry env activatein the basic usage section (#9963).project.nameis always required when theprojectsection is used (#9989).poetry-plugin-exportin the section aboutpoetry export(#9954).poetry-core (
2.0.1)Home-pagewithProject-URL: Homepage(#807).tool.poetry.packageswithout a specifiedformatwere not initialized with the default value resulting in aKeyError(#805).project.urlsentries were not processed correctly resulting in aKeyError(#807).project.dependenciesviatool.poetry.dependencieswere ignored ifproject.optional-dependencieswere defined (#811).python-poetry/poetry-plugin-export (poetry-plugin-export)
v1.10.0Compare Source
Added
pylock.tomlfiles (#357).Changed
Fixed
"dependency walk failed"error message gave an outdated advice (#353).v1.9.0Compare Source
Added
--all-groupsoption to export dependencies from all groups (#294).Changed
--withand--onlyand deprecate--without(#212).poetry.lockfile is not consistent with thepyproject.tomlfile (#310).Fixed
"dependency walk failed".This fix requires a
poetry.lockfile created with Poetry 2.x (#286).pre-commithook regex matched wrong files (#285).rust-lang/rust (rust-lang/rust)
v1.95.0Compare Source
===========================
Language
if letguards on match armsirrefutable_let_patternslint no longer lints on let chainsCompiler
--remap-path-scopefor controlling the scoping of how paths get remapped in the resulting binaryPlatform Support
powerpc64-unknown-linux-muslto Tier 2 with host toolsaarch64-apple-tvosto Tier 2aarch64-apple-tvos-simto Tier 2aarch64-apple-watchosto Tier 2aarch64-apple-watchos-simto Tier 2aarch64-apple-visionosto Tier 2aarch64-apple-visionos-simto Tier 2Refer to Rust's platform support page
for more information on Rust's tiered platform support.
Libraries
thread::scope: document how join interacts with TLS destructorsstr::containson aarch64 targets withneontarget feature enabled by defaultStabilized APIs
MaybeUninit<[T; N]>: From<[MaybeUninit<T>; N]>MaybeUninit<[T; N]>: AsRef<[MaybeUninit<T>; N]>MaybeUninit<[T; N]>: AsRef<[MaybeUninit<T>]>MaybeUninit<[T; N]>: AsMut<[MaybeUninit<T>; N]>MaybeUninit<[T; N]>: AsMut<[MaybeUninit<T>]>[MaybeUninit<T>; N]: From<MaybeUninit<[T; N]>>Cell<[T; N]>: AsRef<[Cell<T>; N]>Cell<[T; N]>: AsRef<[Cell<T>]>Cell<[T]>: AsRef<[Cell<T>]>bool: TryFrom<{integer}>AtomicPtr::updateAtomicPtr::try_updateAtomicBool::updateAtomicBool::try_updateAtomicIn::updateAtomicIn::try_updateAtomicUn::updateAtomicUn::try_updatecfg_select!mod core::rangecore::range::RangeInclusivecore::range::RangeInclusiveItercore::hint::cold_path<*const T>::as_ref_unchecked<*mut T>::as_ref_unchecked<*mut T>::as_mut_uncheckedVec::push_mutVec::insert_mutVecDeque::push_front_mutVecDeque::push_back_mutVecDeque::insert_mutLinkedList::push_front_mutLinkedList::push_back_mutLayout::dangling_ptrLayout::repeatLayout::repeat_packedLayout::extend_packedThese previously stable APIs are now stable in const contexts:
fmt::from_fnControlFlow::is_breakControlFlow::is_continueRustdoc
Compatibility Notes
$cratewithout renaming, i.e.use $crate::{self};, is now no longer permitted due to stricter error checking forselfimports.In very rare cases, this may cause compilation errors due to bytes from parts of a pointer ending up in the padding bytes of a
constorstatic.ambiguous_glob_imported_traitsis now reported when using an ambiguously glob imported traitEq::assert_receiver_is_total_eqand emit future compatibility warnings on manual impls#[non_exhaustive]enum now reads the discriminant, even if the enum has only one variant. This can cause closures to capture values that they previously wouldn't.mut refandmut ref mutpatterns, part of the unstable Match Ergonomics 2024 RFC, were accidentally allowed on stable within struct pattern field shorthand. These patterns are now correctly feature-gated as unstable in this position.-Z unstable-optionsto use. Previously, they could not be used without the standard library, which has no stable build mechanism. In preparation for thebuild-stdproject adding that support, JSON target specs are being proactively gated to ensure they remain unstable even ifbuild-stdis stabilized. Cargo now includes the-Z json-target-specCLI flag to automatically pass-Z unstable-optionsto the compiler when needed. See #150151, #151534, and rust-lang/cargo#16557.#[feature]attributes on invalid targets are now checkedInternal Changes
These changes do not affect any public interfaces of Rust, but they represent
significant improvements to the performance or internals of rustc and related
tools.
v1.94.1Compare Source
===========================
std::thread::spawnon wasm32-wasip1-threadsstd::os::windows::fs::OpenOptionsExtThe new methods were unstable, but the trait itself is not sealed and so
cannot be extended with non-default methods.
match_same_armsThis resolves CVE-2026-33055 and CVE-2026-33056. Users of crates.io are not affected.
See blog for more details.
v1.94.0Compare Source
==========================
Language
dead_codelint level of the corresponding traits and trait itemsunused_visibilitieslint for visibility onconst _declarationsPlatform Support
riscv64im-unknown-none-elfas a tier 3 targetRefer to Rust's platform support page
for more information on Rust's tiered platform support.
Libraries
T: Ordbound for someBinaryHeap<T>methods.Stabilized APIs
<[T]>::array_windows<[T]>::element_offsetLazyCell::getLazyCell::get_mutLazyCell::force_mutLazyLock::getLazyLock::get_mutLazyLock::force_mutimpl TryFrom<char> for usizestd::iter::Peekable::next_if_mapstd::iter::Peekable::next_if_map_mutavx512fp16intrinsics(excluding those that depend directly on the unstable
f16type)(excluding those that depend directly on the unstable
f16type)f32::consts::EULER_GAMMAf64::consts::EULER_GAMMAf32::consts::GOLDEN_RATIOf64::consts::GOLDEN_RATIOThese previously stable APIs are now stable in const contexts:
f32::mul_addf64::mul_addCargo