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.102 to 2.1.117 #97

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Bumps pex from 2.1.102 to 2.1.117.

Release notes

Sourced from pex's releases.

pex 2.1.117


2.1.117

This release fixes a bug introduced in Pex 2.1.109 where the released Pex PEX could not be executed by PyPy interpreters. More generally, any PEX created with interpreter constraints that did not specify the Python implementation, e.g.: ==3.8.*, were interpreted as being CPython specific, i.e.: CPython==3.8.*. This is now fixed, but if the intention of a constraint like ==3.8.* was in fact to restrict to CPython only, interpreter constraints need to say so now and use CPython==3.8.* explicitly.

  • Fix interpreter constraint parsing. (#1998)

pex 2.1.116


2.1.116

This release fixes a bug in --resolve-local-platforms when --complete-platform was used.

  • Check for --complete-platforms match when --resolve-local-platforms (#1991)

pex 2.1.115


2.1.115

This release brings some attention to the pex3 lock export sub-command to make it more useful when inter-operating with pip-tools.

  • Sort requirements based on normalized project name when exporting (#1992)
  • Use raw version when exporting (#1990)

pex 2.1.114


2.1.114

This release brings two fixes for --venv mode PEXes.

  • Only insert "" to head of sys.path if a venv PEX runs in interpreter mode (#1984)
  • Map pex python path interpreter to realpath when creating venv dir hash. (#1972)

pex 2.1.113


... (truncated)

Changelog

Sourced from pex's changelog.

2.1.117

This release fixes a bug introduced in Pex 2.1.109 where the released Pex PEX could not be executed by PyPy interpreters. More generally, any PEX created with interpreter constraints that did not specify the Python implementation, e.g.: ==3.8.*, were interpreted as being CPython specific, i.e.: CPython==3.8.*. This is now fixed, but if the intention of a constraint like ==3.8.* was in fact to restrict to CPython only, interpreter constraints need to say so now and use CPython==3.8.* explicitly.

  • Fix interpreter constraint parsing. (#1998) PR [#1998](https://github.com/pantsbuild/pex/issues/1998) <https://github.com/pantsbuild/pex/pull/1998>_

2.1.116

This release fixes a bug in --resolve-local-platforms when --complete-platform was used.

  • Check for --complete-platforms match when --resolve-local-platforms (#1991) PR [#1991](https://github.com/pantsbuild/pex/issues/1991) <https://github.com/pantsbuild/pex/pull/1991>_

2.1.115

This release brings some attention to the pex3 lock export subcommand to make it more useful when inter-operating with pip-tools.

  • Sort requirements based on normalized project name when exporting (#1992) PR [#1992](https://github.com/pantsbuild/pex/issues/1992) <https://github.com/pantsbuild/pex/pull/1992>_

  • Use raw version when exporting (#1990) PR [#1990](https://github.com/pantsbuild/pex/issues/1990) <https://github.com/pantsbuild/pex/pull/1990>_

2.1.114

This release brings two fixes for --venv mode PEXes.

  • Only insert "" to head of sys.path if a venv PEX runs in interpreter mode (#1984) PR [#1984](https://github.com/pantsbuild/pex/issues/1984) <https://github.com/pantsbuild/pex/pull/1984>_

  • Map pex python path interpreter to realpath when creating venv dir hash. (#1972) PR [#1972](https://github.com/pantsbuild/pex/issues/1972) <https://github.com/pantsbuild/pex/pull/1972>_

2.1.113

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

Superseded by #104.