chore(deps): update all #49
Open
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/all
branch
5 times, most recently
from
16f6047
to
8e86711
Compare
renovate
bot
force-pushed
the
renovate/all
branch
6 times, most recently
from
9de1928
to
b1fdec3
Compare
renovate
bot
force-pushed
the
renovate/all
branch
8 times, most recently
from
dae384b
to
7e3b7e9
Compare
renovate
bot
force-pushed
the
renovate/all
branch
7 times, most recently
from
92d8a25
to
b5fa034
Compare
renovate
bot
force-pushed
the
renovate/all
branch
3 times, most recently
from
78e0542
to
e6d8497
Compare
renovate
bot
force-pushed
the
renovate/all
branch
3 times, most recently
from
45eaa03
to
57e5cff
Compare
renovate
bot
force-pushed
the
renovate/all
branch
2 times, most recently
from
25c61c8
to
2b67b79
Compare
renovate
bot
force-pushed
the
renovate/all
branch
2 times, most recently
from
7e08fb3
to
148dc9b
Compare
renovate
bot
force-pushed
the
renovate/all
branch
3 times, most recently
from
3c830c1
to
5dcbee0
Compare
renovate
bot
force-pushed
the
renovate/all
branch
4 times, most recently
from
159ad99
to
61ea461
Compare
renovate
bot
force-pushed
the
renovate/all
branch
2 times, most recently
from
e3b62f8
to
ca351a0
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
ca351a0
to
a4b8c24
Compare
renovate
bot
force-pushed
the
renovate/all
branch
2 times, most recently
from
72f7e3f
to
b61b2d1
Compare
renovate
bot
force-pushed
the
renovate/all
branch
4 times, most recently
from
f7a00c7
to
5e4a31b
Compare
renovate
bot
force-pushed
the
renovate/all
branch
2 times, most recently
from
fa30a75
to
7c322ad
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
7c322ad
to
289c2a9
Compare
renovate
bot
force-pushed
the
renovate/all
branch
2 times, most recently
from
b3d3642
to
8ee793d
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
8ee793d
to
5d04e61
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:
3.13->3.20~1.1.2->~1.2.01.0.5->1.2.50.5.13->0.6.1v4.0.2+incompatible->v4.1.3v0.3.0->v0.4.0v1.3.2->v1.5.4v1.4.3-0.20191204093753-683f8725b6d0->v1.7.0v1.7.3->v1.8.1v1.1.0->v1.4.0v1.12.1->v1.16.0v1.9.11->v1.9.16v0.8.1->v0.9.1v1.7.0->v1.11.1v2.6.1->v2.21.10ad062e->673ab2cv1.22.2->v1.22.16~4.0.2->~4.5.0v1.13.0->v1.27.01.19-alpine->1.23-alpinev0.0.0-20191206172530-e9b2fee46413->v0.29.00243a4b->65e8d210.0.10->0.0.14~0.7.6->~0.8.0~0.2.3->~0.6.0~0.5.0->~0.7.0~0.4.0->~0.5.0~0.8.0->~0.11.0~0.5.0->~0.8.0~0.2.0->~0.5.0~0.10.0->~0.14.0~0.12.0->~0.15.0~0.2.0->~0.12.0~0.10.0->~0.12.0~0.11.3->~0.12.0~0.3.0->~0.7.0~0.5.1->~0.7.00.2.7->0.11.1~0.5.0->~0.11.0~0.6.0->~0.8.0~8.1.0->~8.6.01.13.0->1.16.0v1.3.0->v1.7.0v1.4.0->v1.6.1~0.10.1->~0.12.0~0.3.2->~0.4.0Release Notes
go-chi/chi (github.com/go-chi/chi)
v4.1.3Compare Source
v4.1.2Compare Source
v4.1.2+incompatibleCompare Source
v4.1.1Compare Source
route to the correct handler through a recursive tree search, thanks to @Jahaja for the PR/fix!
v4.1.1+incompatibleCompare Source
v4.1.0Compare Source
and an extra interface type useful for custom logger implementations.
v4.1.0+incompatibleCompare Source
v4.0.4Compare Source
v4.0.4+incompatibleCompare Source
v4.0.3Compare Source
v4.0.3+incompatibleCompare Source
gobuffalo/packd (github.com/gobuffalo/packd)
v0.4.0Compare Source
golang/protobuf (github.com/golang/protobuf)
v1.5.4Compare Source
Notable changes
v1.5.3Compare Source
Notable changes
*( #1363) jsonpb: accept 'null' as a valid representation of NullValue in unmarshal
v1.5.2Compare Source
Notable changes:
v1.5.1Compare Source
Notable changes:
v1.5.0Compare Source
Overview
This marks the
ptypespackage as deprecated and upgrades the dependency ongoogle.golang.org/protobufto a pre-release version of v1.26.0. A subsequent patch release will update the dependency to v1.26.0 proper.Notable changes
v1.4.3Compare Source
Notable changes:
v1.4.2Compare Source
Notable changes:
v1.4.1Compare Source
Notable changes:
v1.4.0Compare Source
DescriptormethodsgeneratorpackageOverview
This release of the
github.com/golang/protobufmodule introduces a number of significant changes relative to the previous minor release. In particular, this module is now implemented in terms of the newgoogle.golang.org/protobufmodule, which is the next major revision of Go bindings for protocol buffers. From this point onwards, most of the development effort for Go protobufs will be dedicated to the new module, with minimal changes being made to this module.See the release notes for the new module for specific implementation details that may affect this release.
Backwards compatibility
This release maintains backwards compatibility with previous releases of this module. Any observable changes in behavior are to fix bugs, change unspecified behavior, or to make behavior more compliant with the protobuf specification. The compatibility document provides us the freedom to make changes in these areas.
Notable changes
Wire serialization
Wire serialization is now implemented in terms of the new
protopackage by calling out to the relevant functionality in that package (e.g.,proto.Marshalandproto.Unmarshal). There should be no observable changes in behavior other what is mentioned elsewhere in the release notes (e.g., behavior around errors or nil values).JSON and text serialization
The JSON and text format implementations have been ported to use protobuf reflection under the hood instead of relying on Go reflection. This provides flexibility as they can operate on any concrete message type that properly implements the new
proto.Messageinterface.The implementations do not use the new
protojsonorprototextpackages in order to maintain a higher degree of backwards compatibility. Our analysis unfortunately showed us that too many tests rely on their output being stable by performing byte-for-byte comparisons. Even though the compatibility promise gives us the freedom to change the output, we have chosen not to do so for pragmatic reasons. The implementations are now functionally frozen (bugs and all) and will not receive future improvements. Users are encouraged to migrate to theprotojsonorprototextpackages instead.Well-known types
The well-known types declared under
ptypesare moved to thegoogle.golang.org/protobufmodule. The packages continue to exist, but all declarations forward to ones in the new module.For a period of time, it is expected that the
protoc-gen-goplugin continues to generate code with dependencies on the well-known types in this module. The import paths for the well-known types are determined by thego_packageoption specified in the.protofiles. Since these files are managed by the main protocol buffers project, it will require a new release of the protobuf toolchain before the new import paths take effect. Depending on this module’s packages for well-known types is fine since they simply forward over to the new packages.While
descriptorandpluginare not packages for well-known types, they too have also been moved to the new module.Types registry
In order for dynamic usages of protobufs to operate correctly, there must be a unified registry between this module and the new
google.golang.org/protobufmodule. Theprotoregistrypackage is the primary registry for all protobuf files that are linked into a Go program. The registration functions (e.g.,proto.RegisterType) in this package forward to the global registries in that module, and the lookup functions (e.g.,proto.MessageType) in this package source from the global registries in that module.Nil values
Use of the
google.golang.org/protobufmodule for the underlying implementation means that semantics for nil values may have changed. See that module’s release notes for details.Errors
A consequence of using the
google.golang.org/protobufmodule as the underlying implementation means that the text for some errors may change in trivial ways. This may break brittle tests depending on the error message. See that module’s release notes for details.Generated code
The
protoc-gen-goplugin in this module is now a thin wrapper over theprotoc-gen-goplugin in thegoogle.golang.org/protobufmodule. As a result, there are many changes to the generated code. See that module’s release notes for details. Users should migrate to use the newprotoc-gen-goplugin instead of the old one. Code generated by either plugin should be compatible with either module.For backward compatibility purposes, the
protoc-gen-goplugin in this module continues to support generation of gRPC bindings, while theprotoc-gen-goplugin in the new module does not.Upcoming breakage changes
Per the compatibility agreement for Go protobufs, we promise to make announcements about deliberate or potentially breaking changes 6 months in advance.
None of these changes are effective yet in this release.
Deprecation of
DescriptormethodsThe
Descriptormethods on generated messages are deprecated and may be removed in the future.The
descriptor.Messagetype is deprecated as fewer and fewer message types in the future will implement thedescriptor.Messageinterface. Existing usages should migrate to the newproto.Messageinterface.The
descriptor.ForMessagefunction is also deprecated. Users should migrate the code to use protobuf reflection to access descriptor information.Removal of
generatorpackageThe
generatorpackage is an internal implementation detail ofprotoc-gen-goand existed before the internal package mechanism. It has long been exempt from the compatibility promise. A future release of this module will remove the package. Existing users must migrate to the newcompiler/protogenpackage, which is a stable API for implementing protoc plugins, or fork the existinggeneratorpackage.Similarly, the
grpcpackage is also an internal implementation detail ofprotoc-gen-goand will also be deleted in a future release of this module.v1.3.5Compare Source
Notable changes:
go.modGo version togo 1.9.v1.3.4Compare Source
Notable changes:
google/protobuf/*.prototogithub.com/protocolbuffers/protobufv3.11.4.protoc-gen-gooutput to avoid post-gofmtvariation between go1.13 and go1.14.v1.3.3Compare Source
Notable changes:
googollee/go-socket.io (github.com/googollee/go-socket.io)
v1.7.0: Add DB option for Redis adapterCompare Source
v1.6.3Compare Source
Minor fix:
v1.6.2Compare Source
Changelog
v1.6.1Compare Source
v1.6.0: Changes API redis adapter with backward compatibilityCompare Source
v1.5.1: Add errors and cast checkCompare Source
v1.5.0: Refactor main codeCompare Source
v1.4.5: Fix: bug into uuid generateCompare Source
v1.4.4: Multiple improvements, move go-engine.io to go-socket.io repoCompare Source
Making a release here since it was a long time since we made the latest release. Includes bug fixes and a consolidation from to packages into one.
gorilla/mux (github.com/gorilla/mux)
v1.8.1Compare Source
What's Changed
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 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.