Skip to content

Bump pex from 1.6.11 to 2.1.9#149

Closed
dependabot-preview[bot] wants to merge 1 commit into
masterfrom
dependabot/pip/pex-2.1.9
Closed

Bump pex from 1.6.11 to 2.1.9#149
dependabot-preview[bot] wants to merge 1 commit into
masterfrom
dependabot/pip/pex-2.1.9

Conversation

@dependabot-preview

@dependabot-preview dependabot-preview Bot commented Apr 8, 2020

Copy link
Copy Markdown
Contributor

Bumps pex from 1.6.11 to 2.1.9.

Release notes

Sourced from pex's releases.

pex 2.1.9

2.1.9

This release introduces the ability to copy requirements from an existing PEX into a new one.

This can greatly speed up repeatedly creating a PEX when no requirements have changed. A build tool (such as Pants) can create a "requirements PEX" that contains just a static set of requirements, and build a final PEX on top of that, without having to re-run pip to resolve requirements.

  • Support for copying requirements from an existing pex. (#948)

pex 2.1.8

2.1.8

This release brings enhanced performance when using the Pex CLI or API to resolve requirements and improved performance for many PEXed applications when specifying the --unzip option. PEXes built with --unzip will first unzip themselves into the Pex cache if not unzipped there already and then re-execute themselves from there. This can improve startup latency. Pex itself now uses this mode in our PEX release.

  • Better support unzip mode PEXes. (#941)
  • Support an unzip toggle for PEXes. (#939)
  • Ensure the interpreter path is a file (#938)
  • Cache pip.pex. (#937)

pex 2.1.7

2.1.7

This release brings more robust control of the Pex cache (PEX_ROOT).

The --cache-dir setting is deprecated in favor of build time control of the cache location with --pex-root and new support for control of the cache's runtime location with --runtime-pex-root is added. As in the past, the PEX_ROOT environment variable can still be used to control the cache's runtime location.

Unlike in the past, the Pex PEX we release can now also be controlled via the PEX_ROOT environment variable. Consult the CLI help for --no-strip-pex-env to find out more.

  • Sanitize PEX_ROOT handling. (#929)
  • Fix PEX_* env stripping and allow turning off. (#932)
  • Remove second urllib import from compatibility (#931)
  • Adding --runtime-pex-root option. (#780)
... (truncated)
Changelog

Sourced from pex's changelog.

2.1.9

This release introduces the ability to copy requirements from an existing PEX into a new one.

This can greatly speed up repeatedly creating a PEX when no requirements have changed. A build tool (such as Pants) can create a "requirements PEX" that contains just a static set of requirements, and build a final PEX on top of that, without having to re-run pip to resolve requirements.

2.1.8

This release brings enhanced performance when using the Pex CLI or API to resolve requirements and improved performance for many PEXed applications when specifying the --unzip option. PEXes built with --unzip will first unzip themselves into the Pex cache if not unzipped there already and then re-execute themselves from there. This can improve startup latency. Pex itself now uses this mode in our [PEX release](https://github.com/pantsbuild/pex/releases/download/v2.1.8/pex).

2.1.7

This release brings more robust control of the Pex cache (PEX_ROOT).

The --cache-dir setting is deprecated in favor of build time control of the cache location with --pex-root and new support for control of the cache's runtime location with --runtime-pex-root is added. As in the past, the PEX_ROOT environment variable can still be used to control the cache's runtime location.

Unlike in the past, the [Pex PEX](https://github.com/pantsbuild/pex/releases/download/v2.1.7/pex) we release can now also be controlled via the PEX_ROOT environment variable. Consult the CLI help for --no-strip-pex-env to find out more.

2.1.6

2.1.5

... (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.

If all status checks pass Dependabot will automatically merge this pull request.

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 use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
  • @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

  • Update frequency (including time of day and day of week)
  • Pull request limits (per update run and/or open at any time)
  • Automerge options (never/patch/minor, and dev/runtime dependencies)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

@dependabot-preview
Bump pex from 1.6.11 to 2.1.9
5aa895b 
Bumps [pex](https://github.com/pantsbuild/pex) from 1.6.11 to 2.1.9.
- [Release notes](https://github.com/pantsbuild/pex/releases)
- [Changelog](https://github.com/pantsbuild/pex/blob/master/CHANGES.rst)
- [Commits](pex-tool/pex@v1.6.11...v2.1.9)

Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
@dependabot-preview dependabot-preview Bot added the dependencies Pull requests that update a dependency file label Apr 8, 2020
@dependabot-preview dependabot-preview Bot mentioned this pull request Apr 8, 2020
Closed
@dependabot-preview

dependabot-preview Bot commented Apr 8, 2020

Copy link
Copy Markdown
Contributor Author

One of your CI runs failed on this pull request, so Dependabot won't merge it.

Dependabot will still automatically merge this pull request if you amend it and your tests pass.

@dependabot-preview

dependabot-preview Bot commented May 12, 2020

Copy link
Copy Markdown
Contributor Author

Superseded by #155.

@dependabot-preview dependabot-preview Bot deleted the dependabot/pip/pex-2.1.9 branch May 12, 2020 06:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants