Remove Vue set for vue 3 migration from protected environments

changed milestone to %17.0

added Category:SAST Category:Security Policy Management automation:ml devopssecure frontend groupsecurity policies sectionsec test vue3-migration labels

assigned to @arfedoro

changed title from Remove Vue set for vue 3 migration to Remove Vue set for vue 3 migration from protected environments

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.

Reviewer roulette

Category	Reviewer	Maintainer
frontend	`@bsandlin` (UTC-5, 7 hours behind author)	`@eduardosanz` (UTC+2, same timezone as author)

Please check reviewer's status!

Reviewer is available!
Reviewer is unavailable!

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

@arfedoro - please see the following guidance and update this merge request.

	1 Error
	Please add typebug typefeature, or typemaintenance label to this merge request.

Bundle size analysis [beta]

This compares changes in bundle size for entry points between the commits e6c1c757 and ae05bc62

Special assets

Entrypoint / Name	Size before	Size after	Diff	Diff in percent
average	4.31 MB	4.31 MB	-	0.0 %
mainChunk	3.3 MB	3.3 MB	-	0.0 %

Note: We do not have exact data for e6c1c757. So we have used data from: 4a9bef9a.
The target commit was too new, so we used the latest commit from master we have info on.
It might help to rerun the bundle-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

E2E Test Result Summary

allure-report-publisher generated test report!

e2e-test-on-gdk: test report for ae05bc62

expand test summary

+------------------------------------------------------------------+
|                          suites summary                          |
+-------------+--------+--------+---------+-------+-------+--------+
|             | passed | failed | skipped | flaky | total | result |
+-------------+--------+--------+---------+-------+-------+--------+
| Data Stores | 27     | 0      | 4       | 0     | 31    | ✅     |
| Govern      | 66     | 0      | 0       | 0     | 66    | ✅     |
| Verify      | 35     | 0      | 1       | 0     | 36    | ✅     |
| Create      | 96     | 0      | 9       | 0     | 105   | ✅     |
| Plan        | 51     | 0      | 2       | 0     | 53    | ✅     |
| Package     | 19     | 0      | 12      | 0     | 31    | ✅     |
| Monitor     | 7      | 0      | 0       | 0     | 7     | ✅     |
| Release     | 5      | 0      | 0       | 0     | 5     | ✅     |
| Manage      | 0      | 0      | 1       | 0     | 1     | ➖     |
| Analytics   | 2      | 0      | 0       | 0     | 2     | ✅     |
+-------------+--------+--------+---------+-------+-------+--------+
| Total       | 308    | 0      | 29      | 0     | 337   | ✅     |
+-------------+--------+--------+---------+-------+-------+--------+

added 448 commits

65aa7904...b857f4ec - 446 commits from branch master
55c2a0ed - Remove Vue set for vue 3 migration
aab0ce29 - Applied maintainer changes

Compare with previous version

@arfedoro Some end-to-end (E2E) tests should run based on the stage label.

Please start the manual:e2e-test-pipeline-generate job in the prepare stage and wait for the tests in the follow-up:e2e:package-and-test-ee pipeline to pass before merging this MR. Do not use Auto-merge, unless these tests have already completed successfully, because a failure in these tests do not block the auto-merge. (E2E tests are computationally intensive and don't run automatically for every push/rebase, so we ask you to run this job manually at least once.)

To run all E2E tests, apply the pipeline:run-all-e2e label and run a new pipeline.

E2E test jobs are allowed to fail due to flakiness. See current failures at the latest pipeline triage issue.

Once done, apply the emoji on this comment.

Team members only: for any questions or help, reach out on the internal #test-platform Slack channel.