Update AWS gems

This MR contains the following updates:

Package	Update	Change
aws-sdk-core	patch	'~> 3.190.0' -> '~> 3.190.1'
aws-sdk-s3	minor	'~> 1.141.0' -> '~> 1.142.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.

Immortal: This MR will be recreated if closed unmerged. Get config help if that's undesired.

---

• 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":["maintenance::dependency","type::maintenance","automation:bot-authored","backend","Engineering Productivity"],"assignees":["gitlab-dependency-update-bot"],"reviewers":["stanhu"]}

assigned to @gitlab-dependency-update-bot

Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this MR as-is.

Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this MR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: Gemfile.lock

Fetching gem metadata from https://rubygems.org/.......

Could not find gem 'aws-sdk-s3 (~> 1.142.0)' with platform 'ruby' in rubygems
repository https://rubygems.org/ or installed locally.

The source contains the following gems matching 'aws-sdk-s3 (~> 1.142.0)':
  * aws-sdk-s3-1.142.0

mentioned in issue #365045

added Engineering Productivity automation:bot-authored backend maintenancedependency typemaintenance labels

requested review from @stanhu

added 1 commit

• 2187a37f - Update AWS gems

Compare with previous version

mentioned in commit e2820d51

mentioned in merge request !140599 (merged)

mentioned in commit 838cf18f

mentioned in commit dc85634d

marked the checklist item If you want to rebase/retry this MR, check this box as completed

marked the checklist item If you want to rebase/retry this MR, check this box as incomplete

added 31 commits

• 2187a37f...dea46be9 - 30 commits from branch gitlab-org:master
• 58450e46 - Update AWS gems

Compare with previous version

I'm not sure why Gemfile.lock isn't updating.

closed