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

Grype DB schemas v1 & v2 are EOL #2075

Closed
2 tasks
willmurphyscode opened this issue Aug 21, 2024 · 0 comments · Fixed by anchore/grype-db#434
Closed
2 tasks

Grype DB schemas v1 & v2 are EOL #2075

willmurphyscode opened this issue Aug 21, 2024 · 0 comments · Fixed by anchore/grype-db#434
Assignees
Labels
changelog-ignore Don't include this issue in the release changelog planning high level epic that should be broken into smaller tasks

Comments

@willmurphyscode
Copy link
Contributor

This issue tracks the work to turn down the infra related to Grype DB Schema v1 and Grype DB Schema v2. (Note to concerned visitors: anyone using grype after v0.13.0, which was released in 1 June 2021, is not by this change. If you are using a version of Grype from May 2021 or before, it's time to upgrade.) See also the official announcement on Discourse

Tasks

@willmurphyscode willmurphyscode added breaking-change planning high level epic that should be broken into smaller tasks labels Aug 21, 2024
@wagoodman wagoodman pinned this issue Oct 31, 2024
@wagoodman wagoodman self-assigned this Nov 18, 2024
@wagoodman wagoodman moved this to In Progress in OSS Nov 18, 2024
@wagoodman wagoodman moved this from In Progress to In Review in OSS Nov 21, 2024
@wagoodman wagoodman added changelog-ignore Don't include this issue in the release changelog and removed breaking-change labels Nov 21, 2024
@github-project-automation github-project-automation bot moved this from In Review to Done in OSS Nov 21, 2024
@wagoodman wagoodman changed the title Turning down old Grype DB Schemas - schema v1, v2 will go EOL on 20 November 2024 Grype DB schemas v1 & v2 are EOL Nov 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
changelog-ignore Don't include this issue in the release changelog planning high level epic that should be broken into smaller tasks
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants