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

[GH-ISSUE #4596] [Website] Library - Newest doesn't really sort with the newest releases #64923

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

Originally created by @Qualzz on GitHub (May 23, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/4596

Originally assigned to: @BruceMacD on GitHub.

I'm not sure if it's the right place to post it, but the https://ollama.com/library?sort=newest newest sort is kinda misleading, as it doesn't take into account the last update of the model.

For exemple with the recent Mistral update (v3), I expect the Mistral to be one of the most recent models on the list if I sort by date, but it's way further down the list.

Exemple using the newest sort
image

The current implementation of newest sort doesn't make sense as the only date we can see on a model page is the date of the last update. I understand that newest sort probably use some internal created_at field, but this somewhat feels wrong.

Originally created by @Qualzz on GitHub (May 23, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/4596 Originally assigned to: @BruceMacD on GitHub. I'm not sure if it's the right place to post it, but the [https://ollama.com/library?sort=newest](https://ollama.com/library?sort=newest) **newest** sort is kinda misleading, as it doesn't take into account the last update of the model. For exemple with the recent Mistral update (v3), I expect the Mistral to be one of the most recent models on the list if I sort by date, but it's way further down the list. Exemple using the **newest** sort ![image](https://github.com/ollama/ollama/assets/35169816/37359611-09ff-42c6-b0a7-dc8bf4af392c) The current implementation of **newest** sort doesn't make sense as the only date we can see on a model page is the date of the last update. I understand that newest sort probably use some internal `created_at` field, but this somewhat feels wrong.
GiteaMirror added the ollama.comfeature request labels 2026-05-03 19:17:04 -05:00
GiteaMirror commented 2026-05-03 19:17:08 -05:00
Author
Owner
Copy Link

@timsankara commented on GitHub (May 23, 2024):

Looking at this... 👀

<!-- gh-comment-id:2127921343 --> @timsankara commented on GitHub (May 23, 2024): Looking at this... 👀
GiteaMirror commented 2026-05-03 19:17:09 -05:00
Author
Owner
Copy Link

@BruceMacD commented on GitHub (May 30, 2024):

Thanks for reporting this, they are actually sorted by creation time rather than updated time, so the information displayed is a bit misleading here. Leaving this open for now until we can reconcile that confusion.

<!-- gh-comment-id:2140964548 --> @BruceMacD commented on GitHub (May 30, 2024): Thanks for reporting this, they are actually sorted by creation time rather than updated time, so the information displayed is a bit misleading here. Leaving this open for now until we can reconcile that confusion.
GiteaMirror commented 2026-05-03 19:17:10 -05:00
Author
Owner
Copy Link

@Qualzz commented on GitHub (Jul 2, 2024):

Bumping this as it's almost a freebie 😸

<!-- gh-comment-id:2204011741 --> @Qualzz commented on GitHub (Jul 2, 2024): Bumping this as it's almost a freebie 😸
GiteaMirror commented 2026-05-03 19:17:10 -05:00
Author
Owner
Copy Link

@abitrolly commented on GitHub (Feb 10, 2025):

Where is the source code for ollama website?

<!-- gh-comment-id:2648441994 --> @abitrolly commented on GitHub (Feb 10, 2025): Where is the source code for `ollama` website?
GiteaMirror commented 2026-05-03 19:17:10 -05:00
Author
Owner
Copy Link

@rkrisztian commented on GitHub (Oct 17, 2025):

I got similar filtering needs, see https://github.com/ollama/ollama/issues/5233#issuecomment-3416610399

<!-- gh-comment-id:3416619222 --> @rkrisztian commented on GitHub (Oct 17, 2025): I got similar filtering needs, see https://github.com/ollama/ollama/issues/5233#issuecomment-3416610399
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 feature request ollama.com
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#64923
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?