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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

[chore]: Bump github.com/spf13/viper from 1.16.0 to 1.18.1 #2441

Closed

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Dec 11, 2023

Bumps github.com/spf13/viper from 1.16.0 to 1.18.1.

Release notes

Sourced from github.com/spf13/viper's releases.

v1.18.1

What's Changed

Bug Fixes 馃悰

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

v1.18.0

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

... (truncated)

Commits
  • fb6eb1e fix: merge missing struct keys inside UnmarshalExact
  • f5fcb4a chore: update crypt
  • f736363 fix isPathShadowedInFlatMap type cast bug (#1585)
  • 36a3868 Review changes
  • f0c4ccd fix: gocritic lint issues
  • 3a23b80 ci: enable test shuffle; fix tests
  • 73dfb94 feat: make Unmarshal work with AutomaticEnv
  • 6ea31ae refactor: move all settings code to a getter
  • c4dcd31 fix: godot lint issues
  • 4c9b2a2 Note Get* behavior on parse failure
  • Additional commits viewable in compare view

Most Recent Ignore Conditions Applied to This Pull Request
Dependency Name Ignore Conditions
github.com/spf13/viper [>= 1.17.a, < 1.18]

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot dependabot bot added the chore a pain in the butt that needs doing label Dec 11, 2023
Bumps [github.com/spf13/viper](https://github.com/spf13/viper) from 1.16.0 to 1.18.1.
- [Release notes](https://github.com/spf13/viper/releases)
- [Commits](spf13/viper@v1.16.0...v1.18.1)

---
updated-dependencies:
- dependency-name: github.com/spf13/viper
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot force-pushed the dependabot/go_modules/github.com/spf13/viper-1.18.1 branch from 137cf64 to 938de55 Compare December 11, 2023 10:10
@NyaaaWhatsUpDoc
Copy link
Member

This is somehow causing build failures, which I think is due to it (somehow?) updating the experimental slices package we rely on in a few areas, i.e. "golang.org/x/exp/slices". As the build error is complaining that the slices sort function signature has changed. This can be fixed by updating the anonymous function signature we're using, and it would also be worth changing all of those files to instead import the standard library slices package "slices".

Though also to keep in mind, as @daenney pointed out in matrix, this version also seems to be causing issues for others too: spf13/viper#1706

@tsmethurst
Copy link
Contributor

Alright! I made an issue for this so we can tackle it properly instead of pushing to this dependabot PR.

@dependabot close

@dependabot dependabot bot closed this Dec 11, 2023
@dependabot dependabot bot deleted the dependabot/go_modules/github.com/spf13/viper-1.18.1 branch December 11, 2023 13:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chore a pain in the butt that needs doing
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants