Update dependency @gitlab/ui to v78.6.1
This MR contains the following updates:
Package | Type | Update | Change |
---|---|---|---|
@gitlab/ui | dependencies | patch | 78.6.0 -> 78.6.1 |
MR created with the help of gitlab-org/frontend/renovate-gitlab-bot
Release Notes
Configuration
-
If you want to rebase/retry this MR, check this box
This MR has been generated by Renovate Bot.
Merge request reports
Activity
Renovate Comment
What are the next steps?
If you have been assigned as a reviewer to this Merge Request, please review this Merge Request with the same scrutiny as any community contribution:
-
Ensure that the dependencies updated meet our standards:
- Security: Dependencies do not contain malicious code
- Performance: Dependencies do not bloat the application code or prolong CI times unnecessarily
- Stability: Pipelines are passing
-
Review the changes introduced by the version upgrade. Consider using https://my.diffend.io to compare the two versions in case the updated dependency is either a Ruby Gem or a Node.js package, for example to compare
pg_query
2.1.0
and2.1.4
. -
Check if
bundle install
works locally, in the context of GDK. -
If tests are passing and you've reviewed the updated dependencies, execute pipelines in the context of the main project
This MR is created from a fork, therefore not all jobs (e.g. Danger) might have been executed. Instead of hitting MWPS right away, you might want to wait until the pipeline you've just triggered finished.
Note: This might not be available in projects, in that case merging right away is an option
-
Merge away!
Troubleshooting
We have assembled some FAQs to help reviewers of these kind of merge requests.
Improve this message – The JSON comment below is for automation purposes.
{"labels":["maintenance::dependency","type::maintenance","automation:bot-authored","frontend"],"assignees":["gitlab-dependency-update-bot"],"reviewers":["aturinske","afontaine","ankit.panchal","anna_vovchenko","arfedoro","blabuschagne","dpisek","dmishunov","djadmin","elwyn-gitlab","ealcantara","fguibert","himkp","jannik_lehmann","jerasmus","jivanvl","justin_ho","kushalpandya","leipert","mfluharty","mgandres","mrincon","ntepluhina","ohoral","pgascouvaillancourt","pslaughter","iamphill","psjakubowska","rchanila","rob.hunt","svedova","shampton","slashmanov","tbulva","vitallium"]}
Edited by GitLab Dependency Bot-
mentioned in issue #365044
requested review from @slashmanov and @jannik_lehmann
assigned to @gitlab-dependency-update-bot
added 149 commits
-
1d88f8ed...26fc4eea - 148 commits from branch
gitlab-org:master
- 225354a1 - Update dependency @gitlab/ui to v78.6.1
-
1d88f8ed...26fc4eea - 148 commits from branch
2 Warnings This merge request has introduced duplicated yarn dependencies. This merge request does not refer to an existing milestone. 1 Message CHANGELOG missing: If this merge request needs a changelog entry, add the
Changelog
trailer to the commit message you want to add to the changelog.If this merge request doesn't need a CHANGELOG entry, feel free to ignore this message.
Duplicate yarn dependencies
The following dependencies should be de-duplicated:
Package "ignore" wants ^5.2.0 and could get 5.3.1, but got 5.3.0
Package "ignore" wants ^5.3.0 and could get 5.3.1, but got 5.3.0
Package "jsonc-parser" wants ^3.0.0 and could get 3.2.1, but got 3.2.0
Package "minimatch" wants ^9.0.1 and could get 9.0.3, but got 9.0.1
Please run the following command and commit the changes to
yarn.lock
:node_modules/.bin/yarn-deduplicate --strategy fewer yarn.lock \ && yarn install
Reviewer roulette
Category Reviewer Maintainer frontend @lcallahan
(UTC-6)
@djadmin
(UTC+5.5)
Please check reviewer's status!
Please refer to documentation page for guidance on how you can benefit from the Reviewer Roulette, or use the GitLab Review Workload Dashboard to find other available reviewers.
If needed, you can retry the
danger-review
job that generated this comment.Generated by
Danger- Resolved by Savas Vedova
@svedova The pipeline on the GitLab UI integration MR is broken. This is the MR: gitlab-ui!4040 (merged) that triggered the GitLab UI update.
Since you have context, could you help out investigating here? Thank you!
requested review from @svedova
added 43 commits
-
225354a1...e3da1159 - 42 commits from branch
gitlab-org:master
- 7afb7561 - Update dependency @gitlab/ui to v78.6.1
-
225354a1...e3da1159 - 42 commits from branch
assigned to @slashmanov
removed review request for @slashmanov
Bundle size analysis [beta]
This compares changes in bundle size for entry points between the commits 457909e1 and 384a85e8
Special assetsEntrypoint / Name Size before Size after Diff Diff in percent average 4.25 MB 4.25 MB - 0.0 % mainChunk 3.23 MB 3.23 MB - 0.0 %
Note: We do not have exact data for 457909e1. So we have used data from: df31e7c3.
The target commit was too new, so we used the latest commit from master we have info on.
It might help to rerun thebundle-size-review
job
This might mean that you have a few false positives in this report. If something unrelated to your code changes is reported, you can check this comparison in order to see if they caused this change.Please look at the full report for more details
Read more about how this report works.
Generated by
DangerEdited/Blocked Notification
Renovate will not automatically rebase this MR, because it does not recognize the last commit author and assumes somebody else may have edited the MR.
You can manually request rebase by checking the rebase/retry box above.
Warning: custom changes will be lost.added pipeline:mr-approved label
- Resolved by Savas Vedova
@svedova
, thanks for approving this merge request.This is the first time the merge request has been approved. To ensure we don't only run predictive pipelines, and we don't break
master
, a new pipeline will be started shortly.Please wait for the pipeline to start before resolving this discussion and set auto-merge for the new pipeline. See merging a merge request for more details.
enabled an automatic merge when the pipeline for a6d20d9b succeeds
Merge request already has "MWPS" set.
Adding automation:bot-no-updates in order to prevent renovate from updating the MR.
If you want the MR to be updated again, please remove the label and check the "rebase checkbox" in the description.
added automation:bot-no-updates label
E2E Test Result Summary
allure-report-publisher
generated test report!e2e-test-on-gdk:
test report for 384a85e8expand test summary
+------------------------------------------------------------------+ | suites summary | +-------------+--------+--------+---------+-------+-------+--------+ | | passed | failed | skipped | flaky | total | result | +-------------+--------+--------+---------+-------+-------+--------+ | Create | 77 | 0 | 9 | 0 | 86 | ✅ | | Govern | 66 | 0 | 0 | 0 | 66 | ✅ | | Verify | 35 | 0 | 1 | 0 | 36 | ✅ | | Package | 24 | 0 | 6 | 0 | 30 | ✅ | | Plan | 51 | 0 | 2 | 0 | 53 | ✅ | | Data Stores | 31 | 0 | 0 | 0 | 31 | ✅ | | Monitor | 7 | 0 | 0 | 0 | 7 | ✅ | | Manage | 0 | 0 | 1 | 0 | 1 | ➖ | | Analytics | 2 | 0 | 0 | 0 | 2 | ✅ | | Release | 5 | 0 | 0 | 0 | 5 | ✅ | +-------------+--------+--------+---------+-------+-------+--------+ | Total | 298 | 0 | 19 | 0 | 317 | ✅ | +-------------+--------+--------+---------+-------+-------+--------+
e2e-package-and-test:
test report for 384a85e8expand test summary
+---------------------------------------------------------------------+ | suites summary | +----------------+--------+--------+---------+-------+-------+--------+ | | passed | failed | skipped | flaky | total | result | +----------------+--------+--------+---------+-------+-------+--------+ | Package | 205 | 0 | 38 | 18 | 243 | ✅ | | Govern | 271 | 0 | 20 | 0 | 291 | ✅ | | Fulfillment | 8 | 0 | 75 | 1 | 83 | ✅ | | Create | 570 | 0 | 81 | 8 | 651 | ✅ | | Plan | 249 | 0 | 19 | 0 | 268 | ✅ | | Monitor | 36 | 0 | 13 | 0 | 49 | ✅ | | GitLab Metrics | 2 | 0 | 1 | 0 | 3 | ✅ | | Data Stores | 119 | 0 | 28 | 0 | 147 | ✅ | | Systems | 10 | 0 | 0 | 0 | 10 | ✅ | | Analytics | 7 | 0 | 0 | 0 | 7 | ✅ | | Verify | 150 | 0 | 30 | 2 | 180 | ✅ | | Manage | 37 | 1 | 12 | 0 | 50 | ❌ | | Configure | 1 | 0 | 9 | 0 | 10 | ✅ | | Secure | 6 | 0 | 3 | 0 | 9 | ✅ | | Growth | 0 | 0 | 6 | 0 | 6 | ➖ | | Release | 15 | 0 | 3 | 0 | 18 | ✅ | | ModelOps | 0 | 0 | 3 | 0 | 3 | ➖ | | Ai-powered | 0 | 0 | 3 | 0 | 3 | ➖ | +----------------+--------+--------+---------+-------+-------+--------+ | Total | 1686 | 1 | 344 | 29 | 2031 | ❌ | +----------------+--------+--------+---------+-------+-------+--------+
mentioned in incident gitlab-org/quality/engineering-productivity/review-apps-broken-incidents#1515 (closed)
The pipeline failed in Trigger:package, looks like this has been fixed now (omnibus-gitlab#8476 (comment 1845182727)) so I am re-running the pipeline.
Edited by Miguel RinconWe had more failures, so I am retrying again: omnibus-gitlab#8476 (comment 1845448460)
mentioned in commit edd692e8
added workflowstaging-canary label
added workflowcanary label and removed workflowstaging-canary label
added workflowproduction label and removed workflowcanary label
added workflowstaging label and removed workflowproduction label
changed milestone to %16.11
added workflowpost-deploy-db-staging label and removed workflowstaging label
added workflowpost-deploy-db-production label and removed workflowpost-deploy-db-staging label
added releasedcandidate label
added releasedpublished label and removed releasedcandidate label
added pipelinetier-3 label