support numeric values in CSV release field #1904
Closed
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 of the change:
The GetRelease() function previously failed when the release field in a CSV spec was specified as a numeric value (e.g., release: 0.20250104) instead of a string. This occurred because YAML parsers treat values starting with digits as numbers, and the function attempted to unmarshal directly into a string type, causing a type mismatch error.
Modified GetRelease() to first unmarshal into an interface{} type, then convert to string using fmt.Sprintf(), allowing it to handle both string and numeric release values.