chore(deps): update dependency octokit to v6

Renovate Comment

This Merge Request has been created with the help of renovate-gitlab-bot project.

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
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","Quality"],"assignees":["gitlab-dependency-update-bot"],"reviewers":["acunskis","a_mcdonald","chloeliu","ddavison","mlapierre","sliaquat","treagitlab"]}

assigned to @gitlab-dependency-update-bot

mentioned in issue #377987 (closed)

added Quality automation:bot-authored maintenancedependency typemaintenance labels

requested review from @ddavison and @a_mcdonald

added 1 commit

6fa50084 - Update dependency octokit to v6

Compare with previous version

changed title from Update dependency octokit to v6 to chore(deps): update dependency octokit to v6

changed title from chore(deps): update dependency octokit to v6 to Update dependency octokit to v6

changed title from Update dependency octokit to v6 to chore(deps): update dependency octokit to v6

marked the checklist item If you want to rebase/retry this MR, click this checkbox. as completed

added 849 commits

6fa50084...c340f404 - 848 commits from branch gitlab-org:master
5da128b6 - Update dependency octokit to v6

Compare with previous version

added QA label

	1 Warning
	This merge request does not refer to an existing milestone.

1 Message

CHANGELOG missing:

If you want to create a changelog entry for GitLab FOSS, add the Changelog trailer to the commit message you want to add to the changelog.

If you want to create a changelog entry for GitLab EE, also add the EE: true trailer to your commit message.

If this merge request doesn't need a CHANGELOG entry, feel free to ignore this message.

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
QA	Jay McCure (`@jay_mccure`) (UTC+10)	Ramya Authappan (`@at.ramya`) (UTC+5.5)

To spread load more evenly across eligible reviewers, Danger has picked a candidate for each review slot, based on their timezone. 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

marked the checklist item If you want to rebase/retry this MR, click this checkbox. as incomplete

added 1 commit

8a9acca5 - chore(deps): update dependency octokit to v6

Compare with previous version

Allure report

allure-report-publisher generated test report!

e2e-review-qa: test report for 5da128b6

expand test summary

+-----------------------------------------------------------------------------------------+
|                                     suites summary                                      |
+------------------------------------+--------+--------+---------+-------+-------+--------+
|                                    | passed | failed | skipped | flaky | total | result |
+------------------------------------+--------+--------+---------+-------+-------+--------+
| Govern                             | 18     | 0      | 5       | 1     | 23    | ❗     |
| Manage                             | 60     | 0      | 17      | 2     | 77    | ❗     |
| Create                             | 157    | 0      | 8       | 34    | 165   | ❗     |
| Fulfillment                        | 0      | 0      | 17      | 0     | 17    | ➖     |
| Package                            | 0      | 0      | 3       | 0     | 3     | ➖     |
| Plan                               | 56     | 0      | 4       | 0     | 60    | ✅     |
| Secure                             | 24     | 0      | 1       | 13    | 25    | ❗     |
| Verify                             | 42     | 0      | 8       | 21    | 50    | ❗     |
| Configure                          | 0      | 0      | 3       | 0     | 3     | ➖     |
| Analytics                          | 1      | 0      | 1       | 0     | 2     | ✅     |
| Release                            | 5      | 0      | 0       | 0     | 5     | ✅     |
| Feature flag handler sanity checks | 9      | 0      | 0       | 0     | 9     | ✅     |
| Version sanity check               | 0      | 0      | 1       | 0     | 1     | ➖     |
+------------------------------------+--------+--------+---------+-------+-------+--------+
| Total                              | 372    | 0      | 68      | 71    | 440   | ❗     |
+------------------------------------+--------+--------+---------+-------+-------+--------+

e2e-package-and-test: test report for 5da128b6

expand test summary

+---------------------------------------------------------------------------+
|                              suites summary                               |
+----------------------+--------+--------+---------+-------+-------+--------+
|                      | passed | failed | skipped | flaky | total | result |
+----------------------+--------+--------+---------+-------+-------+--------+
| Verify               | 214    | 0      | 42      | 4     | 256   | ❗     |
| Create               | 823    | 0      | 27      | 11    | 850   | ❗     |
| Package              | 144    | 0      | 37      | 0     | 181   | ✅     |
| Manage               | 365    | 0      | 65      | 1     | 430   | ❗     |
| Plan                 | 312    | 0      | 0       | 21    | 312   | ❗     |
| Configure            | 1      | 0      | 15      | 0     | 16    | ✅     |
| Fulfillment          | 12     | 0      | 75      | 0     | 87    | ✅     |
| GitLab Metrics       | 2      | 0      | 1       | 0     | 3     | ✅     |
| Release              | 25     | 0      | 0       | 0     | 25    | ✅     |
| Govern               | 123    | 1      | 0       | 7     | 124   | ❌     |
| Version sanity check | 0      | 0      | 7       | 3     | 7     | ➖     |
| Systems              | 18     | 0      | 1       | 0     | 19    | ✅     |
| Secure               | 121    | 0      | 5       | 9     | 126   | ❗     |
| Analytics            | 11     | 0      | 0       | 0     | 11    | ✅     |
| Data Stores          | 12     | 0      | 1       | 8     | 13    | ❗     |
+----------------------+--------+--------+---------+-------+-------+--------+
| Total                | 2183   | 1      | 276     | 64    | 2460  | ❌     |
+----------------------+--------+--------+---------+-------+-------+--------+

changed milestone to %15.6

approved this merge request

resolved all threads

merged

@a_mcdonald, did you forget to run a pipeline before you merged this work? Based on our code review process, if the latest pipeline finished more than 2 hours ago, you should:

Ensure the merge request is not in Draft status.
Start a pipeline (especially important for Community contribution merge requests).
Set the merge request to merge when pipeline succeeds.

This is a guideline, not a rule. Please consider replying to this comment for transparency.

This message was generated automatically. You're welcome to improve it.