Add missing package manager `poetry`

changed milestone to %16.6

added Category:Software Composition Analysis Enterprise Edition GitLab Ultimate SCA:License Scanning backend bugfunctional devopssecure groupcomposition analysis sectionsec typebug labels

assigned to @gonzoyumo

Reviewer roulette

Changes that require review have been detected!

Please refer to the table below for assigning reviewers and maintainers suggested by Danger in the specified category:

Category	Reviewer	Maintainer
backend	`@jtapiab` (UTC-3, 1 hour ahead of author)	`@ck3g` (UTC+2, 6 hours ahead of author)

Please check reviewer's status!

Reviewer is available!
Reviewer is unavailable!

Feel free to override these selections if you think someone else would be better-suited or use the GitLab Review Workload Dashboard to find other available reviewers.

To read more on how to use the reviewer roulette, please take a look at the Engineering workflow and code review guidelines. Please consider assigning a reviewer or maintainer who is a domain expert in the area of the merge request.

Once you've decided who will review this merge request, assign them as a reviewer! Danger does not automatically notify them for you.

If needed, you can retry the danger-review job that generated this comment.

Generated by Danger

Allure report

allure-report-publisher generated test report!

e2e-test-on-gdk: test report for 221a1947

expand test summary

+------------------------------------------------------------------+
|                          suites summary                          |
+-------------+--------+--------+---------+-------+-------+--------+
|             | passed | failed | skipped | flaky | total | result |
+-------------+--------+--------+---------+-------+-------+--------+
| Plan        | 51     | 0      | 0       | 0     | 51    | ✅     |
| Govern      | 42     | 0      | 3       | 0     | 45    | ✅     |
| Verify      | 20     | 0      | 0       | 0     | 20    | ✅     |
| Create      | 32     | 0      | 5       | 0     | 37    | ✅     |
| Data Stores | 20     | 0      | 0       | 0     | 20    | ✅     |
| Manage      | 0      | 0      | 1       | 0     | 1     | ➖     |
+-------------+--------+--------+---------+-------+-------+--------+
| Total       | 165    | 0      | 9       | 0     | 174   | ✅     |
+-------------+--------+--------+---------+-------+-------+--------+

e2e-package-and-test: test report for 0a4b8172

expand test summary

+-------------------------------------------------------------+
|                       suites summary                        |
+--------+--------+--------+---------+-------+-------+--------+
|        | passed | failed | skipped | flaky | total | result |
+--------+--------+--------+---------+-------+-------+--------+
| Create | 129    | 1      | 25      | 0     | 155   | ❌     |
| Secure | 6      | 0      | 3       | 0     | 9     | ✅     |
+--------+--------+--------+---------+-------+-------+--------+
| Total  | 135    | 1      | 28      | 0     | 164   | ❌     |
+--------+--------+--------+---------+-------+-------+--------+

marked this merge request as ready

marked the checklist item I have evaluated the MR acceptance checklist for this MR. as completed

@jtapiab could you please review this MR? Thanks!

requested review from @jtapiab

approved this merge request

removed review request for @jtapiab

@jtapiab, thanks for approving this merge request.

This is the first time the merge request has been approved. To ensure full test coverage, a new pipeline will be started shortly.

For more info, please refer to the following links:

added pipeline:mr-approved label

	1 Warning
	This Merge Request needs to be labelled with documentation. Please request a reviewer or maintainer to add them.

	1 Message
	This merge request adds or changes documentation files. A review from the Technical Writing team before you merge is recommended. Reviews can happen after you merge.

Documentation review

The following files require a review from a technical writer:

doc/api/graphql/reference/index.md (Link to current live version)

The review does not need to block merging this merge request. See the:

Metadata for the *.md files that you've changed. The first few lines of each *.md file identify the stage and group most closely associated with your docs change.
The Technical Writer assigned for that stage and group.
Documentation workflows for information on when to assign a merge request for review.

Reviewer roulette

Changes that require review have been detected!

Please refer to the table below for assigning reviewers and maintainers suggested by Danger in the specified category:

Category	Reviewer	Maintainer
backend	`@rkumar555` (UTC+2, 6 hours ahead of author)	`@ck3g` (UTC+2, 6 hours ahead of author)

Please check reviewer's status!

Reviewer is available!
Reviewer is unavailable!

Feel free to override these selections if you think someone else would be better-suited or use the GitLab Review Workload Dashboard to find other available reviewers.

To read more on how to use the reviewer roulette, please take a look at the Engineering workflow and code review guidelines. Please consider assigning a reviewer or maintainer who is a domain expert in the area of the merge request.

Once you've decided who will review this merge request, assign them as a reviewer! Danger does not automatically notify them for you.

If needed, you can retry the danger-review job that generated this comment.

Generated by Danger

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

Please start the trigger-omnibus-and-follow-up-e2e job in the qa stage and ensure tests in the follow-up-e2e:package-and-test-ee pipeline pass before this MR is merged. (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 #quality Slack channel.