-
Notifications
You must be signed in to change notification settings - Fork 7
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.
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
Update go dependencies #234
base: main
Are you sure you want to change the base?
Conversation
|
66918d7
to
fd82a48
Compare
e708ca2
to
1ff3b69
Compare
48645bc
to
b7eb03f
Compare
b78c5a6
to
b56ab71
Compare
a10c223
to
2997322
Compare
d60b3f4
to
7dadfca
Compare
2c25981
to
93b195f
Compare
ℹ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
5c82957
to
103e625
Compare
103e625
to
ac105fc
Compare
39016ff
to
4d049cb
Compare
7e25f4c
to
0f5fc6e
Compare
6062cab
to
464b93e
Compare
a48ceee
to
a6648f7
Compare
a6648f7
to
58b0d1d
Compare
7227fb3
to
7cae745
Compare
cf6e799
to
5e8a66e
Compare
5e8a66e
to
4734706
Compare
This PR contains the following updates:
v0.4.0
->v0.5.0
b396bb4
->6c7d1df
v1.3.1
->v1.3.2
v1.5.3
->v1.5.4
v1.15.4
->v1.17.0
v1.4.0
->v1.8.1
v0.26.0
->v0.33.0
v0.26.0
->v0.33.0
v1.60.0
->v1.66.2
v0.13.0
->v0.24.0
Release Notes
docker/go-connections (github.com/docker/go-connections)
v0.5.0
Compare Source
florianl/go-nfqueue (github.com/florianl/go-nfqueue)
v1.3.2
Compare Source
golang/protobuf (github.com/golang/protobuf)
v1.5.4
Compare Source
Notable changes
jhump/protoreflect (github.com/jhump/protoreflect)
v1.17.0
Compare Source
This release deprecates some packages that have newer alternatives in the Protobuf runtime. It also includes some small additions to the
grpcreflect
anddesc/sourceinfo
packages. 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.FindFieldByName
method."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 theprotoparse
package here is just a veneer on top ofprotocompile
and we plan to do as little maintenance as possible here. In a v2 of this repo, this package will no longer be present.protocompile
dependency 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.FindDescriptorByName
has been fixed.sourceinfo.GlobalFiles
registry 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.GlobalFiles
registry and from the variousWrap*
functions had concrete types defined in this package, not in the Protobuf runtime. But theprotoreflect.Descriptor
interface 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 theprotodesc
package 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:
NewClientV1
function to return a client that uses v1 of the server reflection service. This fills the gap in the existing factory functions,NewClientV1Alpha
andNewClientAuto
.AllowFallbackResolver
method to the*grpcreflect.Client
type. 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.v1.16.0
Compare Source
This release adds support for Protobuf Editions to many of the packages. Note, however, that the
desc/protoparse
package does not yet work to parse Protobuf Editions source files. This release also includes a handful of bug-fixes."github.com/jhump/protoreflect/desc"
Additions:
Edition
method to*desc.FileDescriptor
, which returns non-zero for files that use Protobuf Editions (instead of syntax "proto2" or "proto3").Changes/fixes:
Wrap*
functions, that could result in a descriptor hierarchy where the same descriptors were incorrectly present multiple times. This could happen if a file in the transitive dependency graph being wrapped had more than one incoming edge (e.g. same file appearing in import statements from two or more other files)."github.com/jhump/protoreflect/desc/builder"
Additions:
Editions
field andSetEditions
method to*builder.FileBuilder
, for creating files that use Protobuf Editions."github.com/jhump/protoreflect/desc/protoprint"
Changes/fixes:
Printer.CustomSortFunction
was set wherein enum values could be printed in incorrect order, resulting in invalid source output. In syntax "proto3" and in open enums in Protobuf Editions, the first value must be the one with a zero numeric value."github.com/jhump/protoreflect/grpcreflect"
Additions:
AllowMissingFileDescriptors
method to*grpcreflect.Client
that allows users to opt-in to a lenient mode that will try to return schemas even when some files are unavailable. This will only be successful in cases where the missing files only provide custom options or are unused imports. This restores some lenience that was inadvertently provided (due to bugs and missing validation checks) when versions of this repo prior to v1.15 were combined with versions of thegoogle.golang.org/grpc
module prior to v1.61.v1.15.6
Compare Source
This is a bugfix release to address recently identified regressions in the
desc/protoparse
package -- things that worked in v1.14.1 but did not work in v1.15.x."github.com/jhump/protoreflect/desc/protoparse"
Changes/fixes:
Parser.ImportPaths
field specifies that the field is not used for calls to theParser.ParseFilesButDoNotLink
method. This is because import paths do not need to be resolved if not linking. But as of v1.15.0, theImportPaths
field was being used for that method, and the difference in behavior could break existing programs. This has been fixed, and the behavior once again matches the spec.Parser.ParseFiles
were resolved as descriptors (via theParser.LookupImport
orParser.LookupImportProto
functions) instead of as source code (via theParser.Accessor
function or the default action ofos.Open
), the parse operation would fail with a "no such file" error. This would succeed with v1.14.1, with the descriptor being used as the input for the file instead of the file being parsed from source. So working programs could have been broken by an upgrade to v1.15.x. The package has been changed back to the v1.14.1 behavior.v1.15.5
Compare Source
This is a bugfix release to address bugs in the
desc/builder
,desc/protoparse
, andgrpcreflect
packages and a compatibility issue with the most recent version ofgithub.com/bufbuild/protocompile
."github.com/jhump/protoreflect/desc/builder"
Changes/fixes:
"github.com/jhump/protoreflect/desc/protoparse"
Changes/fixes:
github.com/bufbuild/protocompile
package under the hood as the parser. But that package is still using major version zero, since it's API has not completely stabilized. A recent release (v0.8.0) included backwards-incompatible changes that caused this repo to no longer compile. This release addresses the compile errors: this repo now uses that latest release ofprotocompile
and correctly compiles against it.desc/protoparse
package that could cause it to incorrectly accept or reject some Protobuf source files. See the release notes for protocompile v0.8.0 for more details."github.com/jhump/protoreflect/grpcreflect"
Changes/fixes:
grpcreflect.NewClientAuto
function (added in v1.14.0) returns a client that automatically falls back to using v1alpha of the reflection protocol if the server does not support v1. However, it relied on the server returning an "unimplemented" error to decide to fall back, but this condition has been observed to sometimes instead manifest as an "unavailable" error (in proxies that fail to write a 404 error before closing the connection). In those cases, the client was not correctly falling back to v1alpha. This release remedies that, so it can fallback to v1alpha when this category of error occurs.spf13/cobra (github.com/spf13/cobra)
v1.8.1
Compare 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.0
Compare Source
✨ Features
MarkFlagsOneRequired
API 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.SetErrPrefix
andErrPrefix
APIs on theCommand
struct 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.0
Compare Source
✨ Features
bash
,zsh
,pwsh
, &fish
: @h4ck3rk3y #1903🐛 Bug fixes
template
import variable name: @yashLadha #1879🧪 Testing & CI/CD
🔧 Maintenance
stale.yaml
mispellings: @enrichman #1863Vitess
andArewefastyet
to projects using cobra: @frouioui #1932✏️ Documentation
MarkFlagsMutuallyExclusive
example 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.1
Compare Source
Bug fixes 🐛
AddGroup
isn't called beforeAddCommand(my-sub-command)
is executed. This can happen within more complex cobra file structures that have many differentinit
s to be executed. Now, the check for groups has been moved toExecuteC
and 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.0
Compare Source
Summer 2022 Release
Some exciting changes make their way to Cobra! Command completions continue to get better and better (including adding
--help
and--version
automatic flags to the completions list). Grouping is now possible in your help output as well! And you can now use theOnFinalize
method to cleanup things when all "work" is done. Checkout the full changelog below:Features 🌠
ValidateRequiredFlags
andValidateFlagGroups
: @skeetwu #1760--version
flag to help output: @fnickels #1707--help
and--version
flag in completions: @marckhouzam #1813OnFinalize
method: @yann-soubeyrand #1788InitDefaultcompletionCmd
public: @gssbzn #1467Deprecation 👎🏼
ExactValidArgs
is deprecated (but not being removed entirely). This is abit nuanced, so checkout #1643 for further information and the updateduser_guide.md
on how this may affect you (and how you can take advantage of the correct behavior in the validators): @umarcor #1643Bug fixes 🐛
activeHelp
length check syntax: @scop #1762see_also
for yaml documentation: @zregvart #1771Dependencies 🗳️
gopkg.in/yaml.v3
: @tklauser #1766Testing 🤔
action/setup-go
cache: @umarcor #1783workflow_dispatch
to CI actions: @umarcor #1387Docs ✏️
SetContext
documentation: @katexochen #1748go install
for binary: @marckhouzam #1726Misc 💭
exempt
yaml 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/cobra
GitHub 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.0
Compare 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
username
flag that MUST be partnered with apassword
flag. 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.md
as 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-bot
settings - @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.33.0
Compare Source
What's Changed
If you are building Docker images with the
FromDockerfile
struct in theGenericContainerRequest
, please consider that theContextArchive
field in that struct has changed fromio.Reader
toio.ReadSeeker
. This is needed because we want to be able to rewind to do multiple passes when reading all the images that are present in a Dockerfile.🔒 Security
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.