search

KiraLT / certbot-lambda

Run Certbot on AWS Lambda/Cloud Functions and upload certs to AWS Secrets Manager.
MIT License
16 stars 8 forks source link

chore(deps-dev): bump pex from 2.1.119 to 2.1.125 #162

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Bumps pex from 2.1.119 to 2.1.125.

Release notes

Sourced from pex's releases.

pex 2.1.125

2.1.125

This release makes --platform and --complete-platform resolves and locks as permissive as possible. If such a resolve or lock only has an sdist available for a certain project, that sdist will now be used if it builds to a wheel compatible with the specified foreign platform(s).

  • Attempt "cross-builds" of sdists for foreign platforms. (#2075)

pex 2.1.124

2.1.124

This release adds support for specifying --non-hermetic-venv-scripts when building a --venv PEX. This can be useful when integrating with frameworks that do setup via PYTHONPATH manipulation.

Support for Pip 23.0.1 and setuptools 67.4.0 is added via --pip-version 23.0.1.

Additionally, more work towards hardening Pex against rare concurrency issues in its atomic directory handling is included.

  • Introduce --non-hermetic-venv-scripts. (#2068)
  • Wrap inter-process locks in in-process locks. (#2070)
  • Add support for Pip 23.0.1. (#2072)

pex 2.1.123

2.1.123

This release fixes a few pex3 lock create bugs.

There was a regression introduced in Pex 2.1.122 where projects that used a PEP-518 [build-system] requires but specified no corresponding build-backend would fail to lock.

There were also two long standing issues handling more exotic direct reference URL requirements. Source archives with names not following the standard Python sdist naming scheme of <project name>-<version>.{zip,tar.gz} would cause a lock error. An important class of these is provided by GitHub's magic source archive download URLs. Also, although local projects addressed with Pip proprietary support for pure local path requirements would lock, the same local projects addressed via

... (truncated)

Changelog

Sourced from pex's changelog.

2.1.125

This release makes --platform and --complete-platform resolves and locks as permissive as possible. If such a resolve or lock only has an sdist available for a certain project, that sdist will now be used if it builds to a wheel compatible with the specified foreign platform(s).

  • Attempt "cross-builds" of sdists for foreign platforms. (#2075) PR [#2075](https://github.com/pantsbuild/pex/issues/2075) <https://github.com/pantsbuild/pex/pull/2075>_

2.1.124

This release adds support for specifying --non-hermetic-venv-scripts when building a --venv PEX. This can be useful when integrating with frameworks that do setup via PYTHONPATH manipulation.

Support for Pip 23.0.1 and setuptools 67.4.0 is added via --pip-version 23.0.1.

Additionally, more work towards hardening Pex against rare concurrency issues in its atomic directory handling is included.

  • Introduce --non-hermetic-venv-scripts. (#2068) PR [#2068](https://github.com/pantsbuild/pex/issues/2068) <https://github.com/pantsbuild/pex/pull/2068>_

  • Wrap inter-process locks in in-process locks. (#2070) PR [#2070](https://github.com/pantsbuild/pex/issues/2070) <https://github.com/pantsbuild/pex/pull/2070>_

  • Add support for Pip 23.0.1. (#2072) PR [#2072](https://github.com/pantsbuild/pex/issues/2072) <https://github.com/pantsbuild/pex/pull/2072>_

2.1.123

This release fixes a few pex3 lock create bugs.

There was a regression introduced in Pex 2.1.122 where projects that used a PEP-518 [build-system] requires but specified no corresponding build-backend would fail to lock.

There were also two long standing issues handling more exotic direct reference URL requirements. Source archives with names not following the standard Python sdist naming scheme of <project name>-<version>.{zip,tar.gz} would cause a lock error. An important class of these is provided by GitHub's magic source archive download URLs. Also, although local projects addressed with Pip proprietary support for pure local path requirements would lock, the same local projects addressed via

... (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 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)
codecov[bot] commented 1 year ago

Codecov Report

Merging #162 (44f5812) into main (24397ba) will not change coverage. The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #162   +/-   ##
=======================================
  Coverage   89.81%   89.81%           
=======================================
  Files           5        5           
  Lines         108      108           
=======================================
  Hits           97       97           
  Misses         11       11

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

dependabot[bot] commented 1 year ago

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.