Bump ERB gem to 4.0.3.1

Robert Marshallrequested to merge
backport-19-0-update-erb-gem into 19-0-stable

What does this MR do?

Updates the ERB ruby gem to version 4.0.3.1 to pick up the upstream fix for the publicly-disclosed vulnerability addressed in the 4.0.3.x release.

Bump ERB gem to 4.0.3.1

- Updates the ERB ruby gem to version 4.0.3.1.

Changelog: security

Signed-off-by: Robert Marshall <rmarshall@gitlab.com>

Risk: Low. Gem version bump only; no API surface changes.

Test plan:

  • CI pipeline passes against the bump.
  • The bundled erb gem on a built package reports version 4.0.3.1.

Related issues

https://gitlab.com/gitlab-org/omnibus-gitlab/-/work_items/9858+s

Checklist

See Definition of done.

For anything in this list which will not be completed, please provide a reason in the MR discussion.

Required

  • MR title and description are up to date, accurate, and descriptive.
  • MR targeting the appropriate branch.
  • Latest Merge Result pipeline is green.
  • When ready for review, MR is labeled workflowready for review per the Distribution MR workflow.
  • The UBT version and corresponding checksum hash have been updated and referenced in the merge request if applicable.
    • UBT EE pipeline (Trigger:ee-package-ubt) is green

For GitLab team members

If you don't have access to this, the reviewer should trigger these jobs for you during the review process.

  • The manual Trigger:ee-package jobs have a green pipeline running against latest commit.
  • If config/software or config/patches directories are changed, make sure the build-package-on-all-os job within the Trigger:ee-package downstream pipeline succeeded.
  • If you are changing anything SSL related, then the Trigger:package:fips manual job within the Trigger:ee-package downstream pipeline must succeed.
  • If CI configuration is changed, the branch must be pushed to dev.gitlab.org to confirm regular branch builds aren't broken.

Expected (please provide an explanation if not completing)

  • Test plan indicating conditions for success has been posted and passes.
  • Documentation created/updated.
  • Tests added.
  • Integration tests added to GitLab QA.
  • Equivalent MR/issue for the GitLab Chart opened.
  • Validate potential values for new configuration settings. Formats such as integer 10, duration 10s, URI scheme://user:passwd@host:port may require quotation or other special handling when rendered in a template and written to a configuration file.

Merge request reports