Bump prometheus-client from 0.24.1 to 0.25.0 in /app/backend

[dependabot]

Bumps prometheus-client from 0.24.1 to 0.25.0.

Release notes

Sourced from prometheus-client's releases.

v0.25.0

What's Changed

• Fix spaces in grouping key values for push_to_gateway by @​veeceey in prometheus/client_python#1156
• Support MultiProcessCollector in RestrictedRegistry by @​mathias-kende in prometheus/client_python#1150

Full Changelog: prometheus/client_python@v0.24.1...v0.25.0

Commits

• 2cd1738 Release 0.25.0
• daa1626 docs: add API reference for all metric types (#1159)
• 8673912 Support MultiProcessCollector in RestrictedRegistry. (#1150)
• 671f75c Fix spaces in grouping key values for push_to_gateway (#1156)
• 1cf53fe Fix server shutdown documentation (#1155)
• a854135 Migrate to Github Actions (#1153)
• See full diff in compare view

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
couchers	Ready	Preview	May 4, 2026 0:35am

[aapeliv]

key change for us: prometheus/client_python#1150

[aapeliv]

Opus on whether this interacts with our usage:

---

No impact. Here's why:

Couchers' usage (app/backend/src/couchers/metrics.py:36-37):

registry: CollectorRegistry = CollectorRegistry()
multiprocess.MultiProcessCollector(registry)

Then generate_latest(registry) is called in create_prometheus_server — that's the unrestricted full-registry path.

What the patch changes:

1. Adds an opt-in support_collectors_without_names=False constructor param (default off, so behavior is unchanged unless you pass it).
2. Modifies RestrictedRegistry.collect() — the code path used by restricted_registry(['some_name']).collect() for filtering by name.

Couchers doesn't use either:

• We construct CollectorRegistry() with no args → new flag defaults to False, identical to old behavior.
• We never call restricted_registry(...) (grep confirms zero hits) — so the modified code path isn't exercised.
• generate_latest(registry) walks all collectors directly; the RestrictedRegistry class isn't involved.

So this PR is fully backward-compatible for our setup. The new flag would only become relevant if we ever wanted to support ?name[]=foo style scrape filtering against the multiprocess collector — which we don't currently do.

[github-actions]

📝 Release Notes

This PR does not need to be included in release notes.

Reason: This PR is a routine dependency update to an internal monitoring library, with no user-facing changes and no meaningful impact on Couchers' current usage according to the discussion.

🤖 Bot Debug Information

Model: couchers.openai.gpt-5.4
Decision: exclude
Reasoning: This PR is a routine dependency update to an internal monitoring library, with no user-facing changes and no meaningful impact on Couchers' current usage according to the discussion.