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.

Sign up for GitHub

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

Jump to bottom

Update module github.com/spf13/viper to v1.12.0 #367

Merged
merged 1 commit into from
May 28, 2022
Merged

Update module github.com/spf13/viper to v1.12.0 #367

merged 1 commit into from
May 28, 2022

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 16, 2021 •
edited
Loading

Mend Renovate

This PR contains the following updates:

Package Type Update Change
github.com/spf13/viper require minor v1.7.1 -> v1.12.0

Release Notes

spf13/viper

v1.12.0

Compare Source

This release makes YAML v3 and TOML v2 the default versions used for encoding.

You can switch back to the old versions by adding viper_yaml2 and viper_toml1 to the build tags.

Please note that YAML v2 and TOML v1 are considered deprecated from this release and may be removed in a future release.

Please provide feedback in discussions and report bugs on the issue tracker. Thanks!

What's Changed

Exciting New Features 🎉
Enhancements 🚀
Dependency Updates ⬆️

New Contributors

Full Changelog: spf13/viper@v1.11.0...v1.12.0

v1.11.0

Compare Source

What's Changed

Exciting New Features 🎉
Enhancements 🚀
Bug Fixes 🐛
Breaking Changes 🛠
Dependency Updates ⬆️

New Contributors

Full Changelog: spf13/viper@v1.10.1...v1.11.0

v1.10.1

Compare Source

This is a maintenance release upgrading the Consul dependency fixing CVEs.

v1.10.0

Compare Source

This is a maintenance release primarily containing minor fixes and improvements.

Changes

Added
  • Experimental finder based on io/fs
  • Tests are executed on Windows
  • Tests are executed on Go 1.17
  • Logger interface to decouple Viper from JWW

In addition to the above changes, this release comes with minor improvements, documentation changes an dependency updates.

Many thanks to everyone who contributed to this release!

v1.9.0

Compare Source

This is a maintenance release primarily containing minor fixes and improvements.

Changes

Added
  • Experimental new encoding layer
  • Add support for tfvars files
Fixed
  • Writing hidden files with no extension
  • InConfig processing paths

In addition to the above changes, this release comes with tons of minor improvements, documentation changes an dependency updates.

Many thanks to everyone who contributed to this release!

v1.8.1

Compare Source

This patch releases fixes two minor issues:

  • Replace %s with %w when wrapping errors
  • Fix pflag.StringArray processing

v1.8.0

Compare Source

This is a maintenance release primarily containing fixes and improvements. The most prominent change is the etcd update to 3.5.0. Thanks to proper Go modules support, the dependency graph became much smaller.

Changes

Added
  • Allow BindEnv to register multiple environment variables
  • Support for accessing slices
  • Experimental WASM support: Viper compiles on WASM
  • INI load options
Changed
  • Ensure BindPFlag detects a nil flag parameter
Fixed
  • Merging a key into a nil target
  • Panics during saving INI files
Security
  • Updated etcd to 3.5 which should make a lot of false positive vulnerability reports disappear

In addition to the above changes, this release comes with tons of minor improvements, documentation changes an dependency updates. Find more details in the 1.8.0 milestone.

Many thanks to everyone who contributed to this release!

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.

  • If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/gh.neting.cc-spf13-viper-1.x branch from 2fae6c1 to 6585adc Compare June 25, 2021 12:20
@renovate renovate bot changed the title Update module github.com/spf13/viper to v1.8.0 Update module github.com/spf13/viper to v1.8.1 Jun 25, 2021
@renovate renovate bot changed the title Update module github.com/spf13/viper to v1.8.1 Update module github.com/spf13/viper to v1.9.0 Oct 18, 2021
@renovate renovate bot force-pushed the renovate/gh.neting.cc-spf13-viper-1.x branch from 6585adc to af3e51c Compare October 18, 2021 15:28
@renovate renovate bot force-pushed the renovate/gh.neting.cc-spf13-viper-1.x branch from af3e51c to 5a809fb Compare December 9, 2021 06:08
@github-actions github-actions bot force-pushed the renovate/gh.neting.cc-spf13-viper-1.x branch from 5a809fb to 6e0bca5 Compare December 9, 2021 06:08
@renovate renovate bot force-pushed the renovate/gh.neting.cc-spf13-viper-1.x branch from 6e0bca5 to 4281891 Compare December 9, 2021 06:13
@github-actions github-actions bot force-pushed the renovate/gh.neting.cc-spf13-viper-1.x branch from 4281891 to 09885f5 Compare December 9, 2021 06:14
@renovate renovate bot force-pushed the renovate/gh.neting.cc-spf13-viper-1.x branch from 09885f5 to 8f05d5e Compare December 9, 2021 09:37
@github-actions github-actions bot force-pushed the renovate/gh.neting.cc-spf13-viper-1.x branch from 8f05d5e to a4067d0 Compare December 9, 2021 09:38
@renovate renovate bot force-pushed the renovate/gh.neting.cc-spf13-viper-1.x branch from a4067d0 to 3dc74f9 Compare December 12, 2021 05:21
@renovate renovate bot changed the title Update module github.com/spf13/viper to v1.9.0 Update module github.com/spf13/viper to v1.10.0 Dec 12, 2021
@github-actions github-actions bot force-pushed the renovate/gh.neting.cc-spf13-viper-1.x branch from 3dc74f9 to b14ea27 Compare December 12, 2021 05:22
@renovate renovate bot force-pushed the renovate/gh.neting.cc-spf13-viper-1.x branch from b14ea27 to 91e1faa Compare December 15, 2021 13:52
@renovate renovate bot changed the title Update module github.com/spf13/viper to v1.10.0 Update module github.com/spf13/viper to v1.10.1 Dec 15, 2021
@github-actions github-actions bot force-pushed the renovate/gh.neting.cc-spf13-viper-1.x branch from 91e1faa to 71b3050 Compare December 15, 2021 13:52
@renovate renovate bot changed the title Update module github.com/spf13/viper to v1.10.1 Update module github.com/spf13/viper to v1.11.0 Apr 24, 2022
@renovate renovate bot force-pushed the renovate/gh.neting.cc-spf13-viper-1.x branch from 71b3050 to 2fb9ea2 Compare April 24, 2022 22:50
@github-actions github-actions bot force-pushed the renovate/gh.neting.cc-spf13-viper-1.x branch from 2fb9ea2 to c665e83 Compare April 24, 2022 22:51
h3poteto
h3poteto reviewed May 28, 2022
View reviewed changes
go.sum
cloud.google.com/go/bigquery v1.4.0/go.mod h1:S8dzgnTigyfTmLBfrtrhyYhwRxG72rYxvftPBK2Dvzc=
cloud.google.com/go/bigquery v1.5.0/go.mod h1:snEHRnqQbz117VIFhE8bmtwIDY80NLUZUMb4Nv6dBIg=
cloud.google.com/go/bigquery v1.7.0/go.mod h1://okPTzCYNXSlb24MZs83e2Do+h+VXtc4gLoIoXIAPc=
cloud.google.com/go/bigquery v1.8.0/go.mod h1:J5hqkt3O0uAFnINi6JXValWIb1v0goeZM77hZzJN/fQ=
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[Secret Scan] It may be dangerous to commit the AWS secret access key. (view)

