Update prometheus-client requirement from ~> 2.0 to >= 2, < 5

[dependabot]

Updates the requirements on prometheus-client to permit the latest version.

Release notes

Sourced from prometheus-client's releases.

v4.1.0

4.1.0 / 2023-03-20

Codename: They finally made a point release

Small improvements

• #264 Add JRuby 9.3 to build matrix: JRuby 9.3 was released, and added as an officially supported version

• #273 Add Ruby 3.2 to build matrix: Ruby 3.2 was released, and added as an officially supported version

• #280 Optimize incrementing values in DirectFileStore adapter: There were some expensive method calls being made multiple times when they didn't need to be for simple increments. This PR introduces a specialised implementation for that case.

• #277 Allow use of instance and job labels: It's now possible to set the instance and job labels on metrics, where previously they had been reserved.

  The reason we'd reserved them is that Prometheus automatically generates values for them when it scrapes a target, and we didn't want to cause a collision. It turns out Prometheus handles that collision just fine.

  By default, Prometheus server will prepend exported_ to them if they're present in the scraped data (i.e. exported_instance and exported_job). Users can set honor_labels in their Prometheus server config if they prefer the labels from the scraped metric data to take precedence over the labels generated by the server.

Bug fixes

• #268 Use lowercase response headers in Rack example: Rack 3.0.0 started requiring this for compatibility with HTTP/2
• #271 Use lowercase for HTTP headers in middleware: Fixes the same issue from above in our middleware
• #270 Small compatibility fixes in Rack example: Apple have taken port 5000 for AirPlay, so we had to move away from it. Go has changed how you install binaries, so we updated those instructions too.

v4.0.0 / 2022-03-27

Codename: The "barely a release" release

This version contains a single - sadly breaking - change.

• #251 Remove framework-specific route detection from collector middleware: In 3.0.0 we shipped a feature that attempted to use framework-specific information to determine the path of the request in Prometheus::Middleware::Collector.

  Sadly, we found out after shipping it that it was prone to multiple issues. We spent a decent amount of time looking into them in depth, and came to the conclusion that there wasn't any reasonable way to fix them - the issues are inherent to the feature.

  For a full, detailed write-up of our investigation, see this comment.

  Almost all users will be unaffected by this change, but it is breaking per the definition we've used for previous releases, so we've erred on the side of caution and bumped the major version to communicate that.

  If you use Sinatra or Grape with the Prometheus::Middleware::Collector, you will notice different path labels being generated. If not, this release will change nothing for you.

  If you want the behaviour from 3.0.0 - or any custom path label generation you'd prefer - we've updated [our collector middleware

... (truncated)

Changelog

Sourced from prometheus-client's changelog.

4.1.0 / 2023-03-20

Codename: They finally made a point release

Small improvements

• #264 Add JRuby 9.3 to build matrix: JRuby 9.3 was released, and added as an officially supported version

• #273 Add Ruby 3.2 to build matrix: Ruby 3.2 was released, and added as an officially supported version

• #280 Optimize incrementing values in DirectFileStore adapter: There were some expensive method calls being made multiple times when they didn't need to be for simple increments. This PR introduces a specialised implementation for that case.

• #277 Allow use of instance and job labels: It's now possible to set the instance and job labels on metrics, where previously they had been reserved.

  The reason we'd reserved them is that Prometheus automatically generates values for them when it scrapes a target, and we didn't want to cause a collision. It turns out Prometheus handles that collision just fine.

  By default, Prometheus server will prepend exported_ to them if they're present in the scraped data (i.e. exported_instance and exported_job). Users can set honor_labels in their Prometheus server config if they prefer the labels from the scraped metric data to take precedence over the labels generated by the server.

Bug fixes

• #268 Use lowercase response headers in Rack example: Rack 3.0.0 started requiring this for compatibility with HTTP/2
• #271 Use lowercase for HTTP headers in middleware: Fixes the same issue from above in our middleware
• #270 Small compatibility fixes in Rack example: Apple have taken port 5000 for AirPlay, so we had to move away from it. Go has changed how you install binaries, so we updated those instructions too.

4.0.0 / 2022-03-27

Codename: The "barely a release" release

This version contains a single - sadly breaking - change.

• #251 Remove framework-specific

... (truncated)

Commits

• 1fc94f8 Merge pull request #282 from prometheus/sinjo-fix-date
• 5060390 Fix release date in CHANGELOG.md
• 4c3499f Merge pull request #279 from prometheus/sinjo-prepare-4-1-0
• f285c03 Add missing entries to CHANGELOG.md
• 2022a41 Merge pull request #280 from splattael/perf-inc
• 3ee337e Optimize incrementing values in DirectFileStore adapter
• 52e0416 Prepare release 4.1.0
• db756a1 Merge pull request #277 from prometheus/sinjo-loosen-reserved-labels
• e53f7ed Allow use of instance and job labels
• 825b35c Merge pull request #273 from prometheus/sinjo-add-ruby-3-2
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)