search

franc-pentest / ldeep

In-depth ldap enumeration utility
MIT License
415 stars 45 forks source link

Bump pex from 2.0.3 to 2.3.1 #75

Closed dependabot[bot] closed 5 months ago

dependabot[bot] commented 5 months ago

Bumps pex from 2.0.3 to 2.3.1.

Release notes

Sourced from pex's releases.

pex 2.3.1

2.3.1

This release fixes Pex to respect lock file interpreter constraints and target systems when downloading artifacts.

  • Fix lock downloads to use all lock info. (#2396)

pex 2.3.0

2.3.0

This release introduces pex3 lock sync as a higher-level tool that can be used to create and maintain a lock as opposed to using a combination of pex3 lock create and pex3 lock update. When there is no existing lock file, pex3 lock sync --lock lock.json ... is equivalent to pex3 lock create --output lock.json ..., it creates a new lock. On subsequent uses however, pex3 lock sync --lock lock.json ... updates the lock file minimally to meet any changed requirements or other changed lock settings.

This release also fixes pex --no-build --lock ... to work with lock files also created with --no-build. The known case here is a --style universal lock created with --no-build to achieve a wheel-only universal lock.

This release includes a fix to clarify the conditions under which --requierements-pex can be used to combine the third party dependencies from a pre-built PEX into a new PEX; namely, that the PEXes must use the same value for the --pre-install-wheels option.

Finally, this release fixes pex3 venv to handle venvs created by Virtualenv on systems that distinguish purelib and platlib site-packages directories. Red Hat distributions are a notable example of this.

  • Implement pex3 lock sync. (#2373)
  • Guard against mismatched --requirements-pex. (#2392)
  • Fix pex --no-build --lock .... (#2390)
  • Fix Pex to handle venvs with multiple site-packages dirs. (#2383)

pex 2.2.2

2.2.2

This release fixes pex3 lock create to handle .tar.bz2 and .tgz

... (truncated)

Changelog

Sourced from pex's changelog.

2.3.1

This release fixes Pex to respect lock file interpreter constraints and target systems when downloading artifacts.

  • Fix lock downloads to use all lock info. (#2396)

2.3.0

This release introduces pex3 lock sync as a higher-level tool that can be used to create and maintain a lock as opposed to using a combination of pex3 lock create and pex3 lock update. When there is no existing lock file, pex3 lock sync --lock lock.json ... is equivalent to pex3 lock create --output lock.json ..., it creates a new lock. On subsequent uses however, pex3 lock sync --lock lock.json ... updates the lock file minimally to meet any changed requirements or other changed lock settings.

This release also fixes pex --no-build --lock ... to work with lock files also created with --no-build. The known case here is a --style universal lock created with --no-build to achieve a wheel-only universal lock.

This release includes a fix to clarify the conditions under which --requierements-pex can be used to combine the third party dependencies from a pre-built PEX into a new PEX; namely, that the PEXes must use the same value for the --pre-install-wheels option.

Finally, this release fixes pex3 venv to handle venvs created by Virtualenv on systems that distinguish purelib and platlib site-packages directories. Red Hat distributions are a notable example of this.

  • Implement pex3 lock sync. (#2373)
  • Guard against mismatched --requirements-pex. (#2392)
  • Fix pex --no-build --lock .... (#2390)
  • Fix Pex to handle venvs with multiple site-packages dirs. (#2383)

2.2.2

This release fixes pex3 lock create to handle .tar.bz2 and .tgz sdists in addition to the officially sanctioned .tar.gz and (less officially so) .zip sdists.

  • Handle .tar.bz2 & .tgz sdists when locking. (#2380)

2.2.1

This release trims down the size of the Pex wheel on PyPI and the released Pex PEX by about 20KB by consolidating image resources.

... (truncated)

Commits


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)