github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-08 17:49:24 -05:00
Code Issues 14.6k Packages Projects Releases 122 Wiki Activity

[PR #15735] server: add v2 manifest path #61979

New Issue
Open
opened 2026-04-29 16:56:32 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-29 16:56:32 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/ollama/ollama/pull/15735
Author: @pdevine
Created: 4/21/2026
Status: 🔄 Open

Base: main ← Head: pdevine/addressable-manifest

📝 Commits (2)

  • 7bbcd2e server: add v2 manifest path
  • 7bcdb25 fix failing client2 unit tests

📊 Changes

11 files changed (+1033 additions, -197 deletions)

View changed files

📝 manifest/manifest.go (+408 -45)
📝 manifest/manifest_test.go (+309 -2)
📝 manifest/paths.go (+176 -1)
📝 server/images.go (+20 -48)
📝 server/internal/registry/server.go (+4 -0)
📝 server/routes.go (+8 -6)
📝 server/routes_create_test.go (+46 -46)
📝 server/routes_delete_test.go (+6 -13)
📝 server/routes_test.go (+13 -3)
📝 x/imagegen/manifest/manifest.go (+3 -33)
📝 x/imagegen/manifest/manifest_test.go (+40 -0)

📄 Description

This change adds a new manifest-v2/ path for new models created with the create/pull/copy commands. Under manifest-v2, manifests are now just blobs which are content addressable similar to tensors/config files. The named tags instead will symlink/hard link/contain a copy depending on what the file system supports.

Downgrades to older versions of ollama are still possible, but any create/pull/copy done with the newer version will potentially have its blobs pruned by the older version.

manifest-v2 also changes the default registry name to ollama.com instead of registry.ollama.ai.

🔄 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/15735 **Author:** [@pdevine](https://github.com/pdevine) **Created:** 4/21/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `pdevine/addressable-manifest` --- ### 📝 Commits (2) - [`7bbcd2e`](https://github.com/ollama/ollama/commit/7bbcd2e6be5c0f635d380984e1b0b45b7ce825e9) server: add v2 manifest path - [`7bcdb25`](https://github.com/ollama/ollama/commit/7bcdb250b9ea4cdc104269af5849354c1ead7c79) fix failing client2 unit tests ### 📊 Changes **11 files changed** (+1033 additions, -197 deletions) <details> <summary>View changed files</summary> 📝 `manifest/manifest.go` (+408 -45) 📝 `manifest/manifest_test.go` (+309 -2) 📝 `manifest/paths.go` (+176 -1) 📝 `server/images.go` (+20 -48) 📝 `server/internal/registry/server.go` (+4 -0) 📝 `server/routes.go` (+8 -6) 📝 `server/routes_create_test.go` (+46 -46) 📝 `server/routes_delete_test.go` (+6 -13) 📝 `server/routes_test.go` (+13 -3) 📝 `x/imagegen/manifest/manifest.go` (+3 -33) 📝 `x/imagegen/manifest/manifest_test.go` (+40 -0) </details> ### 📄 Description This change adds a new manifest-v2/ path for new models created with the create/pull/copy commands. Under manifest-v2, manifests are now just blobs which are content addressable similar to tensors/config files. The named tags instead will symlink/hard link/contain a copy depending on what the file system supports. Downgrades to older versions of ollama are still possible, but any create/pull/copy done with the newer version will potentially have its blobs pruned by the older version. manifest-v2 also changes the default registry name to `ollama.com` instead of `registry.ollama.ai`. --- <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-29 16:56:32 -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#61979
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?