You've already forked drone-email
chore(deps): update go modules #102
Reference in New Issue
Block a user
No description provided.
Delete Branch "renovate/go-modules"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
v1.9.1
->v1.10.1
v1.0.7
->v1.0.10
v1.20.1
->v1.21.0
Release Notes
spf13/cobra (github.com/spf13/cobra)
v1.10.1
Compare Source
🐛 Fix
v1.0.9 of pflags brought back
ParseErrorsWhitelist
and marked it as deprecatedFull Changelog: https://github.com/spf13/cobra/compare/v1.10.0...v1.10.1
v1.10.0
Compare Source
What's Changed
🚨 Attention!
This version of
pflag
carried a breaking change: it renamedParseErrorsWhitelist
toParseErrorsAllowlist
which can break builds if bothpflag
andcobra
are dependencies in your project.pflag and
cobra, upgrade
pflagto 1.0.8 and
cobrato
1.10.0`pflag
v1.0.9 which keeps the deprecatedParseErrorsWhitelist
More details can be found here: #2303 (comment)
✨ Features
🐛 Fix
🪠 Testing
📝 Docs
New Contributors
Full Changelog: https://github.com/spf13/cobra/compare/v1.9.1...v1.9.2
spf13/pflag (github.com/spf13/pflag)
v1.0.10
Compare Source
What's Changed
New Contributors
Full Changelog: https://github.com/spf13/pflag/compare/v1.0.9...v1.0.10
v1.0.9
Compare Source
What's Changed
Full Changelog: https://github.com/spf13/pflag/compare/v1.0.8...v1.0.9
v1.0.8
Compare Source
⚠️ Breaking Change
This version, while only a patch bump, includes a (very minor) breaking change: the
flag.ParseErrorsWhitelist
struct and correspondingFlagSet.parseErrorsWhitelist
field have been renamed toParseErrorsAllowlist
.This should result in compilation errors in any code that uses these fields, which can be fixed by adjusting the names at call sites. There is no change in semantics or behavior of the struct or field referred to by these names. If your code compiles without errors after bumping to/past v1.0.8, you are not affected by this change.
The breaking change was reverted in v1.0.9, by means of re-introducing the old names with deprecation warnings. The plan is still to remove them in a future release, so if your code does depend on the old names, please change them to use the new names at your earliest convenience.
What's Changed
New Contributors
Full Changelog: https://github.com/spf13/pflag/compare/v1.0.7...v1.0.8
spf13/viper (github.com/spf13/viper)
v1.21.0
Compare Source
What's Changed
Enhancements 🚀
Bug Fixes 🐛
Dependency Updates ⬆️
Other Changes
mapstructure
package replacement. by @aldas in #2004New Contributors
Full Changelog: https://github.com/spf13/viper/compare/v1.20.0...v1.21.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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Renovate Bot.
97f780d4e8
toe058180744
chore(deps): update module github.com/spf13/pflag to v1.0.8to chore(deps): update module github.com/spf13/pflag to v1.0.9e058180744
to6b4b01f9e0
chore(deps): update module github.com/spf13/pflag to v1.0.9to chore(deps): update go modules6b4b01f9e0
to37a7834ce8
37a7834ce8
to88c6d87b5d
88c6d87b5d
to353416bf39
ℹ 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):Details:
github.com/go-viper/mapstructure/v2
v2.2.1
->v2.4.0
github.com/sagikazarmark/locafero
v0.9.0
->v0.11.0
github.com/sourcegraph/conc
v0.3.0
->v0.3.1-0.20240121214520-5f936abd7ae8
github.com/spf13/afero
v1.14.0
->v1.15.0
github.com/spf13/cast
v1.8.0
->v1.10.0
golang.org/x/text
v0.25.0
->v0.28.0
353416bf39
toe5715060f4