search

godatadriven / dbt-bouncer

Configure and enforce conventions for your dbt project.
https://godatadriven.github.io/dbt-bouncer
MIT License
25 stars 2 forks source link

Bump pex from 2.17.0 to 2.19.1 #265

Closed dependabot[bot] closed 1 month ago

dependabot[bot] commented 1 month ago

Bumps pex from 2.17.0 to 2.19.1.

Release notes

Sourced from pex's releases.

pex 2.19.1

2.19.1

This release fixes a regression introduced by #2512 in the 2.19.0 release when building PEXes using abbreviated --platform targets. Instead of failing certain builds that used to succeed, Pex now warns that the resulting PEX may fail at runtime and that --complete-platform should be used instead.

  • Only warn when --platform resolves fail tag checks. (#2533)
file sha256 size
pex 86ef2ac38d36aba203dc5b9819b77c3e25fb8588b01c9d15f66b1c94bdbc989b 4310578
pex-linux-aarch64 bfe9e3fc43b93a2cf07aafe7573cd047fa182d8d8bf5a01922db6aace845fcc6 24051503
pex-linux-x86_64 427b1fcbccdafa8c07a81a4e6085802e66de49efb82eba035a9a66a846992bc5 27667757
pex-macos-aarch64 0d61f5f6dade67a303fe0f85f55f6bb5a90652bfc8ea62f38ec3fe8d19a06771 21522752
pex-macos-x86_64 368b2c86902f3e56572913101498986c3b8ee5337d0c0f66b36596f600a43f42 22036967

pex 2.19.0

2.19.0

This release adds support for a new --pre-resolved-dists resolver as an alternative to the existing Pip resolver, --lock resolver and --pex-repository resolvers. Using --pre-resolved-dists dists/dir/ behaves much like --no-pypi --find-links dists/dir/ except that it is roughly 3x faster.

  • Support --pre-resolved-dists resolver. (#2512)
file sha256 size
pex 1b56d778fcf3b9504838277a7a20d6676b9f947aaa4759873830af2e78bf33ab 4310167
pex-linux-aarch64 e61d4fd3d9ad237fdb4de3eae3ab8b4ccd6dcb9927aa3fa6670f6ed41e859563 24051094
pex-linux-x86_64 46c9b66cfff839cae952ec5daa3fa2e98e2d5c095e630a33d10bb050f21b2280 27667352
pex-macos-aarch64 e8751e169c57b4610cd4f21b345c12977e829e5621c438aaebea691e7f6395ea 21522348
pex-macos-x86_64 4f30267de92e407e0a5454155d4dd06f62809197ec341d4083e81e194fcb1f63 22036558

pex 2.18.1

2.18.1

This release fixes --scie-name-style platform-parent-dir introduced in #2523. Previously the target platform name also leaked into scies targeting foreign platforms despite using this option.

... (truncated)

Changelog

Sourced from pex's changelog.

2.19.1

This release fixes a regression introduced by #2512 in the 2.19.0 release when building PEXes using abbreviated --platform targets. Instead of failing certain builds that used to succeed, Pex now warns that the resulting PEX may fail at runtime and that --complete-platform should be used instead.

  • Only warn when --platform resolves fail tag checks. (#2533)

2.19.0

This release adds support for a new --pre-resolved-dists resolver as an alternative to the existing Pip resolver, --lock resolver and --pex-repository resolvers. Using --pre-resolved-dists dists/dir/ behaves much like --no-pypi --find-links dists/dir/ except that it is roughly 3x faster.

  • Support --pre-resolved-dists resolver. (#2512)

2.18.1

This release fixes --scie-name-style platform-parent-dir introduced in #2523. Previously the target platform name also leaked into scies targeting foreign platforms despite using this option.

  • Fix --scie-name-style platform-parent-dir. (#2526)

2.18.0

This release adds support for pex3 cache {dir,info,purge} for inspecting and managing the Pex cache. Notably, the pex3 cache purge command is safe in the face of concurrent PEX runs, waiting for in flight PEX runs to complete and blocking new runs from starting once the purge is in progress. N.B.: when using pex3 cache purge it is best to install Pex with the 'management' extra; e.g.: pip install pex[management]. Alternatively, one of the new Pex scie binary releases can be used.

In order to release a Pex binary that can support the new pex3 cache management commands first class, a set of enhancements to project locking and scie generation were added. When using --project you can now specify extras; e.g.: --project ./the/project-dir[extra1,extra2]. When creating a Pex scie, you can now better control the output files using --scie-only to ensure no PEX file is emitted and --scie-name-style to control how the scie target platform name is mixed into the scie output file name. Additionally, you can request one or more shasum-compatible checksum files be emitted for each scie with --scie-hash-alg.

... (truncated)

Commits


Most Recent Ignore Conditions Applied to This Pull Request | Dependency Name | Ignore Conditions | | --- | --- | | pex | [>= 2.20.a, < 2.21] |

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)
dependabot[bot] commented 1 month 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. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

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