github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-08 00:51:34 -05:00
Code Issues 14.5k Packages Projects Releases 120 Wiki Activity

[PR #14392] app/ui: update stale cloud model names in FEATURED_MODELS #25192

New Issue
Open
opened 2026-04-19 18:03:59 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-19 18:03:59 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/ollama/ollama/pull/14392
Author: @RajeshKumar11
Created: 2/24/2026
Status: 🔄 Open

Base: main ← Head: fix/app-ui-stale-cloud-models

📝 Commits (1)

  • 9752383 app/ui: update stale cloud model names in FEATURED_MODELS

📊 Changes

1 file changed (+2 additions, -2 deletions)

View changed files

📝 app/ui/app/src/utils/mergeModels.ts (+2 -2)

📄 Description

Problem

FEATURED_MODELS in app/ui/app/src/utils/mergeModels.ts contains two stale cloud model names that no longer match the current models in cmd/config/integrations.go:

File Stale value Current value
mergeModels.ts minimax-m2:cloud minimax-m2.5:cloud
mergeModels.ts glm-4.6:cloud glm-5:cloud

The backend (integrations.go) was updated to minimax-m2.5:cloud and glm-5:cloud (as recommended models) but the frontend FEATURED_MODELS list was never updated to match. As a result:

  • The GUI model picker shows the outdated minimax-m2:cloud and glm-4.6:cloud names
  • minimax-m2.5:cloud and glm-5:cloud are not shown as featured models

Fixes #14363

Fix

Replace the two stale entries in FEATURED_MODELS to match integrations.go:

  • minimax-m2:cloud → minimax-m2.5:cloud
  • glm-4.6:cloud → glm-5:cloud

Tests

All 4 existing mergeModels.test.ts tests pass without modification — the tests are driven dynamically off FEATURED_MODELS so they automatically validate the updated names.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/ollama/ollama/pull/14392 **Author:** [@RajeshKumar11](https://github.com/RajeshKumar11) **Created:** 2/24/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `fix/app-ui-stale-cloud-models` --- ### 📝 Commits (1) - [`9752383`](https://github.com/ollama/ollama/commit/9752383fc45ff3895f8688d5b6f2769213460359) app/ui: update stale cloud model names in FEATURED_MODELS ### 📊 Changes **1 file changed** (+2 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `app/ui/app/src/utils/mergeModels.ts` (+2 -2) </details> ### 📄 Description ## Problem `FEATURED_MODELS` in `app/ui/app/src/utils/mergeModels.ts` contains two stale cloud model names that no longer match the current models in `cmd/config/integrations.go`: | File | Stale value | Current value | |---|---|---| | `mergeModels.ts` | `minimax-m2:cloud` | `minimax-m2.5:cloud` | | `mergeModels.ts` | `glm-4.6:cloud` | `glm-5:cloud` | The backend (`integrations.go`) was updated to `minimax-m2.5:cloud` and `glm-5:cloud` (as recommended models) but the frontend `FEATURED_MODELS` list was never updated to match. As a result: - The GUI model picker shows the outdated `minimax-m2:cloud` and `glm-4.6:cloud` names - `minimax-m2.5:cloud` and `glm-5:cloud` are not shown as featured models Fixes #14363 ## Fix Replace the two stale entries in `FEATURED_MODELS` to match `integrations.go`: - `minimax-m2:cloud` → `minimax-m2.5:cloud` - `glm-4.6:cloud` → `glm-5:cloud` ## Tests All 4 existing `mergeModels.test.ts` tests pass without modification — the tests are driven dynamically off `FEATURED_MODELS` so they automatically validate the updated names. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-19 18:03:59 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
amd
api
app
bug
build
cli
cloud
compatibility
context-length
create
docker
documentation
embeddings
feature request
feedback wanted
good first issue
gpt-oss
gpu
harmony
help wanted
image
install
intel
js
launch
linux
macos
memory
mlx
model
needs more info
networking
nvidia
ollama.com
performance
pull-request
Mirrored from GitHub Pull Request
 python
question
registry
rendering
thinking
tools
top
vulkan
windows
wsl
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#25192
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?