Update Mend: high confidence minor and patch dependency updates #4
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
![mend-for-github-com[bot]](https://avatars.githubusercontent.com/in/30796?s=60&v=4){kind=small}
mend-for-github-com
bot
force-pushed
the
whitesource-remediate/mend-high-confidence-minor-and-patch-dependency-updates
branch
from
3e18190
to
16f21dc
Compare
mend-for-github-com
bot
changed the title
mend-for-github-com
bot
force-pushed
the
whitesource-remediate/mend-high-confidence-minor-and-patch-dependency-updates
branch
from
16f21dc
to
26910cf
Compare
mend-for-github-com
bot
force-pushed
the
whitesource-remediate/mend-high-confidence-minor-and-patch-dependency-updates
branch
from
26910cf
to
6cdc363
Compare
mend-for-github-com
bot
force-pushed
the
whitesource-remediate/mend-high-confidence-minor-and-patch-dependency-updates
branch
from
6cdc363
to
4f32393
Compare
mend-for-github-com
bot
force-pushed
the
whitesource-remediate/mend-high-confidence-minor-and-patch-dependency-updates
branch
3 times, most recently
from
9f33c51
to
ac47221
Compare
mend-for-github-com
bot
force-pushed
the
whitesource-remediate/mend-high-confidence-minor-and-patch-dependency-updates
branch
2 times, most recently
from
f1cba15
to
9c2b072
Compare
mend-for-github-com
bot
force-pushed
the
whitesource-remediate/mend-high-confidence-minor-and-patch-dependency-updates
branch
from
9c2b072
to
1d62a69
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:
v1.2.2->v1.4.2v1.2.2->v1.3.0v1.26.1->v1.33.0v1.2.1->v1.8.1v1.7.0->v1.9.0v1.19.0->v1.27.0v0.3.7->v0.16.0Release Notes
go-logr/logr (github.com/go-logr/logr)
v1.4.2Compare Source
What's Changed
Dependencies:
Full Changelog: go-logr/logr@v1.4.1...v1.4.2
v1.4.1Compare Source
What's Changed
Full Changelog: go-logr/logr@v1.4.0...v1.4.1
v1.4.0Compare Source
This release dramatically improves interoperability with Go's
log/slogpackage. In particular,logr.NewContextandlogr.NewContextWithSlogLoggeruse the same context key, which allowslogr.FromContextandlogr.FromContextAsSlogLoggerto returnlogr.Loggeror*slog.Loggerrespectively, including transparently converting each to the other as needed.Functions
logr/slogr.NewLograndlogr/slogr.ToSlogHandlerhave been superceded bylogr.FromSlogHandlerandlogr.ToSlogHandlerrespectively, and typelogr/slogr.SlogSinkhas been superceded bylogr.SlogSink. All of the old names inlogr/slogrremain, for compatibility.Package
logr/funcrnow supportslogr.SlogSink, meaning that it's output passes all but one of the Slog conformance tests (that exception being thatfuncrhandles the timestamp itself).Users who have a
logr.Loggerand need a*slog.Loggercan callslog.New(logr.ToSlogHandler(...))and all output will go through the same stack.Users who have a
*slog.Loggerorslog.Handlercan calllogr.FromSlogHandler(...)and all output will go through the same stack.What's Changed
New Contributors
Full Changelog: go-logr/logr@v1.3.0...v1.4.0
v1.3.0Compare Source
This release adds support for slog in a new, self-contained
logr/slogrpackage. Implementers of alogr.LogSinkare encouraged, but not required, to extend their implementation to improve the quality of log output coming from aslogAPI call.Breaking change: the call depth for
LogSink.Enabledwhen called viaLogger.Enabledwas fixed to be the same as for other call paths. Implementers of aLogSinkwho have worked around this bug will need to remove their workarounds.Security best practices were improved. Only Go versions >= 1.18 are supported by this release.
What's Changed
New Contributors
Full Changelog: go-logr/logr@v1.2.4...v1.3.0
v1.2.4Compare Source
This is a collection of small bugfixes and documentation updates.
NOTE: A change (https://github.com/go-logr/logr/pull/166) which was thought to be compatible seems to be a breaking change. In particular, one used to be able to differentiate the result of
Discard()fromLogger{}. After this change, those are the same. We are considering how to address this, but do not currently plan to revert this change. Apologies!What's Changed
New Contributors
Full Changelog: go-logr/logr@v1.2.3...v1.2.4
v1.2.3Compare Source
This is a minor release.
What's Changed
New Contributors
Full Changelog: go-logr/logr@v1.2.2...v1.2.3
go-logr/zapr (github.com/go-logr/zapr)
v1.3.0Compare Source
This release adds support for slog. zapr implements
slogr.SlogSinkand therefore can be used throughslogr.NewSlogHandleras backend for slog.What's Changed
New Contributors
Full Changelog: go-logr/zapr@v1.2.4...v1.3.0
v1.2.4Compare Source
What's Changed
New Contributors
Full Changelog: go-logr/zapr@v1.2.3...v1.2.4
v1.2.3Compare Source
What's Changed
Full Changelog: go-logr/zapr@v1.2.2...v1.2.3
rs/zerolog (github.com/rs/zerolog)
v1.33.0Compare Source
v1.32.0Compare Source
v1.31.0Compare Source
v1.30.0Compare Source
v1.29.1Compare Source
v1.29.0Compare Source
v1.28.0Compare Source
v1.27.0Compare Source
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 #1800Configuration
📅 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.