You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+44
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,47 @@
1
+
3000.0.0 (2024-06-06)
2
+
=====================
3
+
Pipenv 3000.0.0 (2024-06-06)
4
+
============================
5
+
6
+
7
+
Features & Improvements
8
+
-----------------------
9
+
10
+
- Supply any ``--extra-pip-args`` also in the resolver steps. `#6006 <https://github.com/pypa/pipenv/issues/6006>`_
11
+
- The ``uninstall`` command now does the inverse of ``upgrade`` which means it no longer invokes a full ``lock`` cycle which was problematic for projects with many dependencies. `#6029 <https://github.com/pypa/pipenv/issues/6029>`_
12
+
- The ``pipenv requirements`` subcommand now supports the ``--from-pipfile`` flag. When this flag is used, the requirements file will only include the packages explicitly listed in the Pipfile, excluding any sub-packages. `#6156 <https://github.com/pypa/pipenv/issues/6156>`_
13
+
14
+
Behavior Changes
15
+
----------------
16
+
17
+
-``pipenv==3000.0.0`` denotes the first major release of our semver strategy.
18
+
As much requested, the ``install`` no longer does a complete lock operation. Instead ``install`` follows the same code path as pipenv update (which is upgrade + sync).
19
+
This is what most new users expect the behavior to be; it is a behavioral change, a necessary one to make the tool more usable.
20
+
Remember that complete lock resolution can be invoked with ``pipenv lock`` just as before. `#6098 <https://github.com/pypa/pipenv/issues/6098>`_
21
+
22
+
Bug Fixes
23
+
---------
24
+
25
+
- Fix a bug that passes pipenv check command if Pipfile.lock not exist `#6126 <https://github.com/pypa/pipenv/issues/6126>`_
26
+
- Fix a bug that vcs subdependencies were locked without their subdirectory fragment if they had one `#6136 <https://github.com/pypa/pipenv/issues/6136>`_
27
+
-``pipenv`` converts off ``pkg_resources`` API usages. This necessitated also vendoring in:
28
+
* latest ``pipdeptree==2.18.1`` which also converted off ``pkg_resources``
29
+
*``importlib-metadata==7.1.0`` to continue supporting python 3.8 and 3.9
30
+
*``packaging==24.0`` since the packaging we were utilizing in pip's _vendor was insufficient for this conversion. `#6139 <https://github.com/pypa/pipenv/issues/6139>`_
31
+
- Pipenv only supports absolute python version. If the user specifies a Python version with inequality signs like >=3.12, <3.12 in the [requires] field, the code has been modified to explicitly express in an error log that absolute versioning must be used. `#6164 <https://github.com/pypa/pipenv/issues/6164>`_
32
+
33
+
Vendored Libraries
34
+
------------------
35
+
36
+
- Vendor in ``pip==24.0```#6117 <https://github.com/pypa/pipenv/issues/6117>`_
0 commit comments