Update dependency nokogiri to '~> 1.14', '>= 1.14.3'

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
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.
Check if bundle install works locally, in the context of GDK.
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 @sliaquat and @mlapierre

added 1 commit

f191f61a - Update dependency nokogiri to '~> 1.14', '>= 1.14.3'

Compare with previous version

approved this merge request

merged

@sliaquat, did you forget to run a pipeline before you merged this work? Based on our code review process, if the latest pipeline was created more than 6 hours ago OR 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.