Repository navigation
Conversation
rvesse
force-pushed
the
cache-fix
branch
6 times, most recently
from
October 7, 2026 09:48
90ae4de to
4f7cb50
Compare
Previously the action always used a fixed cache key based on the Grype version. This meant that once the cache was created in a repository it could never be updated because GitHub Actions Cache keys are immutable. This meant that the action was frequently downloading a DB update because the cached DB would quickly become stale. The only time the cache would actually update was if the Grype version was changed. The action now creates cache keys using the DB build timestamp so when a new DB update is obtained we update the cache with it using a new key. Thus repositories cache up to date versions of the DB and old stale DB caches will naturally be expired and removed by GitHub Actions. The cache restoration uses restore keys with partial timestamps (day, month, and year) to ensure the most recent cache is always restored, falling back to the legacy cache key used prior to this commit as a restore key. Signed-off-by: Rob Vesse <rob.vesse@telicent.io>
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Previously the action always used a fixed cache key based on the Grype version. This meant that once the cache was created in a repository it could never be updated because GitHub Actions Cache keys are immutable. This meant that the action was frequently downloading a DB update because the cached DB would quickly become stale. The only time the cache would actually update was if the Grype version was changed.
The action now creates cache keys using the DB build timestamp so when a new DB update is obtained we update the cache with it using a new key. Thus repositories cache up to date versions of the DB and old stale DB caches will naturally be expired and removed by GitHub Actions.
The cache restoration uses restore keys with partial timestamps (day, month, and year) to ensure the most recent cache is always restored, falling back to the legacy cache key used prior to this commit as a restore key.
This fixes #778
Validating