Bump Prometheus to version 3.13.2

Pratik Singhrequested to merge
upgrade-prometheus-to-version-3.13.2 into master

What does this MR do?

Upgrades the bundled Prometheus from 3.11.2 to 3.13.2.

Prometheus 3.11.2 has reached EOL. 3.13 is an LTS release with support until July 2027, so this bump moves us back onto a supported version.

Changes:

  • config/software/prometheus.rb: bump Prometheus version from 3.11.2 to 3.13.2.
  • lib/gitlab/license/analyzer.rb: allowlist two new MPL-2.0 licensed transitive Go dependencies pulled in by the new Prometheus version (github.com/hashicorp/go-version and github.com/hashicorp/nomad/api), so the license analyzer does not flag them.

Signed-off-by: psingh29 psingh@gitlab.com

Bump Prometheus to version 3.13.2

- Upgrades Prometheus from 3.11.2 to version 3.13.2.

Related https://gitlab.com/gitlab-org/omnibus-gitlab/-/work_items/10031

Changelog: changed

Signed-off-by: psingh29 <psingh@gitlab.com>

Related issues

Related #10031 (closed)

Related to #9511

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.

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. (N/A - no SSL changes)
  • If CI configuration is changed, the branch must be pushed to dev.gitlab.org to confirm regular branch builds aren't broken. (N/A - no CI configuration changes)

Expected (please provide an explanation if not completing)

  • Test plan indicating conditions for success has been posted and passes.
  • Documentation created/updated. (N/A - dependency version bump, no user-facing configuration changes)
  • Tests added. (N/A - version bump, covered by existing build and QA pipelines)
  • Integration tests added to GitLab QA. (N/A)
  • Equivalent MR/issue for the GitLab Chart opened.
  • Validate potential values for new configuration settings. (N/A - no new configuration settings)
Edited by Robert Marshall

Merge request reports