Skip to content

chore(providers): refresh provider metadata and ordering - #2318

Merged
diegosouzapw merged 1 commit into
cheaper-inference:release/v3.8.0from
backryun:release/v3.8.0
May 17, 2026
Merged

diegosouzapw merged 1 commit into
cheaper-inference:release/v3.8.0from
backryun:release/v3.8.0

Conversation

@backryun

Copy link
Copy Markdown
Contributor

Summary

  • Refreshes provider model metadata for provider registries.
  • Sorts provider entries by display name within existing dashboard provider sections.
  • Updates provider reference generation so regenerated docs preserve frontmatter and correct relative links.

Validation

  • npm run lint
  • npm run test:unit
  • npm run test:coverage
  • Coverage is still >= 60% for statements, lines, functions, and branches
  • SonarQube PR analysis is green or any remaining issues are explicitly documented below

Additional local validation run:

  • Pre-commit hook passed: docs sync, any-budget check, env/docs sync, CLI i18n, i18n coverage.
  • node --import tsx/esm --test tests/unit/provider-models-config.test.ts tests/unit/providers-page-utils.test.ts

Tests Added Or Updated

no changes.

Coverage Notes

  • This changes provider registry metadata under open-sse/ and provider dashboard ordering under src/.
  • Existing provider model config tests and provider page utility tests cover the touched behavior.
  • No coverage decrease is expected because this is metadata/order cleanup, not new production logic.

Reviewer Notes

  • No migrations or feature flags.
  • Main review focus is the refreshed provider model entries and the provider list ordering behavior within existing dashboard sections.

@backryun
backryun requested a review from diegosouzapw as a code owner May 17, 2026 00:20

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the model registries for embeddings, reranking, and providers by adding new models, removing deprecated ones, and enabling reasoning support for several entries. It also introduces alphabetical sorting for provider entries in the dashboard and enhances the documentation generation script to include versioning and corrected link paths. Feedback was provided to improve the robustness of the new provider sorting logic by adding a null check for the provider object to prevent potential runtime errors.

Comment on lines +31 to +35
function getProviderSortLabel<TProvider>(entry: ProviderEntry<TProvider>): string {
const provider = entry.provider as Record<string, unknown>;
const name = typeof provider.name === "string" ? provider.name : "";
return (name || entry.providerId).toLowerCase();
}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The getProviderSortLabel function should be more defensive when accessing entry.provider. Although provider definitions are expected to be objects, casting to Record<string, unknown> without a null check could lead to a runtime error if entry.provider is null or undefined.

Suggested change
function getProviderSortLabel<TProvider>(entry: ProviderEntry<TProvider>): string {
const provider = entry.provider as Record<string, unknown>;
const name = typeof provider.name === "string" ? provider.name : "";
return (name || entry.providerId).toLowerCase();
}
function getProviderSortLabel<TProvider>(entry: ProviderEntry<TProvider>): string {
const provider = entry.provider as Record<string, unknown> | null;
const name = (provider && typeof provider.name === "string") ? provider.name : "";
return (name || entry.providerId).toLowerCase();
}

@diegosouzapw
diegosouzapw merged commit 926ff2b into cheaper-inference:release/v3.8.0 May 17, 2026
3 checks passed
@diegosouzapw

Copy link
Copy Markdown
Collaborator

Thank you @backryun for keeping the provider catalogs up to date! 🙏

The alphabetical sorting of provider entries in the dashboard sections is a nice quality-of-life improvement, and the docs generator fixes for frontmatter and relative links ensure regenerated docs stay consistent.

Integrated into release/v3.8.0. 🚀

HouMinXi pushed a commit to HouMinXi/OmniRoute that referenced this pull request Aug 2, 2026
…erence#2318)

Integrated into release/v3.8.0 — refreshes provider model metadata, sorts dashboard provider entries by display name, and fixes docs generator relative links.
Poid-ZA pushed a commit to Poid-ZA/OmniRoute that referenced this pull request Aug 5, 2026
…erence#2318)

Integrated into release/v3.8.0 — refreshes provider model metadata, sorts dashboard provider entries by display name, and fixes docs generator relative links.
muhamadgalihsaputra pushed a commit to niyatna/NiyatnaRoute that referenced this pull request Sep 27, 2026
…erence#2318)

Integrated into release/v3.8.0 — refreshes provider model metadata, sorts dashboard provider entries by display name, and fixes docs generator relative links.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants