Update module github.com/spf13/viper to v1.21.0 #46
Conversation
This file contains hidden or 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}
ℹ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
![ellipsis-dev[bot]](https://avatars.githubusercontent.com/in/64358?s=60&v=4){kind=small}
There was a problem hiding this comment.
Caution
Changes requested ❌
Reviewed everything up to ae2e547 in 3 minutes and 13 seconds. Click for details.
- Reviewed
145lines of code in2files - Skipped
0files when reviewing. - Skipped posting
3draft comments. View those below. - Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.
1. go.mod:12
- Draft comment:
Updated spf13/viper to v1.21.0 (and pflag to v1.0.10) along with related dependency bumps. Verify that any changes (e.g., config type handling) introduced in v1.21.0 are fully compatible with your code. - Reason this comment was not posted:
Confidence changes required:33%<= threshold50%None
2. go.sum:55
- Draft comment:
The updated go.sum entries (e.g. fsnotify v1.9.0, mapstructure v2.4.0, go-toml v2.2.4, locafero v0.11.0) reflect the bump in dependency versions. Confirm these checksum updates are expected. - Reason this comment was not posted:
Confidence changes required:33%<= threshold50%None
3. go.sum:179
- Draft comment:
Typographical error detected in the module path for YAML module in the go.mod entry. It reads "go.yaml.in/yaml/v3", which seems incorrect. Consider changing it to "gopkg.in/yaml.v3". - Reason this comment was not posted:
Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 0% vs. threshold = 50% The comment points out what seems like a valid issue - "go.yaml.in" is an unusual domain that could be a typo of the more common "gopkg.in". However, I need to be very careful about making assumptions about dependencies. One of the key rules is to NOT comment on dependency changes or library versions we don't recognize. Even if this looks wrong, the author may have a good reason for using this specific module path. The module path could actually be intentional - there might be a fork or alternative implementation hosted at that domain. I shouldn't assume it's wrong just because it's unfamiliar. The rules explicitly state not to comment on dependency changes or library versions we don't recognize. Even if this looks like a typo, it's not my place to question it. This comment should be deleted as it violates the rule about not commenting on dependency changes or library versions.
Workflow ID: wflow_qV06lw7BGXeC4jIB
You can customize 
| @@ -157,6 +175,8 @@ go.uber.org/atomic v1.9.0 h1:ECmE8Bn/WFTYwEW/bpKD3M8VtR/zQVbavAoalC1PYyE= | |||
| go.uber.org/atomic v1.9.0/go.mod h1:fEN4uk6kAWBTFdckzkM89CLk9XfWZrxpCo0nPH17wJc= | |||
| go.uber.org/multierr v1.9.0 h1:7fIwc/ZtS0q++VgcfqFDxSBZVv/Xo49/SYnDFupUwlI= | |||
| go.uber.org/multierr v1.9.0/go.mod h1:X2jQV1h+kxSjClGpnseKVIxpmcjrj7MNnI0bnlfKTVQ= | |||
| go.yaml.in/yaml/v3 v3.0.4 h1:tfq32ie2Jv2UxXFdLJdh3jXuOzWiL1fo0bu/FbuKpbc= | |||
There was a problem hiding this comment.
Typographical error detected in the module path for YAML. It reads "go.yaml.in/yaml/v3", which appears to be a mistake. It is likely intended to be "gopkg.in/yaml.v3". Please verify and correct accordingly.
Suggested change
| go.yaml.in/yaml/v3 v3.0.4 h1:tfq32ie2Jv2UxXFdLJdh3jXuOzWiL1fo0bu/FbuKpbc= | |
| gopkg.in/yaml.v3 v3.0.4 h1:tfq32ie2Jv2UxXFdLJdh3jXuOzWiL1fo0bu/FbuKpbc= |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
v1.20.1->v1.21.0Release Notes
spf13/viper (github.com/spf13/viper)
v1.21.0Compare Source
What's Changed
Enhancements 🚀
Bug Fixes 🐛
Dependency Updates ⬆️
Other Changes
mapstructurepackage replacement. by @aldas in #2004New Contributors
Full Changelog: spf13/viper@v1.20.0...v1.21.0
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - 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 was generated by Mend Renovate. View the repository job log.