changed some packages to force new package versions, rebuild with sbom #3956
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.
- What I did
With #3954 in, packages need to have some change if they are to get a new git tree hash, which will force a rebuild, which now will include an sbom.
I added noop changes to 7 packages to start: containerd, runc, getty, init, sysctl, memlogd, modprobe. These are commonly used in a lot of places. Eventually, we may get to the rest.
I also ran
update-component-sha.sh
to update any dependencies on them.- How I did it
Added empty comments to the Dockerfiles or removed extra lines in README, etc. Anything that is a noop but will cause the tree hash to change.
I then ran
update-component-sha.sh
for all 7.- How to verify it
Since I ran
update-component-sha.sh
, all of the tests were updated, so CI is more than sufficient.- Description for the changelog
SBoMs included with some packages.