fix(deps): update maru code dependencies #223
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/maru-code-dependencies
branch
from
3c7354c to
b979abe
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/maru-code-dependencies
branch
from
b979abe to
9decdbc
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/maru-code-dependencies
branch
from
9decdbc to
97e6865
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/maru-code-dependencies
branch
4 times, most recently
from
3b319e0 to
7ae4a20
Compare
renovate
bot
force-pushed
the
renovate/maru-code-dependencies
branch
from
7ae4a20 to
2d963c2
Compare
Contributor
Author
ℹ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
renovate
bot
force-pushed
the
renovate/maru-code-dependencies
branch
from
2d963c2 to
4a1dfcc
Compare
renovate
bot
force-pushed
the
renovate/maru-code-dependencies
branch
2 times, most recently
from
46f74b7 to
44afc85
Compare
Contributor
Author
ℹ️ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
renovate
bot
force-pushed
the
renovate/maru-code-dependencies
branch
from
44afc85 to
3c5e9b3
Compare
| datasource | package | from | to | | ---------- | --------------------------- | ------- | ------- | | go | github.com/goccy/go-yaml | v1.18.0 | v1.19.2 | | go | github.com/spf13/cobra | v1.9.1 | v1.10.2 | | go | github.com/spf13/pflag | v1.0.7 | v1.0.10 | | go | github.com/spf13/viper | v1.20.1 | v1.21.0 | | go | github.com/stretchr/testify | v1.10.0 | v1.11.1 |
renovate
bot
force-pushed
the
renovate/maru-code-dependencies
branch
from
3c5e9b3 to
a5e5d5e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v1.18.0→v1.19.2v1.9.1→v1.10.2v1.0.7→v1.0.10v1.20.1→v1.21.0v1.10.0→v1.11.1Release Notes
goccy/go-yaml (github.com/goccy/go-yaml)
v1.19.2: 1.19.2Compare Source
What's Changed
New Contributors
Full Changelog: goccy/go-yaml@v1.19.1...v1.19.2
v1.19.1: 1.19.1Compare Source
What's Changed
Full Changelog: goccy/go-yaml@v1.19.0...v1.19.1
v1.19.0: 1.19.0Compare Source
What's Changed
New Contributors
Full Changelog: goccy/go-yaml@v1.18.0...v1.19.0
spf13/cobra (github.com/spf13/cobra)
v1.10.2Compare Source
🔧 Dependencies
gopkg.in/yaml.v3togo.yaml.in/yaml/v3by @dims in #2336 - thegopkg.in/yaml.v3package has been deprecated for some time: this should significantly cleanup dependency/supply-chains for consumers ofspf13/cobra📈 CI/CD
🔥✍🏼 Docs
🍂 Refactors
🤗 New Contributors
Full Changelog: spf13/cobra@v1.10.1...v1.10.2
Thank you to our amazing contributors!!!!! 🐍 🚀
v1.10.1Compare Source
🐛 Fix
v1.0.9 of pflags brought back
ParseErrorsWhitelistand marked it as deprecatedFull Changelog: spf13/cobra@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: spf13/cobra@v1.9.1...v1.9.2
spf13/pflag (github.com/spf13/pflag)
v1.0.10Compare Source
What's Changed
New Contributors
Full Changelog: spf13/pflag@v1.0.9...v1.0.10
v1.0.9Compare Source
What's Changed
Full Changelog: spf13/pflag@v1.0.8...v1.0.9
v1.0.8Compare Source
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: spf13/pflag@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: spf13/viper@v1.20.0...v1.21.0
stretchr/testify (github.com/stretchr/testify)
v1.11.1Compare Source
This release fixes #1785 introduced in v1.11.0 where expected argument values implementing the stringer interface (
String() string) with a method which mutates their value, when passed to mock.Mock.On (m.On("Method", <expected>).Return()) or actual argument values passed to mock.Mock.Called may no longer match one another where they previously did match. The behaviour prior to v1.11.0 where the stringer is always called is restored. Future testify releases may not call the stringer method at all in this case.What's Changed
Full Changelog: stretchr/testify@v1.11.0...v1.11.1
v1.11.0Compare Source
What's Changed
Functional Changes
v1.11.0 Includes a number of performance improvements.
Fixes
Documentation, Build & CI
New Contributors
Full Changelog: stretchr/testify@v1.10.0...v1.11.0
Configuration
📅 Schedule: Branch creation - "after 12pm every weekday,before 11am every weekday" in timezone America/New_York, Automerge - 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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.