fix: Bump stacker Cache Version for WasBom field#760
Merged
hallyn merged 1 commit intoproject-stacker:mainfrom Mar 20, 2026
Merged
fix: Bump stacker Cache Version for WasBom field#760hallyn merged 1 commit intoproject-stacker:mainfrom
hallyn merged 1 commit intoproject-stacker:mainfrom
Conversation
In the previous PR to update CVEs which dropped BOM support a field to Layer structure, WasBom, was added to provide a warning message to users which supply a stacker.yaml with the `bom:` value set. This change to the Layer structure requires a bump to the CacheVersion field. Signed-off-by: Ryan Harper <rharper@woxford.com>
raharper
requested review from
hallyn,
mikemccracken,
rchamarthy,
rchincha,
smoser and
tych0
as code owners
Merged
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #760 +/- ##
===========================================
- Coverage 64.74% 54.18% -10.56%
===========================================
Files 53 55 +2
Lines 4601 5909 +1308
===========================================
+ Hits 2979 3202 +223
- Misses 1024 2128 +1104
+ Partials 598 579 -19 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
hallyn
approved these changes
Mar 20, 2026
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
2 participants
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.
In the previous PR to update CVEs which dropped BOM support a field to Layer structure, WasBom, was added to provide a warning message to users which supply a stacker.yaml with the
bom:value set.This change to the Layer structure requires a bump to the CacheVersion field.
What type of PR is this?
bug
Which issue does this PR fix:
TestCacheEntryChanged
What does this PR do / Why do we need it:
Bump CacheVersion to 16, update TestCache hash in test case. This fixes the issue introduced when added
WasBomflag to provide a helpful message to users ofbom:If an issue # is not available please add repro steps and logs showing the issue:
make go-testTesting done on this change:
Re-ran
make go-testand it passes nowAutomation added to e2e:
None
Will this break upgrades or downgrades?
No
Does this PR introduce any user-facing change?:
No
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.