This repository has been archived by the owner on Mar 27, 2022. It is now read-only.
fix(deps): update module github.com/masterminds/sprig to v3 #154
Conversation
This file contains 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
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This PR contains the following updates:
v2.22.0+incompatible->v3.2.2Release Notes
Masterminds/sprig
v3.2.2Compare Source
This release is here simply to satisfy the Go module system. The code is precisely the same as v3.2.1.
v3.2.1Compare Source
This is a security release for
Masterminds/goutilsv1.1.1. See the Security Advisory.Changelog
Release 3.2.1 (2021-02-04)
Changed
Masterminds/goutilstov1.1.1. see the Security Advisoryv3.2.0Compare Source
Added
(thanks @andrewmostello)
ed25519keys (thanks @misberner)Changed
ed25519support requires Go 1.13 or newerFixed
NOTE: The dependency github.com/imdario/mergo reverted the breaking change in
0.3.9 via 0.3.10 release.
v3.1.0Compare Source
NOTE: The dependency github.com/imdario/mergo made a behavior change in 0.3.9
that impacts sprig functionality. Do not use sprig with a version newer than 0.3.8.
Added
seqfunction (thanks @thadc23)Changed
as it causes a breaking change for sprig. That issue is trackedhttps://github.com/imdario/mergo/issues/139sues/139
Fixed
seqexample in docs (thanks @kalmant)v3.0.2Compare Source
Fixed
v3.0.1Compare Source
Fixed
v3.0.0Compare Source
Sprig v3 brings some changes while retaining the same Go API. This should enable projects to migrate to v3 with relative ease.
You might be wondering, why increment the major version if the Go API didn't break? The reason for that is some edge case behavior changed. Most importantly the use of
^while handling major version 0 use cases with semver. To be cautious, the major version of sprig was incremented to limit the number of surprises.Added
Changed
Configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by WhiteSource Renovate. View repository job log here.