forked from whitesource/log4j-detect-distribution
-
Notifications
You must be signed in to change notification settings - Fork 0
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 Mend: high confidence minor and patch dependency updates #4
Open
mend-for-github-com
wants to merge
1
commit into
main
Choose a base branch
from
whitesource-remediate/mend-high-confidence-minor-and-patch-dependency-updates
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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
mend-for-github-com
bot
force-pushed
the
whitesource-remediate/mend-high-confidence-minor-and-patch-dependency-updates
branch
from
March 26, 2024 02:50
3e18190
to
16f21dc
Compare
mend-for-github-com
bot
changed the title
Update module go.uber.org/zap to v1.27.0
Update Mend: high confidence minor and patch dependency updates
Mar 26, 2024
mend-for-github-com
bot
force-pushed
the
whitesource-remediate/mend-high-confidence-minor-and-patch-dependency-updates
branch
from
April 9, 2024 02:50
16f21dc
to
26910cf
Compare
mend-for-github-com
bot
force-pushed
the
whitesource-remediate/mend-high-confidence-minor-and-patch-dependency-updates
branch
from
May 6, 2024 02:54
26910cf
to
6cdc363
Compare
mend-for-github-com
bot
force-pushed
the
whitesource-remediate/mend-high-confidence-minor-and-patch-dependency-updates
branch
from
May 15, 2024 02:47
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
May 26, 2024 02:40
9f33c51
to
ac47221
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
June 18, 2024 02:49
9c2b072
to
1d62a69
Compare
mend-for-github-com
bot
force-pushed
the
whitesource-remediate/mend-high-confidence-minor-and-patch-dependency-updates
branch
from
July 10, 2024 02:50
1d62a69
to
64f21fe
Compare
ℹ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
mend-for-github-com
bot
force-pushed
the
whitesource-remediate/mend-high-confidence-minor-and-patch-dependency-updates
branch
from
August 11, 2024 03:09
64f21fe
to
d561bd3
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
September 10, 2024 03:53
e001bf6
to
d144256
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
October 9, 2024 02:50
703a6c1
to
e242be1
Compare
mend-for-github-com
bot
force-pushed
the
whitesource-remediate/mend-high-confidence-minor-and-patch-dependency-updates
branch
from
November 13, 2024 02:15
e242be1
to
65a45e3
Compare
mend-for-github-com
bot
force-pushed
the
whitesource-remediate/mend-high-confidence-minor-and-patch-dependency-updates
branch
from
November 24, 2024 05:11
65a45e3
to
15df6a3
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
December 13, 2024 02:56
69b2bf1
to
ff5af30
Compare
mend-for-github-com
bot
force-pushed
the
whitesource-remediate/mend-high-confidence-minor-and-patch-dependency-updates
branch
from
December 23, 2024 03:49
ff5af30
to
29cf2b6
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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.2
v1.2.2
->v1.3.0
v1.26.1
->v1.33.0
v1.2.1
->v1.8.1
v1.7.0
->v1.10.0
v1.19.0
->v1.27.0
v0.0.0-20211109214657-ef0fda0de508
->v0.33.0
v0.3.7
->v0.21.0
Release Notes
go-logr/logr (github.com/go-logr/logr)
v1.4.2
Compare Source
What's Changed
Dependencies:
Full Changelog: go-logr/logr@v1.4.1...v1.4.2
v1.4.1
Compare Source
What's Changed
Full Changelog: go-logr/logr@v1.4.0...v1.4.1
v1.4.0
Compare Source
This release dramatically improves interoperability with Go's
log/slog
package. In particular,logr.NewContext
andlogr.NewContextWithSlogLogger
use the same context key, which allowslogr.FromContext
andlogr.FromContextAsSlogLogger
to returnlogr.Logger
or*slog.Logger
respectively, including transparently converting each to the other as needed.Functions
logr/slogr.NewLogr
andlogr/slogr.ToSlogHandler
have been superceded bylogr.FromSlogHandler
andlogr.ToSlogHandler
respectively, and typelogr/slogr.SlogSink
has been superceded bylogr.SlogSink
. All of the old names inlogr/slogr
remain, for compatibility.Package
logr/funcr
now supportslogr.SlogSink
, meaning that it's output passes all but one of the Slog conformance tests (that exception being thatfuncr
handles the timestamp itself).Users who have a
logr.Logger
and need a*slog.Logger
can callslog.New(logr.ToSlogHandler(...))
and all output will go through the same stack.Users who have a
*slog.Logger
orslog.Handler
can 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.0
Compare Source
This release adds support for slog in a new, self-contained
logr/slogr
package. Implementers of alogr.LogSink
are encouraged, but not required, to extend their implementation to improve the quality of log output coming from aslog
API call.Breaking change: the call depth for
LogSink.Enabled
when called viaLogger.Enabled
was fixed to be the same as for other call paths. Implementers of aLogSink
who 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.4
Compare 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.3
Compare 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.0
Compare Source
This release adds support for slog. zapr implements
slogr.SlogSink
and therefore can be used throughslogr.NewSlogHandler
as backend for slog.What's Changed
New Contributors
Full Changelog: go-logr/zapr@v1.2.4...v1.3.0
v1.2.4
Compare Source
What's Changed
New Contributors
Full Changelog: go-logr/zapr@v1.2.3...v1.2.4
v1.2.3
Compare Source
What's Changed
Full Changelog: go-logr/zapr@v1.2.2...v1.2.3
rs/zerolog (github.com/rs/zerolog)
v1.33.0
Compare Source
v1.32.0
Compare Source
v1.31.0
Compare Source
v1.30.0
Compare Source
v1.29.1
Compare Source
v1.29.0
Compare Source
v1.28.0
Compare Source
v1.27.0
Compare Source
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 #1788Configuration
📅 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.