Skip to content
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.19.0 #98

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 13, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
github.com/spf13/viper v1.17.0 -> v1.19.0 age adoption passing confidence

Release Notes

spf13/viper (github.com/spf13/viper)

v1.19.0

Compare Source

What's Changed

Bug Fixes 🐛
Dependency Updates ⬆️
Other Changes

New Contributors

Full Changelog: spf13/viper@v1.18.1...v1.19.0

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 or UnmarshalExact 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

v1.18.0

Compare Source

Major changes

Highlighting some of the changes for better visibility.

Please share your feedback in the Discussion forum. Thanks! ❤️

AutomaticEnv works with Unmarshal

Previously, environment variables that weren't bound manually or had no defaults could not be mapped by Unmarshal. (The problem is explained in details in this issue: #​761)

#​1429 introduced a solution that solves that issue.

What's Changed

Enhancements 🚀
Bug Fixes 🐛
Dependency Updates ⬆️
Other Changes

New Contributors

Full Changelog: spf13/viper@v1.17.0...v1.18.0


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested review from a team as code owners December 13, 2023 15:22
@renovate renovate bot enabled auto-merge (squash) December 13, 2023 15:22
Copy link

github-actions bot commented Dec 13, 2023

GraphQL Schema Check

Compared 0 schema changes against null operations

✅ Found no changes

🔗 View full schema check details

mergify[bot]
mergify bot previously approved these changes Dec 13, 2023
@renovate renovate bot force-pushed the renovate/github.com-spf13-viper-1.x branch from a97889e to 53c31ef Compare December 15, 2023 16:42
@renovate renovate bot changed the title fix(deps): update module github.com/spf13/viper to v1.18.0 fix(deps): update module github.com/spf13/viper to v1.18.1 Dec 15, 2023
mergify[bot]
mergify bot previously approved these changes Dec 15, 2023
@renovate renovate bot force-pushed the renovate/github.com-spf13-viper-1.x branch from 53c31ef to 6e5b8f9 Compare December 25, 2023 19:15
@renovate 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 25, 2023
mergify[bot]
mergify bot previously approved these changes Dec 25, 2023
mergify[bot]
mergify bot previously approved these changes Jan 17, 2024
@renovate renovate bot force-pushed the renovate/github.com-spf13-viper-1.x branch 3 times, most recently from a34e1cb to 9c8dced Compare January 18, 2024 16:48
@renovate renovate bot force-pushed the renovate/github.com-spf13-viper-1.x branch from 9c8dced to a4e2575 Compare June 8, 2024 13:03
@renovate renovate bot changed the title fix(deps): update module github.com/spf13/viper to v1.18.2 fix(deps): update module github.com/spf13/viper to v1.19.0 Jun 8, 2024
Copy link
Contributor Author

renovate bot commented Jun 8, 2024

ℹ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

  • 25 additional dependencies were updated

Details:

Package Change
github.com/stretchr/testify v1.8.4 -> v1.9.0
github.com/felixge/httpsnoop v1.0.3 -> v1.0.4
github.com/fsnotify/fsnotify v1.6.0 -> v1.7.0
github.com/go-logr/logr v1.2.4 -> v1.4.1
github.com/google/uuid v1.5.0 -> v1.6.0
github.com/nats-io/nats.go v1.31.0 -> v1.34.0
github.com/nats-io/nkeys v0.4.6 -> v0.4.7
github.com/pelletier/go-toml/v2 v2.1.0 -> v2.2.2
github.com/sagikazarmark/locafero v0.3.0 -> v0.4.0
github.com/spf13/afero v1.10.0 -> v1.11.0
github.com/spf13/cast v1.5.1 -> v1.6.0
github.com/stretchr/objx v0.5.0 -> v0.5.2
go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp v0.45.0 -> v0.49.0
go.opentelemetry.io/otel v1.19.0 -> v1.24.0
go.opentelemetry.io/otel/metric v1.19.0 -> v1.24.0
go.opentelemetry.io/otel/trace v1.19.0 -> v1.24.0
golang.org/x/crypto v0.17.0 -> v0.21.0
golang.org/x/net v0.19.0 -> v0.23.0
golang.org/x/oauth2 v0.12.0 -> v0.18.0
golang.org/x/sys v0.16.0 -> v0.18.0
google.golang.org/appengine v1.6.7 -> v1.6.8
google.golang.org/genproto/googleapis/api v0.0.0-20231016165738-49dd2c1f3d0b -> v0.0.0-20240311132316-a219d84964c2
google.golang.org/genproto/googleapis/rpc v0.0.0-20231016165738-49dd2c1f3d0b -> v0.0.0-20240314234333-6e1732d8331c
google.golang.org/grpc v1.59.0 -> v1.62.1
google.golang.org/protobuf v1.31.0 -> v1.33.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants