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.

Sign up for GitHub

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

Jump to bottom

Migrate safety tool to be called with "safety scan" #1736

Open
andy-maier opened this issue Jan 5, 2025 · 2 comments · May be fixed by #1737
Open

Migrate safety tool to be called with "safety scan" #1736

andy-maier opened this issue Jan 5, 2025 · 2 comments · May be fixed by #1737
Assignees
@andy-maier
Labels
area: develop type: cleanup under work
Milestone
1.20.0

Comments

@andy-maier
Copy link
Member

See https://docs.safetycli.com/safety-docs/miscellaneous/release-notes/breaking-changes-in-safety-3
@andy-maier andy-maier self-assigned this Jan 5, 2025
@andy-maier andy-maier changed the title Migrate safety to use "safety scan" Migrate safety tool to be called with "safety scan" Jan 5, 2025
@andy-maier andy-maier added this to the 1.19.0 milestone Jan 5, 2025
@andy-maier
Copy link
Member Author

It turns out that "safety scan" requires an account on the safety site. See pyupio/safety#663

@andy-maier andy-maier linked a pull request Jan 5, 2025 that will close this issue
Migrated safety to use 'safety scan' #1737
Open
@andy-maier
Copy link
Member Author

No reaction yet on the safety issue about the need for an account. Moving this issue into the next release.

@andy-maier andy-maier modified the milestones: 1.19.0, 1.20.0 Jan 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@andy-maier andy-maier

Labels
area: develop type: cleanup under work
Projects
None yet
Milestone
1.20.0
Development

Successfully merging a pull request may close this issue.

Migrated safety to use 'safety scan' zhmcclient/python-zhmcclient
1 participant
@andy-maier