Update all non-major dependencies #100
Open
+107
−67
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
ℹ 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/all-minor-patch
branch
4 times, most recently
from
1458ac9 to
ab97849
Compare
renovate-bot
force-pushed
the
renovate/all-minor-patch
branch
from
ab97849 to
649a7e8
Compare
ywmei-brt1
approved these changes
Oct 1, 2024
renovate-bot
force-pushed
the
renovate/all-minor-patch
branch
8 times, most recently
from
b1b5b52 to
af14a27
Compare
renovate-bot
force-pushed
the
renovate/all-minor-patch
branch
6 times, most recently
from
1d6a692 to
e37633e
Compare
renovate-bot
force-pushed
the
renovate/all-minor-patch
branch
3 times, most recently
from
d53fd24 to
29369a0
Compare
banikharbanda
approved these changes
Oct 22, 2024
renovate-bot
force-pushed
the
renovate/all-minor-patch
branch
3 times, most recently
from
a297f7f to
b96daef
Compare
banikharbanda
approved these changes
Oct 23, 2024
renovate-bot
force-pushed
the
renovate/all-minor-patch
branch
from
b96daef to
5570545
Compare
renovate-bot
force-pushed
the
renovate/all-minor-patch
branch
7 times, most recently
from
d3b286c to
c2502b6
Compare
renovate-bot
force-pushed
the
renovate/all-minor-patch
branch
11 times, most recently
from
1fbf616 to
e69451d
Compare
renovate-bot
force-pushed
the
renovate/all-minor-patch
branch
5 times, most recently
from
cba6b0d to
f0dd67f
Compare
renovate-bot
force-pushed
the
renovate/all-minor-patch
branch
5 times, most recently
from
a44c6c3 to
1ee8dfe
Compare
renovate-bot
force-pushed
the
renovate/all-minor-patch
branch
from
1ee8dfe to
9ecba54
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:
0.9.1->0.12.0v1.22.0->v1.22.1v1.43.0->v1.49.0v1.11.2->v1.11.3v0.24.0->v0.25.0v0.28.0->v0.29.0v0.28.0->v0.29.0v0.213.0->v0.215.0v1.68.0->v1.69.2v1.36.0->v1.36.21.63.1->1.69.02.0.7->2.2.3v1.5.2->v1.5.629.1->29.20.0.17->0.1.01.3.1.bcr.3->1.3.1.bcr.4Release Notes
bazel-contrib/setup-bazel (bazel-contrib/setup-bazel)
v0.12.0Compare Source
What's Changed
New Contributors
Full Changelog: bazel-contrib/setup-bazel@0.11.0...0.12.0
v0.11.0Compare Source
What's Changed
BAZELISK_GITHUB_TOKENvariable by @p0deje in https://github.com/bazel-contrib/setup-bazel/pull/58Full Changelog: bazel-contrib/setup-bazel@0.10.0...0.11.0
v0.10.0Compare Source
What's Changed
Full Changelog: bazel-contrib/setup-bazel@0.9.1...0.10.0
googleapis/google-api-go-client (google.golang.org/api)
v0.215.0Compare Source
Features
v0.214.0Compare Source
Features
grpc/grpc-go (google.golang.org/grpc)
v1.69.2: Release 1.69.2Compare Source
Bug Fixes
Metrics/etc) that were moved to the stats package (#7929).v1.69.0: Release 1.69.0Compare Source
Known Issues
grpc.NewClientfunction is incompatible with forward proxies, because it resolves the target hostname on the client instead of passing the hostname to the proxy. A fix is expected to be a part of grpc-go v1.70. (#7556)New Features
pickfirstLB policy (disabled by default) supports Happy Eyeballs, interleaving IPv4 and IPv6 address as described in RFC-8305 section 4, to attempt connections to multiple backends concurrently. The experimentalpickfirstpolicy can be enabled by setting the environment variableGRPC_EXPERIMENTAL_ENABLE_NEW_PICK_FIRSTtotrue. (#7725, #7742)pick_firstload balancing policy (#7839)MethodHandler, which is the type of an already-exported field inMethodDesc(#7796)Bug Fixes
Behavior Changes
pick_firstLB policy to manage connections (#7826)API Changes
balancer.SubConninterface to force implementors to embed a delegate implementation. This requirement is present in the interface documentation, but wasn't enforced earlier. (#7840)Performance Improvements
ReadAll()method for more efficientio.Readerconsumption (#7653)Documentation
v1.68.2: Release 1.68.2Compare Source
Dependencies
stats/opentelemetrymodule and instead add the experimental packages it contains directly into the maingoogle.golang.org/grpcmodule (#7936)v1.68.1: Release 1.68.1Compare Source
Bug Fixes
Dependencies
go1.22.7togo1.22. (#7831)protocolbuffers/protobuf-go (google.golang.org/protobuf)
v1.36.2Compare Source
Full Changelog: protocolbuffers/protobuf-go@v1.36.1...v1.36.2
Bug fixes:
CL/638515: internal/impl: fix WhichOneof() to work with synthetic oneofs
v1.36.1Compare Source
Full Changelog: protocolbuffers/protobuf-go@v1.36.0...v1.36.1
Bug fixes:
CL/638495: internal/impl: revert IsSynthetic() check to fix panic
Maintenance:
CL/637475: internal/errors: delete compatibility code for Go before 1.13
zlib-ng/zlib-ng (llvm_zlib)
v2.2.3Compare Source
New Years release, zlib-ng's 10 years celebration
My first commit in this repo was in October 8th 2014, although I do remember that I started during summer vacation and had made the zlib cleanup more of a mess than I wanted, so I restarted from scratch in October when I had gotten a better overview of the code and what I wanted to do to clean it up. At that point zlib-ng was not very likely to go anywhere, but despite the odds, over time several people found it and opened PRs with their own improvements, a few of those became long-time contributors, and a few years ago zlib-ng finally became more than an experimental fork. Zlib-ng has since gained traction and several distros have started replacing stock zlib with zlib-ng in compat mode.
The past year we have been lucky enough to have received donations so that we were able to invest in a couple Rpi5 systems for testing, and we are looking forward to hopefully being able to acquire more architectures for development and testing, Risc-V would be interesting for example, and we are lacking a dedicated testing machine capable of AVX512.
Release 2.2.3
This time we have two code fixes for potentially unsafe access, although we have not had any bug-reports about these.
It also contains several optimizations. Especially of note, inflate has been optimized on various instruction sets and also the generic C code has seen improvements, and we have improvements for arches where unaligned accesses are not possible (lacking instructions to handle unaligned access) and also improvements on big endian.
Example benchmarks:
x86-64 AVX2: Inflate ~17.8% faster, Deflate unchanged. -4.6KB library size.
Aarch64: Inflate ~2.3% faster, Deflate unchanged. - 5.5KB library size.
We also took some time to do a comprehensive cleanup of the now misleading UNALIGNED_OK option and of all the "unaligned" functions. We have noticed that some distros have been disabling these, fearing they are using potentially unsafe unaligned pointers, but we already fixed that in 2.1.0-beta1. Since then, these "unaligned" settings/functions have been referring to using unaligned accesses in safe ways, like utilizing unaligned intrinsics or memcpy to fix alignment for example and selecting what safe method is optimal to the arch. So disabling that instead disabled several safe optimizations.
Because this was obviously misleading certain distros into disabling these optimizations, we have cleaned it up, removed a lot of unnecessary preprocessor checks, and made detection of optimal methods happen during compile instead of configure. As a bonus, this cleaned up a lot of code and also let us not compile in many extra variants of compare256/longest_match, saving about 8-10KB of library size.
Changes
Fixes for potentially unsafe access
Optimizations / Cleanups
Big Endian
Buildsys fixes / minor fixes
CI
v2.2.2Compare Source
This release fixes a corruption bug with the inflateback implementation, this was
detected by Docker using pigz w/zlib-ng to decompress a 25GB image file and failing CRC.
Since this is so far the only known way to trigger the bug, it seems to be hard to hit.
Most of the rest are minor changes to avoid triggering warnings in MSVC or optional
warnings in other compilers, as well as a few minor fixes to the buildsystem and CI.
Changes
Important Fixes
Buildsystem
CI/Test
Misc
S390x
RISC-V
v2.2.1Compare Source
This is the first stable release of the 2.2.x branch
Please read the changelog for the 2.2.0 Release Candidate if you didn't already, especially if your software gives zlib-ng a custom allocator.
No bugreports came in during 2.2.0 RC testing, so the only change in 2.2.1 is a small fix for Configure that was already in the pipe:
v2.2.0: Release CandidateCompare Source
This release contains several larger changes and optimizations. On x86-64 for example, this leads to a compression speedup of ~12% on default level.
We also have a major reorganization of memory alloc/free to always happen during init, this allows applications to potentially do the init early and be finished with the malloc system calls before it needs to process latency sensitive compression/decompression. It also ensures that zlib-ng can not fail due to memory pressure after having run the init functions successfully. We also now only do a single memory allocation deflate or inflate, ensuring we do less system calls and the allocated buffers live close together in memory.
Compression or decompression of very small buffers will now also be faster due to spending less time doing malloc/free.
The downside to this is that decompression will now always allocate the maximum required memory (~42KB total on 64-bit platforms), previously it would allocate (and potentially free) memory as needed during decompression.
It also means that applications that replace the alloc/free functions with their own can potentially have some issues (Yes I am looking at you Nginx).
Changes
Buildsystem
CI/Test
Cleanup
Refactoring and Optimizations
ARM
Power
RVV
S390x
x86
Misc
v2.1.8Compare Source
This backport release fixes a corruption bug with the inflateback implementation, this was
detected by Docker using pigz w/zlib-ng to decompress a 25GB image file and failing CRC.
Since this is so far the only known way to trigger the bug, it seems to be hard to hit.
Most of the rest are minor changes to avoid triggering warnings in MSVC or optional
warnings in other compilers, as well as a few minor fixes to the buildsystem and CI.
Other changes
Important Fixes
Buildsystem
CI/Test
Misc
S390x
RISC-V
v2.1.7Compare Source
Due to the high amount of refactoring changes in
develop, I have decided to target those to a new version branch2.2.x.There is also a lot of fixes and minor improvements, so those will be backported and released as 2.1.7.
To work around the #1708 issue (incompatibility with applications mis-using the zlib zalloc/zfree API), #1710 is merged instead of backporting the much bigger #1713.
Backported Changes
Buildsystem
CI/Test
Cleanup
Refactoring and Optimizations
ARM
Power
RVV
S390x
x86
Misc
v2.1.6Compare Source
This is a stable release, with several minor improvements and one corruption fix for inflateCopy().
This release also improves on the functable implementation, and also moves its initialization to happen in deflateInit() and inflateInit(). We also have some optimizations for RVV and ARM.
Notes for packagers:
INSTALL_LIB_DIRworkarounds, this should not be needed since v2.0.2 (2021), but packagers seem to keep copying the workaround from each other. Please see cmake/detect-install-dirs.cmake.Changes
Functable
API
ARM
RVV
x86
Buildsystem
Misc
v2.1.5Compare Source
This is a hotfix release, fixing an issue where certain applications would fail with a checksum error during inflate (decompression).
A few minor fixes and improvements are also included.
Fix bug with Z_FINISH handling with no window. #1602
Added unit test for inflate with Z_FINISH and no window #1603
Fix CMake handling of CMAKE_INSTALL_INCLUDEDIR #1593
Fix pkgconfig support for WITH_GZFILEOP #1595 #1598
Github Actions update #1590
Readme Update #1594
v2.1.4Configuration
📅 Schedule: Branch creation - "* 0-3 * * 1" (UTC), 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.