chore(deps): update module golang.org/x/crypto to v0.28.0

This MR contains the following updates:

Package	Type	Update	Change
golang.org/x/crypto	require	minor	v0.27.0 -> v0.28.0

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

---

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.

added 1 commit

• e6edb53f - chore(deps): update module golang.org/x/crypto to v0.28.0

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::code review","devops::create","section::dev","Category:GitLab CLI"],"assignees":["gitlab-dependency-update-bot"],"reviewers":["garyh","shekharpatnaik","viktomas"]}

added Category:GitLab CLI automation:bot-authored devopscreate groupcode review maintenancedependency sectiondev typemaintenance labels

requested review from @shekharpatnaik

assigned to @gitlab-dependency-update-bot

added 3 commits

• e6edb53f...7c5a291d - 2 commits from branch gitlab-org:main
• 645e604a - chore(deps): update module golang.org/x/crypto to v0.28.0

Compare with previous version

approved this merge request

started a merge train

Reviewer roulette

Changes that require review have been detected! A merge request is normally reviewed by both a reviewer and a maintainer in its primary category and by a maintainer in all other categories.

To spread load more evenly across eligible reviewers, Danger has picked a candidate for each review slot. 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, mention them as you normally would! Danger does not automatically notify them for you.

Reviewer	Maintainer
@eurie (UTC-4)	@hacks4oats (UTC-4)

Generated by 🚫 Danger

merged

mentioned in commit 75bbcd0f