Update go dependencies - autoclosed #411
Closed
Conversation
This file contains 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]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
|
|
renovate
bot
force-pushed
the
renovate/go-dependencies
branch
from
37164e5
to
a40f93d
Compare
ℹ 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/go-dependencies
branch
2 times, most recently
from
fbb176e
to
34e0767
Compare
renovate
bot
force-pushed
the
renovate/go-dependencies
branch
from
34e0767
to
e7a6a03
Compare
renovate
bot
force-pushed
the
renovate/go-dependencies
branch
from
e7a6a03
to
5e4c939
Compare
renovate
bot
changed the title
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:
v0.4.0->v0.5.0447e8c6->d91f02bv1.16.0->v1.17.0v1.4.0->v1.8.1v0.26.0->v0.34.0v0.26.0->v0.34.01.22.4->1.23.3v1.65.0->v1.68.0v1.34.2->v1.35.1v0.13.0->v0.25.0Release Notes
docker/go-connections (github.com/docker/go-connections)
v0.5.0Compare Source
jhump/protoreflect (github.com/jhump/protoreflect)
v1.17.0Compare Source
This release deprecates some packages that have newer alternatives in the Protobuf runtime. It also includes some small additions to the
grpcreflectanddesc/sourceinfopackages. The rest of the changes are bug fixes."github.com/jhump/protoreflect/desc"
Changes:
"google.golang.org/protobuf/reflect/protoreflect"package in the Protobuf runtime. In a v2 of this repo, this package will no longer be present.MessageDescriptor.FindFieldByNamemethod."github.com/jhump/protoreflect/desc/protoparse"
Changes and bugfixes:
"github.com/bufbuild/protocompile"package. There are some behavioral differences that we hope to address with additional API and enhancements toprotocompile. But theprotoparsepackage here is just a veneer on top ofprotocompileand we plan to do as little maintenance as possible here. In a v2 of this repo, this package will no longer be present.protocompiledependency has been updated to use a more recent version of that package. This addresses potential panics when callingParser.ParseButDontLink."github.com/jhump/protoreflect/desc/sourceinfo"
Changes and bugfixes:
sourceinfo.GlobalFiles.FindDescriptorByNamehas been fixed.sourceinfo.GlobalFilesregistry or from the variousWrap*functions could induce panics in user code if querying for non-existent elements. For example, callingmessageDescriptor.Fields().ByNumber(123)could return a typed-nil value on failure, instead of a nil interface. This would result in nil-dereference panics if methods were called on this later. These have been fixed.sourceinfo.GlobalFilesregistry and from the variousWrap*functions had concrete types defined in this package, not in the Protobuf runtime. But theprotoreflect.Descriptorinterface has a "do not implement" marker, indicating that concrete types implementing the interface should not be implemented outside of that module. To avoid future issues with the Protobuf runtime, there are no more implementations in this repo. Instead of wrapping other descriptor implementations (via embedding, and then overriding some methods), this package now builds new descriptors, using theprotodescpackage in the Protobuf runtime module.Wrap*functions are now deprecated. The name is no longer accurate since they no longer return wrapper values. Also the new implementation, which builds new descriptors, can fail (though unlikely), but the existing signature of these functions did not allow for returning an error. So these functions could possibly panic in the face of malformed input descriptors. Users should use the newAddSourceInfoTo*versions of these functions instead.Additions:
AddSourceInfoTo*functions to replace theWrap*functions. These functions augment the input descriptors by adding source code information to them."github.com/jhump/protoreflect/dynamic"
Changes:
"google.golang.org/protobuf/types/dynamicpb"package in the Protobuf runtime. In a v2 of this repo, this package will no longer be present."github.com/jhump/protoreflect/grpcreflect"
Additions:
NewClientV1function to return a client that uses v1 of the server reflection service. This fills the gap in the existing factory functions,NewClientV1AlphaandNewClientAuto.AllowFallbackResolvermethod to the*grpcreflect.Clienttype. This allows the client to be configured with an alternate resolver that can be used as a backup when trying to satisfy dependencies, for cases where the remote server is non-authoritative and unable to provide all of them.spf13/cobra (github.com/spf13/cobra)
v1.8.1Compare Source
✨ Features
🐛 Bug fixes
🔧 Maintenance
🧪 Testing & CI/CD
✏️ Documentation
New Contributors
Thank you everyone who contributed to this release and all your hard work! Cobra and this community would never be possible without all of you!!!! 🐍
Full Changelog: spf13/cobra@v1.8.0...v1.8.1
v1.8.0Compare Source
✨ Features
MarkFlagsOneRequiredAPI for flags which can be used to mark a flag group as required and cause command failure if at least one is not used when invoked.SetErrPrefixandErrPrefixAPIs on theCommandstruct to allow for setting a custom prefix for errors🐛 Bug fixes
🔧 Maintenance
🧪 Testing & CI/CD
✏️ Documentation
Thank you everyone who contributed to this release and all your hard work! Cobra and this community would never be possible without all of you!!!! 🐍
Full Changelog: spf13/cobra@v1.7.0...v1.8.0
v1.7.0Compare Source
✨ Features
bash,zsh,pwsh, &fish: @h4ck3rk3y #1903🐛 Bug fixes
templateimport variable name: @yashLadha #1879🧪 Testing & CI/CD
🔧 Maintenance
stale.yamlmispellings: @enrichman #1863VitessandArewefastyetto projects using cobra: @frouioui #1932✏️ Documentation
MarkFlagsMutuallyExclusiveexample in user guide: @janhn #1904shell_completions.md: @gusega #1907This release contains several long running fixes, improvements to powershell completions, and further optimizations for completions.
Thank you everyone who contributed to this release and all your hard work! Cobra and this community would never be possible without all of you! 🐍
Full changelog: spf13/cobra@v1.6.1...v1.7.0
v1.6.1Compare Source
Bug fixes 🐛
AddGroupisn't called beforeAddCommand(my-sub-command)is executed. This can happen within more complex cobra file structures that have many differentinits to be executed. Now, the check for groups has been moved toExecuteCand provides more flexibility when working with grouped commands - @marckhouzam (and shout out to @aawsome, @andig and @KINGSABRI for a deep investigation into this! 👏🏼)v1.6.0Compare Source
Summer 2022 Release
Some exciting changes make their way to Cobra! Command completions continue to get better and better (including adding
--helpand--versionautomatic flags to the completions list). Grouping is now possible in your help output as well! And you can now use theOnFinalizemethod to cleanup things when all "work" is done. Checkout the full changelog below:Features 🌠
ValidateRequiredFlagsandValidateFlagGroups: @skeetwu #1760--versionflag to help output: @fnickels #1707--helpand--versionflag in completions: @marckhouzam #1813OnFinalizemethod: @yann-soubeyrand #1788InitDefaultcompletionCmdpublic: @gssbzn #1467Deprecation 👎🏼
ExactValidArgsis deprecated (but not being removed entirely). This is abit nuanced, so checkout #1643 for further information and the updateduser_guide.mdon how this may affect you (and how you can take advantage of the correct behavior in the validators): @umarcor #1643Bug fixes 🐛
activeHelplength check syntax: @scop #1762see_alsofor yaml documentation: @zregvart #1771Dependencies 🗳️
gopkg.in/yaml.v3: @tklauser #1766Testing 🤔
action/setup-gocache: @umarcor #1783workflow_dispatchto CI actions: @umarcor #1387Docs ✏️
SetContextdocumentation: @katexochen #1748go installfor binary: @marckhouzam #1726Misc 💭
exemptyaml keys: @jpmcb #1800Note: Per #1804, we will be moving away from "seasonal" releases and doing more generic point release targets. Continue to track the milestones and issues in the
spf13/cobraGitHub repository for more information!Great work everyone! Cobra would never be possible without your contributions! 🐍
Full Changelog: spf13/cobra@v1.5.0...v1.6.0
v1.5.0Compare Source
Spring 2022 Release 🌥️
Hello everyone! Welcome to another release of cobra. Completions continue to get better and better. This release adds a few really cool new features. We also continue to patch versions of our dependencies as they become available via dependabot. Happy coding!
Active help 👐🏼
Shout out to @marckhouzam for a big value add: Active Help https://github.com/spf13/cobra/pull/1482. With active help, a program can provide some inline warnings or hints for users as they hit tab. Now, your CLIs can be even more intuitive to use!
Currently active help is only supported for bash V2 and zsh. Marc wrote a whole guide on how to do this, so make sure to give it a good read to learn how you can add this to your cobra code! https://github.com/spf13/cobra/blob/master/active_help.md
Group flags 🧑🏼🤝🧑🏼
Cobra now has the ability to mark flags as required or exclusive as a group. Shout out to our newest maintainer @johnSchnake for this! https://github.com/spf13/cobra/pull/1654 Let's say you have a
usernameflag that MUST be partnered with apasswordflag. Well, now, you can enforce those as being required together:Flags may also be marked as "mutally exclusive" with the
MarkFlagsMutuallyExclusive(string, string ... )command API. Refer to our user guide documentation for further info!Completions 👀
Documentation 📝
CHANGELOG.mdas it isn't updated - @johnSchnake https://github.com/spf13/cobra/pull/1634shell_completion.md- @danieldn https://github.com/spf13/cobra/pull/1678Testing & CI ⚙️
RICHGO_FORCE_COLOR- @umarcor https://github.com/spf13/cobra/pull/1647stale-botsettings - @jpmcb https://github.com/spf13/cobra/pull/1609Beep boop, bot commits 🤖
Misc 💭
errors.Is()to check for errors - @Luap99 https://github.com/spf13/cobra/pull/1730Shoutout to ALL our contributors (and all the new first time contributors!!) - great work everyone!! Cobra and it's huge impact wouldn't be possible without you 👏🏼 🚀 🐍
Full Changelog: spf13/cobra@v1.4.0...v1.5.0
testcontainers/testcontainers-go (github.com/testcontainers/testcontainers-go)
v0.34.0Compare Source
What's Changed
🚀 Features
🐛 Bug Fixes
📖 Documentation
🧹 Housekeeping
ContainsorErrorContainswith testify (#2839) @mmorel-35📦 Dependency updates
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ 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 was generated by Mend Renovate. View the repository job log.