chore: Update STABLE-RELEASE to v1.4.6 #1909
Merged
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
rksharma95
previously approved these changes
Dec 6, 2024
daemon1024
previously approved these changes
Dec 6, 2024
DelusionalOptimist
force-pushed
the
chore/latest-release-timeout
branch
from
38aea94 to
30e3aca
Compare
Signed-off-by: Rudraksh Pareek <[email protected]>
Signed-off-by: Rudraksh Pareek <[email protected]>
DelusionalOptimist
dismissed stale reviews from daemon1024 and rksharma95
via
537460d
DelusionalOptimist
force-pushed
the
chore/latest-release-timeout
branch
from
30e3aca to
537460d
Compare
DelusionalOptimist
changed the title
daemon1024
approved these changes
Dec 11, 2024
rootxrishabh
approved these changes
Dec 11, 2024
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.
Purpose of PR?:
Fixes https://github.com/kubearmor/KubeArmor/actions/runs/12197275207/job/34034317189
Does this PR introduce a breaking change?
If the changes in this PR are manually verified, list down the scenarios covered::
Additional information for reviewer? :
Mention if this PR is part of any design or a continuation of previous PRs
Checklist:
<type>(<scope>): <subject>