-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(deps): update module github.com/spf13/viper to v1.18.2 #1069
Merged
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
✅ Deploy Preview for polite-licorice-3db33c canceled.
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1069 +/- ##
=======================================
Coverage 73.53% 73.53%
=======================================
Files 32 32
Lines 3113 3113
=======================================
Hits 2289 2289
Misses 717 717
Partials 107 107 ☔ View full report in Codecov by Sentry. |
renovate
bot
force-pushed
the
renovate/github.com-spf13-viper-1.x
branch
16 times, most recently
from
December 18, 2023 15:29
422cd36
to
49c1ec1
Compare
renovate
bot
force-pushed
the
renovate/github.com-spf13-viper-1.x
branch
from
December 18, 2023 19:02
49c1ec1
to
1c7a37a
Compare
renovate
bot
changed the title
fix(deps): update module github.com/spf13/viper to v1.18.1
fix(deps): update module github.com/spf13/viper to v1.18.2
Dec 18, 2023
renovate
bot
force-pushed
the
renovate/github.com-spf13-viper-1.x
branch
9 times, most recently
from
December 20, 2023 09:06
d78ec3d
to
48ab48d
Compare
renovate
bot
force-pushed
the
renovate/github.com-spf13-viper-1.x
branch
5 times, most recently
from
December 22, 2023 03:49
0f950f0
to
d99d5fb
Compare
renovate
bot
force-pushed
the
renovate/github.com-spf13-viper-1.x
branch
from
December 22, 2023 10:38
d99d5fb
to
c5ae02d
Compare
Merged
beeme1mr
pushed a commit
that referenced
this pull request
Jan 4, 2024
🤖 I have created a release *beep* *boop* --- <details><summary>flagd: 0.8.1</summary> ## [0.8.1](flagd/v0.8.0...flagd/v0.8.1) (2024-01-04) ### 🐛 Bug Fixes * **deps:** update module github.com/open-feature/flagd/core to v0.7.3 ([#1104](#1104)) ([b6c00c7](b6c00c7)) * **deps:** update module github.com/spf13/viper to v1.18.2 ([#1069](#1069)) ([f0d6206](f0d6206)) </details> <details><summary>flagd-proxy: 0.4.1</summary> ## [0.4.1](flagd-proxy/v0.4.0...flagd-proxy/v0.4.1) (2024-01-04) ### 🐛 Bug Fixes * **deps:** update module github.com/open-feature/flagd/core to v0.7.3 ([#1104](#1104)) ([b6c00c7](b6c00c7)) * **deps:** update module github.com/spf13/viper to v1.18.2 ([#1069](#1069)) ([f0d6206](f0d6206)) </details> <details><summary>core: 0.7.4</summary> ## [0.7.4](core/v0.7.3...core/v0.7.4) (2024-01-04) ### 🐛 Bug Fixes * add custom marshalling options ([#1117](#1117)) ([e8e49de](e8e49de)) * **deps:** update kubernetes packages to v0.29.0 ([#1082](#1082)) ([751a79a](751a79a)) * **deps:** update module connectrpc.com/connect to v1.14.0 ([#1108](#1108)) ([0a41aca](0a41aca)) * **deps:** update module github.com/prometheus/client_golang to v1.18.0 ([#1110](#1110)) ([745bbb0](745bbb0)) * **deps:** update module golang.org/x/crypto to v0.17.0 [security] ([#1090](#1090)) ([26681de](26681de)) * **deps:** update module google.golang.org/protobuf to v1.32.0 ([#1106](#1106)) ([e0d3b34](e0d3b34)) </details> --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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.18.0
->v1.18.2
Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
spf13/viper (github.com/spf13/viper)
v1.18.2
Compare Source
tl;dr Skip 1.18.0 and 1.18.1 and upgrade to this version instead.
This release fixes a regression that appears in rare circumstances when using
Unmarshal
orUnmarshalExact
to decode values onto pointers with multiple indirection (eg. pointer to a pointer, etc). The change was introduced in 1.18.0 as a means to resolve a long-standing bug when decoding environment variables to structs.The feature is now disabled by default and can be enabled using the
viper_bind_struct
build tag. It's also considered experimental at this point, so breaking changes may be introduced in the future.What's Changed
Bug Fixes 🐛
Full Changelog: spf13/viper@v1.18.1...v1.18.2
v1.18.1
Compare Source
What's Changed
Bug Fixes 🐛
Full Changelog: spf13/viper@v1.18.0...v1.18.1
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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 Mend Renovate. View repository job log here.