fix: handle Docker image tags with SHA256 hash #313
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.
Description
Fixes an issue where Docker images with SHA256 hashes in their tags were being incorrectly validated, resulting in false "Missing image tag" errors. The fix modifies the tag parsing logic to properly handle tags that include SHA256 hashes by extracting only the version number portion for validation purposes.
For example, with an image like
cimg/node:22.11.0@sha256:76aae59c6259672ab68819b8960de5ef571394681089eab2b576f85f080c73ba
, the system now correctly extracts22.11.0
as the tag for validation while preserving the full reference.Implementation details
parseDockerImageValue
indockerImageParser.go
to split tags at "@" and use only the version part for validationdockerImageParser_test.go
to verify correct handling of tags with SHA256 hashesFullPath
field