Update sprig to v3 to resolve semver constraint validity issues #374
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.
The Masterminds/sprig library was identifying the kubeVersion value
>= 1.23.0 < 1.26.3
to be invalid. This was known working within Helm itself. Peeking at the helm source, I saw that the helm source is using v3 of this library, and we were using v2, so this PR bumps that dependency and adds test to make sure we pass this case.