Update dependency auto-build-image to v1.46.0

This MR contains the following updates:

Package	Update	Change
auto-build-image	minor	v1.44.0 -> v1.46.0

MR created with the help of gitlab-org/frontend/renovate-gitlab-bot

---

Release Notes

gitlab-org/cluster-integration/auto-build-image

v1.46.0

Compare Source

1.46.0 (2023-10-16)

Features

• deps: update dependency @​commitlint/config-conventional to ^17.8.0 (ea83e94)

v1.45.0

Compare Source

1.45.0 (2023-10-16)

Features

• deps: update dependency @​commitlint/cli to ^17.8.0 (90dd388)

---

Configuration

Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever MR becomes conflicted, or you tick the rebase/retry checkbox.

Ignore: Close this MR and you won't be reminded about this update again.

---

• If you want to rebase/retry this MR, check this box

---

This MR has been generated by Renovate Bot.

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:

1. 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

2. 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 and 2.1.4.

3. Check if bundle install works locally, in the context of GDK.

4. 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

5. 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":["type::maintenance","maintenance::dependency","ci::templates","group::environments","devops::deploy","section::cd"],"assignees":["gitlab-dependency-update-bot"],"reviewers":["Alexand","hfyngvason","tigerwnz"]}

assigned to @gitlab-dependency-update-bot

mentioned in issue #368050

added citemplates devopsdeploy groupenvironments maintenancedependency sectioncd typemaintenance labels

requested review from @tigerwnz and @Alexand

added 1 commit

• 6d9162a5 - Update dependency auto-build-image to v1.45.0

Compare with previous version

changed title from Update dependency auto-build-image to v1.45.0 to Update dependency auto-build-image to v1.46.0

changed the description

added 16 commits

• 6d9162a5...e0588559 - 15 commits from branch gitlab-org:master
• e593cf33 - Update dependency auto-build-image to v1.46.0

Compare with previous version

added automation:bot-authored label

approved this merge request

@Alexand, 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:

• rspec predictive jobs
• jest predictive jobs
• merging a merge request.

added pipeline:mr-approved label

removed review request for @Alexand

	2 Warnings
	This merge request does not refer to an existing milestone.
	You've made some app changes, but didn't add any tests. That's OK as long as you're refactoring existing code, but please consider adding any of the maintenancepipelines, maintenancerefactor, maintenanceworkflow, documentation, QA labels.

	1 Message
	This merge request adds or changes files that require a review from the CI/CD Templates maintainers.

This merge request requires a CI/CD Template review. To make sure these changes are reviewed, take the following steps:

1. Ensure the merge request has the citemplates label. If the merge request modifies CI/CD Template files, Danger will do this for you.
2. Prepare your MR for a CI/CD Template review according to the template development guide.
3. Assign and @ mention the CI/CD Template reviewer suggested by Reviewer Roulette.

The following files require a review from the CI/CD Templates maintainers:

• lib/gitlab/ci/templates/Jobs/Build.gitlab-ci.yml
• lib/gitlab/ci/templates/Jobs/Build.latest.gitlab-ci.yml

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
citemplates	lma-git (UTC-7)	hfyngvason (UTC-4)
~"Verify"	Reviewer review is optional for ~"Verify"	hfyngvason (UTC-4)

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 e593cf33

expand test summary

+-----------------------------------------------------------------------+
|                            suites summary                             |
+------------------+--------+--------+---------+-------+-------+--------+
|                  | passed | failed | skipped | flaky | total | result |
+------------------+--------+--------+---------+-------+-------+--------+
| Data Stores      | 22     | 0      | 0       | 0     | 22    | ✅     |
| Plan             | 55     | 0      | 0       | 0     | 55    | ✅     |
| Govern           | 48     | 0      | 0       | 0     | 48    | ✅     |
| Package          | 0      | 0      | 1       | 0     | 1     | ➖     |
| Create           | 40     | 0      | 6       | 0     | 46    | ✅     |
| Verify           | 32     | 0      | 0       | 1     | 32    | ❗     |
| Monitor          | 4      | 0      | 0       | 0     | 4     | ✅     |
| Framework sanity | 0      | 0      | 1       | 0     | 1     | ➖     |
| Manage           | 0      | 0      | 1       | 0     | 1     | ➖     |
+------------------+--------+--------+---------+-------+-------+--------+
| Total            | 201    | 0      | 9       | 1     | 210   | ❗     |
+------------------+--------+--------+---------+-------+-------+--------+

Merge request already approved.

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

approved this merge request

changed milestone to %16.6