deps(deps): update all non-major dependencies#447
Open
renovate[bot] wants to merge 1 commit intomainfrom
Open
Conversation
![renovate-approve[bot]](https://avatars.githubusercontent.com/in/7394?s=60&v=4){kind=small}
dosubot
bot
added
the
size:XS
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
219ea24 to
c2d6cc9
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
c2d6cc9 to
1186965
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
1186965 to
ec5eb71
Compare
Contributor
Author
ℹ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
dosubot
bot
removed
the
size:XS
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
ec5eb71 to
63450bb
Compare
dosubot
bot
removed
the
size:S
dosubot
bot
added
the
size:M
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
63450bb to
4f965d4
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
8a88bd0 to
2331416
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
6bca6f3 to
80f6d7d
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
80f6d7d to
7d4e25c
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
7d4e25c to
339a44d
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
339a44d to
54fec25
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
54fec25 to
b5b66f5
Compare
Contributor
Author
|
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
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
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.17.0-20240205164452-95dfd137cb54.1→v1.19.1-20240205164452-95dfd137cb54.2v1.35.2-20240205164452-95dfd137cb54.1→v1.36.11-20240205164452-95dfd137cb54.1v1.17.0→v1.19.1v1.4.2→v1.4.3v2.22.0→v2.28.1v1.36.0→v1.39.1v0.15.0→v0.20.0v0.3.3→v0.3.5v0.31.3→v0.35.3v0.31.3→v0.35.3v0.31.3→v0.35.3v2.130.1→v2.140.0v1.8.5→v1.12.4v0.19.2→v0.23.3v1.4.0→v1.6.0Release Notes
connectrpc/connect-go (connectrpc.com/connect)
v1.19.1Compare Source
What's Changed
Bugfixes
Full Changelog: connectrpc/connect-go@v1.19.0...v1.19.1
v1.19.0Compare Source
This release introduces the highly requested "simple" flag for code generation, making Connect significantly more ergonomic for everyday RPC development.
The new simple flag in protoc-gen-connect-go generates cleaner, more intuitive client and handler interfaces that eliminate request/response wrappers for most use cases. This addresses community feedback about verbosity and provides a more straightforward API. When enabled, metadata (headers/trailers) can be passed through context instead of explicit wrapper objects, optimizing for the common case where developers don't need direct access to HTTP headers.
What's Changed
Enhancements
golang.org/x/net/http2by @maxbrunet in #873, #877Bugfixes
Other changes
#880
New Contributors
Full Changelog: connectrpc/connect-go@v1.18.1...v1.19.0
v1.18.1Compare Source
What's Changed
Bugfixes
Full Changelog: connectrpc/connect-go@v1.18.0...v1.18.1
v1.18.0Compare Source
What's Changed
Enhancements
package_suffixoption toprotoc-gen-connect-goto allow specifying the output directory of generated code by @bufdev and @emcfarlane in #803Other changes
New Contributors
Full Changelog: connectrpc/connect-go@v1.17.0...v1.18.0
go-logr/logr (github.com/go-logr/logr)
v1.4.3Compare Source
Minor release.
What's Changed
New Contributors
Full Changelog: go-logr/logr@v1.4.2...v1.4.3
onsi/ginkgo (github.com/onsi/ginkgo/v2)
v2.28.1Compare Source
2.28.1
Update all dependencies. This auto-updated the required version of Go to 1.24, consistent with the fact that Go 1.23 has been out of support for almost six months.
v2.28.0Compare Source
2.28.0
Ginkgo's SemVer filter now supports filtering multiple components by SemVer version:
can be filtered in or out with an invocation like:
ginkgo --sem-ver-filter="2.1.1, redis=8.2.0"Huge thanks to @Icarus9913 for working on this!
v2.27.5Compare Source
2.27.5
Fixes
Don't make a new formatter for each GinkgoT(); that's just silly and uses precious memory
v2.27.4Compare Source
2.27.4
Fixes
59bc751]v2.27.3Compare Source
2.27.3
Fixes
report exit result in case of failure [
1c9f356]fix data race [
ece19c8]v2.27.2Compare Source
2.27.2
Fixes
a69113a]Maintenance
a99c6e0]f993df5]v2.27.1Compare Source
2.27.1
Fixes
606c1cb]a6463b3]v2.27.0Compare Source
2.27.0
Features
Transforming Nodes during Tree Construction
This release adds support for
NodeArgsTransformers that can be registered withAddTreeConstructionNodeArgsTransformer.These are called during the tree construction phase as nodes are constructed and can modify the node strings and decorators. This enables frameworks built on top of Ginkgo to modify Ginkgo nodes and enforce conventions.
Learn more here.
Spec Prioritization
A new
SpecPriority(int)decorator has been added. Ginkgo will honor priority when ordering specs, ensuring that higher priority specs start running before lower priority specsLearn more here.
Maintenance
1333dae]17ae63e]v2.26.0Compare Source
2.26.0
Features
Ginkgo can now generate json-formatted reports that are compatible with the
go testjson format. Useginkgo --gojson-report=report.go.json. This is not intended to be a replacement for Ginkgo's native json format which is more information rich and better models Ginkgo's test structure semantics.v2.25.3Compare Source
2.25.3
Fixes
f01aed1]v2.25.2Compare Source
2.25.2
Fixes
Add github output group for progress report content
Maintenance
Bump Gomega
v2.25.1Compare Source
2.25.1
Fixes
10866d3]2e42cff]v2.25.0Compare Source
2.25.0
AroundNodeThis release introduces a new decorator to support more complex spec setup usecases.
AroundNoderegisters a function that runs before each individual node. This is considered a more advanced decorator.Please read the docs for more information and some examples.
Allowed signatures:
AroundNode(func())-funcwill be called before the node is run.AroundNode(func(ctx context.Context) context.Context)-funccan wrap the passed in context and return a new one which will be passed on to the node.AroundNode(func(ctx context.Context, body func(ctx context.Context)))-ctxis the context for the node andbodyis a function that must be called to run the node. This gives you complete control over what runs before and after the node.Multiple
AroundNodedecorators can be applied to a single node and they will run in the order they are applied.Unlike setup nodes like
BeforeEachandDeferCleanup,AroundNodeis guaranteed to run in the same goroutine as the decorated node. This is necessary when working with lower-level libraries that must run on a single thread (you can callruntime.LockOSThread()in theAroundNodeto ensure that the node runs on a single thread).Since
AroundNodeallows you to modify the context you can also useAroundNodeto implement shared setup that attaches values to the context.If applied to a container,
AroundNodewill run before every node in the container. Including setup nodes likeBeforeEachandDeferCleanup.AroundNodecan also be applied toRunSpecsto run before every node in the suite. This opens up new mechanisms for instrumenting individual nodes across an entire suite.v2.24.0Compare Source
2.24.0
Features
Specs can now be decorated with (e.g.)
SemVerConstraint("2.1.0")andginkgo --sem-ver-filter="2.1.1"will only run constrained specs that match the requested version. Learn more in the docs here! Thanks to @Icarus9913 for the PR.Fixes
3f5d379]. fixes #1582Maintenance
Numerous dependency bumps and documentation fixes
v2.23.4Compare Source
2.23.4
Prior to this release Ginkgo would compute the incorrect number of available CPUs when running with
-pin a linux container. Thanks to @emirot for the fix!Features
2b9c428]Fixes
1f59d07]Maintenance
2d134d5]v2.23.3Compare Source
2.23.3
Fixes
-as a standalone argument [cfcc1a5]feaf292]88e2282]v2.23.2Compare Source
2.23.2
🎉🎉🎉
At long last, some long-standing performance gaps between
ginkgoandgo testhave been resolved!Ginkgo operates by running
go test -cto generate test binaries, and then running those binaries. It turns out that the compilation step ofgo test -cis slower thango test's compilation step becausego teststrips out debug symbols (ldflags=-w) whereasgo test -cdoes not.Ginkgo now passes the appropriate
ldflagstogo test -cwhen running specs to strip out symbols. This is only done when it is safe to do so and symbols are preferred when profiling is enabled and whenginkgo buildis called explicitly.This, coupled, with the instructions for disabling XProtect on MacOS yields a much better performance experience with Ginkgo.
v2.23.1Compare Source
2.23.1
🚨 For users on MacOS 🚨
A long-standing Ginkgo performance issue on MacOS seems to be due to mac's antimalware XProtect. You can follow the instructions here to disable it in your terminal. Doing so sped up Ginkgo's own test suite from 1m8s to 47s.
Fixes
Ginkgo's CLI is now a bit clearer if you pass flags in incorrectly:
a0e52ff]b799d8d]This might cause existing CI builds to fail. If so then it's likely that your CI build was misconfigured and should be corrected. Open an issue if you need help.
v2.23.0Compare Source
2.23.0
Ginkgo 2.23.0 adds a handful of methods to
GinkgoT()to make it compatible with thetesting.TBinterface in Go 1.24.GinkgoT().Context(), in particular, is a useful shorthand for generating a new context that will clean itself up in aDeferCleanup(). This has subtle behavior differences from the golang implementation but should make sense in a Ginkgo... um... context.Features
37a511b]Fixes
7556a86]4df06c6]Maintenance
cbcf39a]9b261ff]00f19c8]e98a4df]60cc4e2]fea6f2d]31d7813]fc3bbd6]aee0d56]809a710]v2.22.2Compare Source
What's Changed
Full Changelog: onsi/ginkgo@v2.22.1...v2.22.2
v2.22.1Compare Source
2.22.1
Fixes
Fix CSV encoding
aab3da6]c09df39]96a80fc]43dad69]Maintenance
c88c634]4df44bf]onsi/gomega (github.com/onsi/gomega)
v1.39.1Compare Source
1.39.1
Update all dependencies. This auto-updated the required version of Go to 1.24, consistent with the fact that Go 1.23 has been out of support for almost six months.
v1.39.0Compare Source
1.39.0
Features
Add
MatchErrorStrictlywhich only passes iferrors.Is(actual, expected)returns true.MatchError, by contrast, will fallback to string comparison.v1.38.3Compare Source
1.38.3
Fixes
make string formatitng more consistent for users who use format.Object directly
v1.38.2Compare Source
1.38.2
c404969]v1.38.1Compare Source
1.38.1
Fixes
Numerous minor fixes and dependency bumps
v1.38.0Compare Source
1.38.0
Features
4ee7ed0]Fixes
36bbf72]Maintenance
529d408]acd1f55]bae65a0]8dda91f]212d812]59bd7f9]328c729]9a798a1]04a72c6]v1.37.0Compare Source
1.37.0
Features
5666f98]v1.36.3Compare Source
1.36.3
Maintenance
adb8b49]interface{}withany[7613216]9fe5259]a0e85b9]604a8b1]36fbc84]ced70d7]c8b4a07]06431b9]b55a92d]a1d518b]v1.36.2Compare Source
Maintenance
v1.36.1Compare Source
1.36.1
Fixes
1c6c112]4feb9d7]slack-go/slack (github.com/slack-go/slack)
v0.20.0Compare Source
Previous release. See GitHub releases
for details.
v0.19.0Compare Source
Previous release. See GitHub releases
for details.
v0.18.0Compare Source
Previous release. See GitHub releases
for details.
v0.17.3Compare Source
What's New
IsEmailConfirmedtoUserby @nlopes in #1458Fixes
In the previous version we introduced the ability to parse specific errors (more complex ones) but Slack can still send us a
string.stringis now the fallback type.Other
Also added a ./examples/README.md explaining the patterns that should be used.
Full Changelog: slack-go/slack@v0.17.2...v0.17.3
v0.17.2Compare Source
Features added
Timezoneparameter for the slackTimePickerBlockElementby @jamesjarvis in #1448 and #1449ImageBlockElementby @superturkey650 in #1444/migration.exchangeto the library by @nlopes in #1453/apps.connections.openhandler to slacktest by @prologic in #1447New Contributors
Full Changelog: slack-go/slack@v0.17.1...v0.17.2
v0.17.1Compare Source
This has the potential to be a breaking change if and only if you have been building
SlackResponseby hand, which you shouldn't 😬. If you are, my apologies for adding this in a minor version, I thought the likelihood of this to be very very low. See #1443 for more details.Features added
channel_unsharedevent by @nlopes in #1437This adds the missing optional dependency for Blocks to the upload file method, allowing users to use rich blocks and buttons during the file upload process.
Detailed list of all of the changes
New Contributors
Full Changelog: slack-go/slack@v0.17.0...v0.17.1
v0.17.0Compare Source
MAJOR BREAKING CHANGES
This release has a few major breaking changes. And a couple require developers to pay a bit of attention, else their programs will break.
I am sorry this is the case but such is life sometimes.
See below for the most important, and trickier breaking changes.
Breaking changes
Our
MessageEventhas been quite wrong for a while. This should fix it but it does mean folks will have to change their code to cope with this new structure. Please be extra vigilant in areas of your code that usesMessageEvent.FunctionExecutedEventhadInputsset asmap[string]stringbut that didn't allow enough flexibility - that has been changed tomap[string]interface.emojivalue in plain text blocks to be null by @calebmckay in #1354The
Emojifield inTextBlockObjectis now a pointer to ensure we can make a distinction betweennilandfalse. Only affects when unmarshalling.Slack has deprecated legacy workflows for a long time, and beginning September 26, 2024, Slack stopped executing workflows containing a "step from app." See more at https://api.slack.com/changelog/2023-08-workflow-steps-from-apps-step-back.
PublishViewContext()now requires people to pass aPublishViewContextRequestwhich became a public type. If you callPublishViewContext()in your code, please adjust accordingly.AltTexttoAltTxtandSnippetTexttoSnippetType(inGetUploadURLExternalParametersandUploadFileV2Parameters) by @nlopes in #1422AppHomeOpenedEventViewis now a pointer by @nlopes in #1424This provides slightly better ergonomics in the case when there's no view yet.
Features added
MultiSelectBlockElementby @quantumsheep in #1373Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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.