ReleaseTag

ReleaseTag pins the specific llama.cpp release from which native binaries are downloaded. The SDK’s P/Invoke signatures are validated against the default tag; changing it without a tested migration risks runtime failures.

Quick reference


Type	`string`
Default	`"b8816"` (on SDK v26.5.0)
Category	Native binary source
Field on	`BinaryManagerParameters.ReleaseTag`

What it does

Identifies a GitHub release under <Owner>/<Repo>. The engine downloads the asset whose name matches your platform and acceleration from that release.

"b8816" (default on v26.5.0) — the upstream release validated against this SDK version.
Older / newer tag — only when you control a matching validation story.

The Aspose team tracks upstream llama.cpp releases and bumps the default ReleaseTag in each SDK minor version. The llama-cpp-migration skill automates the per-release validation and updates.

When to change it

Scenario	Value
Default (recommended)	`"b8816"` or unset
Dev / testing a new upstream release	That tag, only in dev
Pinned to an older validated tag	Specific older tag

Changing ReleaseTag to a tag whose P/Invoke signatures differ from the SDK’s expectations produces runtime crashes. Never ship an unvalidated tag to production.

Example

var preset = new Qwen25Preset();
preset.BinaryManagerParameters.ReleaseTag = "b8816";  // explicit pin for reproducibility

Interactions

Owner and Repo — together with ReleaseTag form the source URL.
BinaryPath — cache location per tag; different tags use different subfolders.
Session persistence portability — sessions assume a consistent ReleaseTag across save / load.

What’s next

Binary download fails troubleshooting — common issues.
Binary manager hub — all binary-manager knobs.
Offline deployment — pre-populating binaries for a pinned tag.

Repo BinaryPath