Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Vendor new safety #5217

Merged
merged 4 commits into from Aug 2, 2022
Merged

Vendor new safety #5217

merged 4 commits into from Aug 2, 2022

Conversation

matteius
Copy link
Member

@matteius matteius commented Aug 2, 2022

Going to squash my commits into this other branch,

The issue

Vendoring latest safety.

@matteius matteius merged commit 026be80 into vendor-latest-safety2 Aug 2, 2022
@matteius matteius deleted the vendor-new-safety branch August 2, 2022 01:41
yeisonvargasf pushed a commit to yeisonvargasf/pipenv that referenced this pull request Nov 19, 2022
* Vendor safety==2.1.1 cleanly with ruamel.

* Apply more minimal patch to safety.
matteius added a commit that referenced this pull request Nov 23, 2022
* Vendor new safety (#5217)

* Closest to correct vendoring of ruamel.

* Fix lint

* New pipenv check with minimal output.

* Remove decode_for_output use in pipenv check functions.

* Use click.secho where is possible.

* Rerun vendoring to get the latest safety version.

* skip this test for now.

Co-authored-by: Yeison Vargas <yeisonvargasjf@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant