fix(deps): update dependency @gitlab/svgs to v3.102.0

This MR contains the following updates:

Package	Type	Update	Change	Pending
@gitlab/svgs	dependencies	minor	3.101.0 -> 3.102.0	3.103.0

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

---

Release Notes

gitlab-org/gitlab-svgs (@​gitlab/svgs)

v3.102.0

Compare Source

[3.102.0]

Changes

• Added illustration 'scan-alert-sm'

---

Configuration

Schedule: Branch creation - "before 05:00 on Monday" (UTC), 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.

added 1 commit

• 31e882b3 - fix(deps): update gitlab ui/svg

Compare with previous version

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. Assign the current milestone to the MR

6. 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","group::foundations","devops::manage","section::dev"],"assignees":["gitlab-dependency-update-bot"],"reviewers":["sdejonge","psimyn"]}

mentioned in issue #1370

added automation:bot-authored devopsmanage maintenancedependency sectiondev typemaintenance + 1 deleted label

requested review from @leipert and @psimyn

assigned to @gitlab-dependency-update-bot

added 3 commits

• 31e882b3...2adaf80b - 2 commits from branch gitlab-org/gitlab-services:main
• 47c9c793 - fix(deps): update dependency @gitlab/svgs to v3.102.0

Compare with previous version

changed title from fix(deps): update gitlab ui/svg to fix(deps): update dependency @gitlab/svgs to v3.102.0

changed the description

changed the description

enabled automatic add to merge train when the pipeline for ae632e99 succeeds

Patch release (conventional commits)

This Merge Request will trigger a patch release of Pajamas Design System, triggered by commit: 47c9c793

This will bump the third part of the version number, e.g. v1.2.3 -> v1.2.4.

Generated by Danger

approved this merge request

started a merge train

merged

mentioned in commit f83bd679

added Category:Design System groupdesign system labels and removed 1 deleted label