AWS secret access key is an important credential that allows you to use AWS programmatically.
Once this leaks, an attacker can access and operate your AWS resources.

See also:

Rule Severity
sider.secrets.aws.secret_access_key warning

You can close this issue if no need to fix it. Learn more.

I closed this issue. Reason:

  • When this is not an AWS secret access key.

h3poteto
h3poteto reviewed May 28, 2022
View reviewed changes
go.sum
github.com/fatih/color v1.7.0/go.mod h1:Zm6kSWBoL9eyXnKyktHP6abPY2pDugNf5KwzbycvMj4=
github.com/fsnotify/fsnotify v1.4.7 h1:IXs+QLmnXW2CcXuY+8Mzv/fWEsPGWxqefPtCP5CnV9I=
github.com/fatih/color v1.9.0/go.mod h1:eQcE1qtQxscV5RaZvpXrrb8Drkc3/DdQ+uUYCNjL+zU=
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[Secret Scan] It may be dangerous to commit the AWS secret access key. (view)

AWS secret access key is an important credential that allows you to use AWS programmatically.
Once this leaks, an attacker can access and operate your AWS resources.

See also:

Rule Severity
sider.secrets.aws.secret_access_key warning

You can close this issue if no need to fix it. Learn more.

I closed this issue. Reason:

  • When this is not an AWS secret access key.

h3poteto
h3poteto reviewed May 28, 2022
View reviewed changes
go.sum
google.golang.org/api v0.36.0/go.mod h1:+z5ficQTmoYpPn8LCUNVpK5I7hwkpjbcgqA7I34qYtE=
google.golang.org/api v0.40.0/go.mod h1:fYKFpnQN0DsDSKRVRcQSDQNtqWPfM9i+zNPxepjRCQ8=
google.golang.org/api v0.41.0/go.mod h1:RkxM5lITDfTzmyKFPt+wGrCJbVfniCr2ool8kTBzRTU=
google.golang.org/api v0.43.0/go.mod h1:nQsDGjRXMo4lvh5hP0TKqF244gqhGcr/YSIykhUk/94=
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[Secret Scan] It may be dangerous to commit the AWS secret access key. (view)

AWS secret access key is an important credential that allows you to use AWS programmatically.
Once this leaks, an attacker can access and operate your AWS resources.

See also:

Rule Severity
sider.secrets.aws.secret_access_key warning

You can close this issue if no need to fix it. Learn more.

I closed this issue. Reason:

  • When this is not an AWS secret access key.

@renovate renovate bot force-pushed the renovate/gh.neting.cc-spf13-viper-1.x branch from c665e83 to 62113e3 Compare May 28, 2022 03:07
@renovate renovate bot changed the title Update module github.com/spf13/viper to v1.11.0 Update module github.com/spf13/viper to v1.12.0 May 28, 2022
@h3poteto
Copy link
Owner

[Secret Scan] It may be dangerous to commit the AWS secret access key. (view)

AWS secret access key is an important credential that allows you to use AWS programmatically.
Once this leaks, an attacker can access and operate your AWS resources.

See also:

Rule Severity
sider.secrets.aws.secret_access_key warning

You can close this issue if no need to fix it. Learn more.

I closed this issue. Reason:

  • When this is not an AWS secret access key.

@github-actions github-actions bot force-pushed the renovate/gh.neting.cc-spf13-viper-1.x branch from 62113e3 to 4a84448 Compare May 28, 2022 03:08
@renovate renovate bot force-pushed the renovate/gh.neting.cc-spf13-viper-1.x branch from 4a84448 to 1efc817 Compare May 28, 2022 03:09
@github-actions github-actions bot force-pushed the renovate/gh.neting.cc-spf13-viper-1.x branch from 1efc817 to 5d5805b Compare May 28, 2022 03:09
@h3poteto h3poteto merged commit e5fe02e into master May 28, 2022
@renovate renovate bot deleted the renovate/gh.neting.cc-spf13-viper-1.x branch May 28, 2022 04:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@h3poteto h3poteto h3poteto left review comments

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@h3poteto @renovate-bot