Prepare model repo for API-free discovery and verified downloads#28
Merged
Conversation
TurboGit
reviewed
May 25, 2026
| @@ -0,0 +1,7 @@ | |||
| { | |||
Member
There was a problem hiding this comment.
Probably needs a note here:
https://github.com/darktable-org/darktable-ai/wiki/Creating-a-release#2-cut-the-release-branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two changes that let darktable discover and download models without touching
api.github.com(and so without being subject to its 60 req/hr unauthenticated rate limit – breaks users behind shared NAT, in CI, in classrooms).releases-index.json(new, tracked at repo root): maps darktableX.Y.Zto the model-release tag built for it. darktable reads it fromraw.githubusercontent.com/.../HEAD/releases-index.json(CDN, branch-agnostic viaHEAD, no API limit).schema: 1shape is frozen forever so old binaries keep working; future schemas live in parallel keys.versions.jsoncarries SHA256 per model.dtai versionsgained--artifacts-dir; when CI passes the built.dtmodeldir, the manifest gains a nestedmodels[id] = {version, sha256}shape. darktable reads the SHA from there instead of an API call per asset. CLI accepts both nested (CI) and flat (localoutput/) layouts. Bothrelease.ymlandnightly.ymlupdated to download artifacts before generating the manifest.Breaking change
models[id]went from string → object. Old darktable installs silently stop detecting model updates until they upgrade. No crash; matching darktable C-side PR ships separately.