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.1v1.0.7->v1.0.10v1.20.1->v1.21.0Release Notes
spf13/cobra (github.com/spf13/cobra)
v1.10.1Compare Source
🐛 Fix
v1.0.9 of pflags brought back
ParseErrorsWhitelistand marked it as deprecatedFull Changelog: https://github.com/spf13/cobra/compare/v1.10.0...v1.10.1
v1.10.0Compare Source
What's Changed
🚨 Attention!
This version of
pflagcarried a breaking change: it renamedParseErrorsWhitelisttoParseErrorsAllowlistwhich can break builds if bothpflagandcobraare dependencies in your project.pflag andcobra, upgradepflagto 1.0.8 andcobrato1.10.0`pflagv1.0.9 which keeps the deprecatedParseErrorsWhitelistMore 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.10Compare Source
What's Changed
New Contributors
Full Changelog: https://github.com/spf13/pflag/compare/v1.0.9...v1.0.10
v1.0.9Compare Source
What's Changed
Full Changelog: https://github.com/spf13/pflag/compare/v1.0.8...v1.0.9
v1.0.8Compare Source
⚠️ Breaking Change
This version, while only a patch bump, includes a (very minor) breaking change: the
flag.ParseErrorsWhiteliststruct and correspondingFlagSet.parseErrorsWhitelistfield 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.0Compare Source
What's Changed
Enhancements 🚀
Bug Fixes 🐛
Dependency Updates ⬆️
Other Changes
mapstructurepackage 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.
97f780d4e8toe058180744chore(deps): update module github.com/spf13/pflag to v1.0.8to chore(deps): update module github.com/spf13/pflag to v1.0.9e058180744to6b4b01f9e0chore(deps): update module github.com/spf13/pflag to v1.0.9to chore(deps): update go modules6b4b01f9e0to37a7834ce837a7834ce8to88c6d87b5d88c6d87b5dto353416bf39ℹ Artifact update notice
File name: go.mod
In order to perform the update(s) described in the table above, Renovate ran the
go getcommand, which resulted in the following additional change(s):Details:
github.com/go-viper/mapstructure/v2v2.2.1->v2.4.0github.com/sagikazarmark/locaferov0.9.0->v0.11.0github.com/sourcegraph/concv0.3.0->v0.3.1-0.20240121214520-5f936abd7ae8github.com/spf13/aferov1.14.0->v1.15.0github.com/spf13/castv1.8.0->v1.10.0golang.org/x/textv0.25.0->v0.28.0353416bf39toe5715060f4