Skip to content

Releases: mcpg-dev/mcpg-backend-llm-shared

v0.1.0-beta.44

v0.1.0-beta.44 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 23 Oct 15:58

Release of mcpg-backend-llm-shared at v0.1.0-beta.44.
Issues are welcome; pull requests cannot be merged here — development happens upstream.

This crate is consumed by git reference — it is not published to crates.io:

[dependencies]
mcpg-backend-llm-shared = { git = "https://github.com/mcpg-dev/mcpg-backend-llm-shared", tag = "v0.1.0-beta.44" }

(binaries: cargo install --git https://github.com/mcpg-dev/mcpg-backend-llm-shared --tag v0.1.0-beta.44 mcpg-backend-llm-shared, or use the packed assets below)

Every asset is signed with cosign (keyless, Sigstore transparency log);
public releases also carry a SLSA build-provenance attestation. Verify one with:

gh attestation verify <file> --repo mcpg-dev/mcpg-backend-llm-shared

A resolved Cargo.lock and an SPDX SBOM are attached. Every lane built --locked against that exact
lockfile, so it describes these binaries rather than a later resolution — to rebuild this version
byte-for-byte, drop it in as Cargo.lock and build --locked.
Library and plugin releases also carry a cargo-public-api diff of the public Rust surface against the
previous release tag — these releases do not ship a changelog, and that diff is the machine-checkable
answer to what changed.

macOS: the aarch64-apple-darwin binaries are signed by cosign but are not Apple-codesigned or
notarised, so Gatekeeper quarantines them on download and reports the binary as damaged. That is a policy
decision by macOS, not a corrupt artifact — verify the cosign signature, then clear the quarantine flag:

xattr -d com.apple.quarantine ./<binary>

v0.1.0-beta.43

v0.1.0-beta.43 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 19 Oct 06:19

Release of mcpg-backend-llm-shared at v0.1.0-beta.43.
Issues are welcome; pull requests cannot be merged here — development happens upstream.

This crate is consumed by git reference — it is not published to crates.io:

[dependencies]
mcpg-backend-llm-shared = { git = "https://github.com/mcpg-dev/mcpg-backend-llm-shared", tag = "v0.1.0-beta.43" }

(binaries: cargo install --git https://github.com/mcpg-dev/mcpg-backend-llm-shared --tag v0.1.0-beta.43 mcpg-backend-llm-shared, or use the packed assets below)

Every asset is signed with cosign (keyless, Sigstore transparency log);
public releases also carry a SLSA build-provenance attestation. Verify one with:

gh attestation verify <file> --repo mcpg-dev/mcpg-backend-llm-shared

A resolved Cargo.lock and an SPDX SBOM are attached. Every lane built --locked against that exact
lockfile, so it describes these binaries rather than a later resolution — to rebuild this version
byte-for-byte, drop it in as Cargo.lock and build --locked.
Library and plugin releases also carry a cargo-public-api diff of the public Rust surface against the
previous release tag — these releases do not ship a changelog, and that diff is the machine-checkable
answer to what changed.

macOS: the aarch64-apple-darwin binaries are signed by cosign but are not Apple-codesigned or
notarised, so Gatekeeper quarantines them on download and reports the binary as damaged. That is a policy
decision by macOS, not a corrupt artifact — verify the cosign signature, then clear the quarantine flag:

xattr -d com.apple.quarantine ./<binary>

v0.1.0-beta.42

v0.1.0-beta.42 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 18 Oct 23:54

Release of mcpg-backend-llm-shared at v0.1.0-beta.42.
Issues are welcome; pull requests cannot be merged here — development happens upstream.

This crate is consumed by git reference — it is not published to crates.io:

[dependencies]
mcpg-backend-llm-shared = { git = "https://github.com/mcpg-dev/mcpg-backend-llm-shared", tag = "v0.1.0-beta.42" }

(binaries: cargo install --git https://github.com/mcpg-dev/mcpg-backend-llm-shared --tag v0.1.0-beta.42 mcpg-backend-llm-shared, or use the packed assets below)

Every asset is signed with cosign (keyless, Sigstore transparency log);
public releases also carry a SLSA build-provenance attestation. Verify one with:

gh attestation verify <file> --repo mcpg-dev/mcpg-backend-llm-shared

A resolved Cargo.lock and an SPDX SBOM are attached. Every lane built --locked against that exact
lockfile, so it describes these binaries rather than a later resolution — to rebuild this version
byte-for-byte, drop it in as Cargo.lock and build --locked.
Library and plugin releases also carry a cargo-public-api diff of the public Rust surface against the
previous release tag — these releases do not ship a changelog, and that diff is the machine-checkable
answer to what changed.

macOS: the aarch64-apple-darwin binaries are signed by cosign but are not Apple-codesigned or
notarised, so Gatekeeper quarantines them on download and reports the binary as damaged. That is a policy
decision by macOS, not a corrupt artifact — verify the cosign signature, then clear the quarantine flag:

xattr -d com.apple.quarantine ./<binary>

v0.1.0-beta.41

v0.1.0-beta.41 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 17 Oct 21:08

Release of mcpg-backend-llm-shared at v0.1.0-beta.41.
Issues are welcome; pull requests cannot be merged here — development happens upstream.

This crate is consumed by git reference — it is not published to crates.io:

[dependencies]
mcpg-backend-llm-shared = { git = "https://github.com/mcpg-dev/mcpg-backend-llm-shared", tag = "v0.1.0-beta.41" }

(binaries: cargo install --git https://github.com/mcpg-dev/mcpg-backend-llm-shared --tag v0.1.0-beta.41 mcpg-backend-llm-shared, or use the packed assets below)

Every asset is signed with cosign (keyless, Sigstore transparency log);
public releases also carry a SLSA build-provenance attestation. Verify one with:

gh attestation verify <file> --repo mcpg-dev/mcpg-backend-llm-shared

A resolved Cargo.lock and an SPDX SBOM are attached. Every lane built --locked against that exact
lockfile, so it describes these binaries rather than a later resolution — to rebuild this version
byte-for-byte, drop it in as Cargo.lock and build --locked.
Library and plugin releases also carry a cargo-public-api diff of the public Rust surface against the
previous release tag — these releases do not ship a changelog, and that diff is the machine-checkable
answer to what changed.

macOS: the aarch64-apple-darwin binaries are signed by cosign but are not Apple-codesigned or
notarised, so Gatekeeper quarantines them on download and reports the binary as damaged. That is a policy
decision by macOS, not a corrupt artifact — verify the cosign signature, then clear the quarantine flag:

xattr -d com.apple.quarantine ./<binary>

v0.1.0-beta.40

v0.1.0-beta.40 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 17 Oct 04:26

Release of mcpg-backend-llm-shared at v0.1.0-beta.40.
Issues are welcome; pull requests cannot be merged here — development happens upstream.

This crate is consumed by git reference — it is not published to crates.io:

[dependencies]
mcpg-backend-llm-shared = { git = "https://github.com/mcpg-dev/mcpg-backend-llm-shared", tag = "v0.1.0-beta.40" }

(binaries: cargo install --git https://github.com/mcpg-dev/mcpg-backend-llm-shared --tag v0.1.0-beta.40 mcpg-backend-llm-shared, or use the packed assets below)

Every asset is signed with cosign (keyless, Sigstore transparency log);
public releases also carry a SLSA build-provenance attestation. Verify one with:

gh attestation verify <file> --repo mcpg-dev/mcpg-backend-llm-shared

A resolved Cargo.lock and an SPDX SBOM are attached. Every lane built --locked against that exact
lockfile, so it describes these binaries rather than a later resolution — to rebuild this version
byte-for-byte, drop it in as Cargo.lock and build --locked.
Library and plugin releases also carry a cargo-public-api diff of the public Rust surface against the
previous release tag — these releases do not ship a changelog, and that diff is the machine-checkable
answer to what changed.

macOS: the aarch64-apple-darwin binaries are signed by cosign but are not Apple-codesigned or
notarised, so Gatekeeper quarantines them on download and reports the binary as damaged. That is a policy
decision by macOS, not a corrupt artifact — verify the cosign signature, then clear the quarantine flag:

xattr -d com.apple.quarantine ./<binary>

v0.1.0-beta.39

v0.1.0-beta.39 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 28 Sep 23:54

Release of mcpg-backend-llm-shared at v0.1.0-beta.39.
Issues are welcome; pull requests cannot be merged here — development happens upstream.

This crate is consumed by git reference — it is not published to crates.io:

[dependencies]
mcpg-backend-llm-shared = { git = "https://github.com/mcpg-dev/mcpg-backend-llm-shared", tag = "v0.1.0-beta.39" }

(binaries: cargo install --git https://github.com/mcpg-dev/mcpg-backend-llm-shared --tag v0.1.0-beta.39 mcpg-backend-llm-shared, or use the packed assets below)

Every asset is signed with cosign (keyless, Sigstore transparency log);
public releases also carry a SLSA build-provenance attestation. Verify one with:

gh attestation verify <file> --repo mcpg-dev/mcpg-backend-llm-shared

A resolved Cargo.lock and an SPDX SBOM are attached. Every lane built --locked against that exact
lockfile, so it describes these binaries rather than a later resolution — to rebuild this version
byte-for-byte, drop it in as Cargo.lock and build --locked.
Library and plugin releases also carry a cargo-public-api diff of the public Rust surface against the
previous release tag — these releases do not ship a changelog, and that diff is the machine-checkable
answer to what changed.

macOS: the aarch64-apple-darwin binaries are signed by cosign but are not Apple-codesigned or
notarised, so Gatekeeper quarantines them on download and reports the binary as damaged. That is a policy
decision by macOS, not a corrupt artifact — verify the cosign signature, then clear the quarantine flag:

xattr -d com.apple.quarantine ./<binary>

v0.1.0-beta.37

v0.1.0-beta.37 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 26 Sep 05:11

Release of mcpg-backend-llm-shared at v0.1.0-beta.37.
Issues are welcome; pull requests cannot be merged here — development happens upstream.

This crate is consumed by git reference — it is not published to crates.io:

[dependencies]
mcpg-backend-llm-shared = { git = "https://github.com/mcpg-dev/mcpg-backend-llm-shared", tag = "v0.1.0-beta.37" }

(binaries: cargo install --git https://github.com/mcpg-dev/mcpg-backend-llm-shared --tag v0.1.0-beta.37 mcpg-backend-llm-shared, or use the packed assets below)

Every asset is signed with cosign (keyless, Sigstore transparency log);
public releases also carry a SLSA build-provenance attestation. Verify one with:

gh attestation verify <file> --repo mcpg-dev/mcpg-backend-llm-shared

A resolved Cargo.lock and an SPDX SBOM are attached. Every lane built --locked against that exact
lockfile, so it describes these binaries rather than a later resolution — to rebuild this version
byte-for-byte, drop it in as Cargo.lock and build --locked.
Library and plugin releases also carry a cargo-public-api diff of the public Rust surface against the
previous release tag — these releases do not ship a changelog, and that diff is the machine-checkable
answer to what changed.

macOS: the aarch64-apple-darwin binaries are signed by cosign but are not Apple-codesigned or
notarised, so Gatekeeper quarantines them on download and reports the binary as damaged. That is a policy
decision by macOS, not a corrupt artifact — verify the cosign signature, then clear the quarantine flag:

xattr -d com.apple.quarantine ./<binary>

v0.1.0-beta.36

v0.1.0-beta.36 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 25 Sep 07:13

Release of mcpg-backend-llm-shared at v0.1.0-beta.36.
Issues are welcome; pull requests cannot be merged here — development happens upstream.

This crate is consumed by git reference — it is not published to crates.io:

[dependencies]
mcpg-backend-llm-shared = { git = "https://github.com/mcpg-dev/mcpg-backend-llm-shared", tag = "v0.1.0-beta.36" }

(binaries: cargo install --git https://github.com/mcpg-dev/mcpg-backend-llm-shared --tag v0.1.0-beta.36 mcpg-backend-llm-shared, or use the packed assets below)

Every asset is signed with cosign (keyless, Sigstore transparency log);
public releases also carry a SLSA build-provenance attestation. Verify one with:

gh attestation verify <file> --repo mcpg-dev/mcpg-backend-llm-shared

A resolved Cargo.lock and an SPDX SBOM are attached. Every lane built --locked against that exact
lockfile, so it describes these binaries rather than a later resolution — to rebuild this version
byte-for-byte, drop it in as Cargo.lock and build --locked.
Library and plugin releases also carry a cargo-public-api diff of the public Rust surface against the
previous release tag — these releases do not ship a changelog, and that diff is the machine-checkable
answer to what changed.

macOS: the aarch64-apple-darwin binaries are signed by cosign but are not Apple-codesigned or
notarised, so Gatekeeper quarantines them on download and reports the binary as damaged. That is a policy
decision by macOS, not a corrupt artifact — verify the cosign signature, then clear the quarantine flag:

xattr -d com.apple.quarantine ./<binary>

v0.1.0-beta.35

v0.1.0-beta.35 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 24 Sep 20:20

Release of mcpg-backend-llm-shared at v0.1.0-beta.35.
Issues are welcome; pull requests cannot be merged here — development happens upstream.

This crate is consumed by git reference — it is not published to crates.io:

[dependencies]
mcpg-backend-llm-shared = { git = "https://github.com/mcpg-dev/mcpg-backend-llm-shared", tag = "v0.1.0-beta.35" }

(binaries: cargo install --git https://github.com/mcpg-dev/mcpg-backend-llm-shared --tag v0.1.0-beta.35 mcpg-backend-llm-shared, or use the packed assets below)

Every asset is signed with cosign (keyless, Sigstore transparency log);
public releases also carry a SLSA build-provenance attestation. Verify one with:

gh attestation verify <file> --repo mcpg-dev/mcpg-backend-llm-shared

A resolved Cargo.lock and an SPDX SBOM are attached. Every lane built --locked against that exact
lockfile, so it describes these binaries rather than a later resolution — to rebuild this version
byte-for-byte, drop it in as Cargo.lock and build --locked.
Library and plugin releases also carry a cargo-public-api diff of the public Rust surface against the
previous release tag — these releases do not ship a changelog, and that diff is the machine-checkable
answer to what changed.

macOS: the aarch64-apple-darwin binaries are signed by cosign but are not Apple-codesigned or
notarised, so Gatekeeper quarantines them on download and reports the binary as damaged. That is a policy
decision by macOS, not a corrupt artifact — verify the cosign signature, then clear the quarantine flag:

xattr -d com.apple.quarantine ./<binary>

v0.1.0-beta.29

v0.1.0-beta.29 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 20 Sep 23:32

Release of mcpg-backend-llm-shared at v0.1.0-beta.29.
Issues are welcome; pull requests cannot be merged here — development happens upstream.

This crate is consumed by git reference — it is not published to crates.io:

[dependencies]
mcpg-backend-llm-shared = { git = "https://github.com/mcpg-dev/mcpg-backend-llm-shared", tag = "v0.1.0-beta.29" }

(binaries: cargo install --git https://github.com/mcpg-dev/mcpg-backend-llm-shared --tag v0.1.0-beta.29 mcpg-backend-llm-shared, or use the packed assets below)

Every asset is signed with cosign (keyless, Sigstore transparency log);
public releases also carry a SLSA build-provenance attestation. Verify one with:

gh attestation verify <file> --repo mcpg-dev/mcpg-backend-llm-shared

A resolved Cargo.lock and an SPDX SBOM are attached. Every lane built --locked against that exact
lockfile, so it describes these binaries rather than a later resolution — to rebuild this version
byte-for-byte, drop it in as Cargo.lock and build --locked.
Library and plugin releases also carry a cargo-public-api diff of the public Rust surface against the
previous release tag — these releases do not ship a changelog, and that diff is the machine-checkable
answer to what changed.

macOS: the aarch64-apple-darwin binaries are signed by cosign but are not Apple-codesigned or
notarised, so Gatekeeper quarantines them on download and reports the binary as damaged. That is a policy
decision by macOS, not a corrupt artifact — verify the cosign signature, then clear the quarantine flag:

xattr -d com.apple.quarantine ./<binary>