chore(deps): bump prom-client from 12.0.0 to 13.1.0

[dependabot]

Bumps prom-client from 12.0.0 to 13.1.0.

Release notes

Sourced from prom-client's releases.

v13.1.0

[13.1.0] - 2021-01-24

Changed

• fix: push client attempting to write Promise (fixes #390)
• types: improve type checking of labels
• fix: Summary#observe should throw when adding additional labels to labelset (fixes #262)

Added

• feat: added the ability to pass labels as an object to labels() and remove()
• Added: More examples with commented output

13.0.0

[13.0.0] - 2020-12-16

Breaking

• changed: The following functions are now async (return a promise): registry.metrics() registry.getMetricsAsJSON() registry.getMetricsAsArray() registry.getSingleMetricAsString()

  If your metrics server has a line like res.send(register.metrics()), you should change it to res.send(await register.metrics()).

  Additionally, all metric types now accept an optional collect function, which is called when the metric's value should be collected and within which you should set the metric's value. You should provide a collect function for point-in-time metrics (e.g. current memory usage, as opposed to HTTP request durations that are continuously logged in a histogram).

• changed: register.clusterMetrics() no longer accepts a callback; it only returns a promise.

• removed: v12.0.0 added the undocumented functions registry.registerCollector and registry.collectors(). These have been removed. If you were using them, you should instead provide a collect function as described above.

Changed

• fix: provide nodejs_version_info metric value after calling registry.resetMetrics() (#238)
• fix: provide process_max_fds metric value after calling registry.resetMetrics()
• fix: provide process_start_time_seconds metric value after calling registry.resetMetrics()
• chore: improve performance of registry.getMetricAsPrometheusString
• chore: refactor metrics to reduce code duplication
• chore: replace utils.getPropertiesFromObj with Object.values
• chore: remove unused catch bindings

... (truncated)

Changelog

Sourced from prom-client's changelog.

[13.1.0] - 2021-01-24

Changed

• fix: push client attempting to write Promise (fixes #390)
• types: improve type checking of labels
• fix: Summary#observe should throw when adding additional labels to labelset (fixes #262)

Added

• feat: added the ability to pass labels as an object to labels() and remove()
• Added: More examples with commented output

[13.0.0] - 2020-12-16

Breaking

• changed: The following functions are now async (return a promise): registry.metrics() registry.getMetricsAsJSON() registry.getMetricsAsArray() registry.getSingleMetricAsString()

  If your metrics server has a line like res.send(register.metrics()), you should change it to res.send(await register.metrics()).

  Additionally, all metric types now accept an optional collect function, which is called when the metric's value should be collected and within which you should set the metric's value. You should provide a collect function for point-in-time metrics (e.g. current memory usage, as opposed to HTTP request durations that are continuously logged in a histogram).

• changed: register.clusterMetrics() no longer accepts a callback; it only returns a promise.

• removed: v12.0.0 added the undocumented functions registry.registerCollector and registry.collectors(). These have been removed. If you were using them, you should instead provide a collect function as described above.

Changed

• fix: provide nodejs_version_info metric value after calling registry.resetMetrics() (#238)
• fix: provide process_max_fds metric value after calling registry.resetMetrics()
• fix: provide process_start_time_seconds metric value after calling registry.resetMetrics()
• chore: improve performance of registry.getMetricAsPrometheusString
• chore: refactor metrics to reduce code duplication
• chore: replace utils.getPropertiesFromObj with Object.values
• chore: remove unused catch bindings
• chore: upgrade Prettier to 2.x
• fix: startTimer returns number in typescript instead of void

... (truncated)

Commits

• e29a172 v13.1.0
• b3199da docs: add example files with console log output
• 5ee2d47 fix: summary.observe should validate labels correctly
• 3a86d05 feat: Added the ability to pass labels as an object to labels() and remove()
• 487611c types: allow readonly labelNames in metric configuration
• 961a833 docs: add note and example about setting agent
• 83f7867 Fix push gateway attempting to write promise instead of awaiting (#419)
• bec8067 Updated CHANGELOG with 13.0.0
• 2c9ae0e 13.0.0
• fecd75e feat: added support for adding labels to default metrics (#374)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by zbjornson, a new releaser for prom-client since your current version.

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)

[WikiRik]

Will be fixed in #2

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.