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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump safety from 1.10.3 to 2.0.0 #196

Merged
merged 1 commit into from Jun 29, 2022
Merged

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jun 29, 2022

Bumps safety from 1.10.3 to 2.0.0.

Release notes

Sourced from safety's releases.

2.0b2

Safety 2.0b2

Summary:

  • This version of Safety is not stable; it is only a beta, pre-release version.
  • Compared to previous versions, Safety 2.0 will be a significant update that includes new features and refactors, resulting in breaking changes to some inputs and outputs.
  • Improved grammar and formatting in the whole code
  • Improved the exception handling in the .yml policy file parsing
  • Improved the JSON output following the customers/users feedback - (This is a breaking change between beta releases)
  • Added the generate command
  • Added the validate command

2.0b1

Safety 2.0.0b1

This version of Safety is not stable; it is only a beta, pre-release version. Compared to previous versions, Safety 2.0 will be a significant update that includes new features and refactors, resulting in breaking changes to some inputs and outputs. See the changelogs (CHANGELOG.md) and readme update for more detailed information.

The most notable high-level changes are:

  • Vastly improved text, screen, and JSON outputs that include more detailed information about each scan and each vulnerability found.
  • New remediation (fix recommendations) output. This feature requires an API key from PyUp.io
  • Improved native exit codes for using Safety within CI/CD processes.
  • A new security policy file that enables ignoring vulnerabilities by their ID and filtering vulnerabilities by their CVSS severity score.

Contributors

This work was done by @鈥媦eisonvargasf 馃憦

Changelog

Sourced from safety's changelog.

Changelog

All notable changes to this project will be documented in this file.

The format is partly based on Keep a Changelog, and this project adheres to Semantic Versioning and PEP 440

[Unreleased] 2.0b5.dev

[2.0b4] - 2022-06-16

Summary:

  • Fixed issue with paddings and margins at specific console outputs like Github actions console
  • Added the --save-json flag and other aliases
  • Added a fallback size for the terminal size function, related to https://bugs.python.org/issue42174
  • Suppressed the announcements sent to stderr when it is running via 'run' environments

[2.0b3] - 2022-05-30

Summary:

  • Fixed issue in the Screen and Text report due to the remediations rendering for the users using an API Key
  • Improved the handling exception in the generate command

[2.0b2] - 2022-05-27

Summary:

  • This version of Safety is not stable; it is only a beta, pre-release version.
  • Compared to previous versions, Safety 2.0 will be a significant update that includes new features and refactors, resulting in breaking changes to some inputs and outputs.
  • Improved grammar and formatting in the whole code
  • Improved the exception handling in the .yml policy file parsing
  • Improved the JSON output following the customers/users feedback - (This is a breaking change between beta releases)
  • Added the generate command
  • Added the validate command

[2.0b1] - 2022-05-08

Summary:

  • This version of Safety is not stable; it is only a beta, pre-release version.
  • Compared to previous versions, Safety 2.0 will be a significant update that includes new features and refactors, resulting in breaking changes to some inputs and outputs.

Updated outputs:

  • Text & screen output: Upgraded the text and screen outputs, removing the old table style and adding new data and formats to vulnerabilities.
  • JSON output: New and updated JSON output (breaking change). Safety adds all the possible information in the JSON report. The structure of this JSON file has been improved.
  • Improved the support for exit codes. There are now custom exit codes with detailed information about the result. Examples include: VULNERABILITIES_FOUND and INVALID_API_KEY.
  • Added remediations (fix recommendations) sections to outputs. Now, Safety will suggest the steps to fix a detected vulnerability when an API key is used.
  • Added new summary meta-data data to the reports showing the Safety version used, the dependencies found, the timestamp, the target scanned, and more. These data are included in the text, screen, and JSON output for improved audit capabilities.
  • Added more info per vulnerability, including URLs to read more about a vulnerability and/or a package.

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

Bumps [safety](https://github.com/pyupio/safety) from 1.10.3 to 2.0.0.
- [Release notes](https://github.com/pyupio/safety/releases)
- [Changelog](https://github.com/pyupio/safety/blob/develop/CHANGELOG.md)
- [Commits](pyupio/safety@1.10.3...2.0.0)

---
updated-dependencies:
- dependency-name: safety
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file python Pull requests that update Python code labels Jun 29, 2022
@cauliyang cauliyang merged commit a6f8f48 into main Jun 29, 2022
@cauliyang cauliyang deleted the dependabot/pip/safety-2.0.0 branch June 29, 2022 01:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file python Pull requests that update Python code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant