chore(ui): Update lodash/lodash-es to 4.18.1#19783
Conversation
|
This change is part of the following stack: Change managed by git-spice. |
|
Images are ready for the commit at fc2e64b. To use with deploy scripts, first |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #19783 +/- ##
=======================================
Coverage 49.59% 49.60%
=======================================
Files 2763 2763
Lines 208167 208167
=======================================
+ Hits 103240 103253 +13
+ Misses 97262 97250 -12
+ Partials 7665 7664 -1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
The backport to To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-release-4.8 release-4.8
# Navigate to the new working tree
cd .worktrees/backport-release-4.8
# Create a new branch
git switch --create backport-19783-to-release-4.8
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 dc7b1244d7c03ebe7f6301e13c592ce4228a6f93
# Push it to GitHub
git push --set-upstream origin backport-19783-to-release-4.8
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-release-4.8Then, create a pull request where the |
|
The backport to To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-release-4.9 release-4.9
# Navigate to the new working tree
cd .worktrees/backport-release-4.9
# Create a new branch
git switch --create backport-19783-to-release-4.9
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 dc7b1244d7c03ebe7f6301e13c592ce4228a6f93
# Push it to GitHub
git push --set-upstream origin backport-19783-to-release-4.9
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-release-4.9Then, create a pull request where the |
|
The backport to To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-release-4.10 release-4.10
# Navigate to the new working tree
cd .worktrees/backport-release-4.10
# Create a new branch
git switch --create backport-19783-to-release-4.10
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 dc7b1244d7c03ebe7f6301e13c592ce4228a6f93
# Push it to GitHub
git push --set-upstream origin backport-19783-to-release-4.10
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-release-4.10Then, create a pull request where the |
🚀 Build Images ReadyImages are ready for commit dc7b124. To use with deploy scripts: export MAIN_IMAGE_TAG=4.11.x-545-gdc7b1244d7 |
Description
As titled. https://access.redhat.com/security/cve/cve-2026-4800
User-facing documentation
Testing and quality
Automated testing
How I validated my change
CI