chore(deps): update dependency safety to v3 #467
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
2.3.4
->3.2.10
Release Notes
pyupio/safety (safety)
v3.2.10
Compare Source
v3.2.9
Compare Source
4149b70
)61b2fe2
)be42d8e
)5ec80dd
)0591838
)04d7efb
)07bc5b7
)78109e5
)cc49542
)v3.2.8
Compare Source
v3.2.7
Compare Source
v3.2.6
Compare Source
v3.2.5
Compare Source
v3.2.4
Compare Source
get_from_cache=None
and ensure directory exists (#538)install_requires
(#538)v3.2.3
Compare Source
v3.2.2
Compare Source
v3.2.1
Compare Source
v3.2.0
Compare Source
v3.1.0
Compare Source
v3.0.1
Compare Source
v3.0.0
Compare Source
Safety 3.0.0 major version release!
Main updates
check
command, including automatic Python project scanning, native support for Poetry and Pipenv files, Python virtual environment folders, and more granular configuration options.safety check
. To migrate a Safety 2.x policy, see Migrating from Safety 2.x to Safety CLI 3.New scan command:
safety check
with a more powerful and easier to use command. The scan command:report
field.Other new commands:
safety check
command can still be used with the API key --key argument, and scan and system-scan commands should also beNew policy file schema for scan and system-scan commands
Adds scanning-settings root property, which contains settings to configure rules and settings for how safety traverses the directory and subdirectories being scanned, including “exclude” rules, “include” rules, the max directory depth to scan and which root directories safety system-scan should start from.
safety check
command still supports and relies on the policy schema from safety 2.3.5 and below, meaning no changes are required when migrating to safety 2.x to Safety 3.0.0 when only using thesafety check
command.New global options and configurations
scan
andsystem-scan
commands.Other
safety check
command, since this is now replaced bysafety scan
, a more comprehensive scanning command. The check command will continue receiving maintenance support until June 2024.safety alert
command, which works in tandem with thesafety check
command. Safety alert functionality is replaced by Safety Platform. The alert command will continue receiving maintenance support until June 2024.safety validate
will assume 3.0 policy file version by default.Small updates/ bug fixes
v2.3.5
Compare Source
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.