[kaya-abdullah]

Description

Adds Prometheus to the "also listed in official ... docs" line in README.md and all eight localized READMEs (zh/ja/es/ur/hi/pt/ru/ko), right after etcd so the Apache entries stay together at the end of the line. The Prometheus integrations page now lists LibreDB Studio in its "Other" section: https://prometheus.io/docs/operating/integrations/#:~:text=LibreDB%20Studio

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Code refactoring
• Performance improvement
• Test addition or update

Related Issue

No related issue in this repo. A follow-up now that prometheus/docs#3127 is merged (2026-11-04) and live. Same shape as the etcd (#2100), Couchbase (#1910) and MariaDB Ecosystem Hub (#1892) README additions.

Changes Made

• README.md, README_zh.md, README_ja.md, README_es.md, README_ur.md, README_hi.md, README_pt.md, README_ru.md, README_ko.md: added "Prometheus" after the etcd link in the vendor-listing line, using each file's own list separator

Testing

• I have tested this locally
• I have added/updated tests
• All existing tests pass

bun run format and bun run readme:check pass, and so do the unit tests that read the READMEs (tests/unit/readme-check.test.ts, readme-numeral-names.test.ts, helm-chart-readme-recipes.test.ts). The link was opened live and the page carries the LibreDB Studio row. No executable code changed, so no test was added. Branched from the current main; no conflicts.

Test Environment

N/A, documentation-only change with no runtime behavior involved.

Screenshots (if applicable)

N/A

Checklist

• My code follows the project's code style guidelines
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have updated the documentation accordingly
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• The required CI test job passes the 100% line-coverage gate (bun run test:coverage and bun run coverage:check)
• If I changed src/lib/db/providers/, I updated the matching docs/providers/ documentation and tests/integration/db/ tests in the same PR (provider triad)
• Any dependent changes have been merged and published

Additional Notes

README-only change; the coverage gate and provider triad items do not apply. The Prometheus row has no anchor of its own, so the link uses a #:~:text=LibreDB%20Studio fragment, the same form as the etcd, Druid and OpenSearch links.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud