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

[GH-ISSUE #12728] Inaccurate last modified timestamp #8446

New Issue
Closed
opened 2026-04-12 21:07:42 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-12 21:07:42 -05:00
Owner
Copy Link

Originally created by @binarynoise on GitHub (Oct 21, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/12728

When pulling from a registry, ollama should set the "last modified" timestamp to the actual last modification of the model in the registry and not to when the ollama pull command was run.

Examples:

  • If I pulled qwen3-coder:30b right now, modified would say a few seconds ago where the real modification date would be 4 weeks ago (as displayed online).
  • If I pulled qwen3-coder:30b two weeks ago and ran ollama pull qwen3-coder:30b again, it would reset the modification date even if nothing was changed.
Originally created by @binarynoise on GitHub (Oct 21, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/12728 When pulling from a registry, `ollama` should set the "last modified" timestamp to the actual last modification of the model in the registry and not to when the `ollama pull` command was run. Examples: - If I pulled `qwen3-coder:30b` right now, `modified` would say a few seconds ago where the real modification date would be 4 weeks ago (as displayed [online](https://ollama.com/library/qwen3-coder)). - If I pulled `qwen3-coder:30b` two weeks ago and ran `ollama pull qwen3-coder:30b` again, it would reset the modification date even if nothing was changed.
GiteaMirror added the feature request label 2026-04-12 21:07:42 -05:00
GiteaMirror commented 2026-04-12 21:07:45 -05:00
Author
Owner
Copy Link

@pdevine commented on GitHub (Oct 22, 2025):

@binarynoise I'd be nervous to change this given its been the behaviour for the past 2 years. It is something that we have thought about before though, and there's actually even an issue open for it. I'll go ahead and close this as a duplicate of that issue.

<!-- gh-comment-id:3430025345 --> @pdevine commented on GitHub (Oct 22, 2025): @binarynoise I'd be nervous to change this given its been the behaviour for the past 2 years. It is something that we have thought about before though, and there's actually even an issue open for it. I'll go ahead and close this as a duplicate of that issue.
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
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#8446
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?