v0.1.0-alpha.47

Release of mcpg-plugin-backend-http at v0.1.0-alpha.47.
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-plugin-backend-http = { git = "https://github.com/mcpg-dev/mcpg-plugin-backend-http", tag = "v0.1.0-alpha.47" }

(binaries: cargo install --git https://github.com/mcpg-dev/mcpg-plugin-backend-http --tag v0.1.0-alpha.47 mcpg-plugin-backend-http, 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-plugin-backend-http

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-alpha.46

Release of mcpg-plugin-backend-http at v0.1.0-alpha.46.
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-plugin-backend-http = { git = "https://github.com/mcpg-dev/mcpg-plugin-backend-http", tag = "v0.1.0-alpha.46" }

(binaries: cargo install --git https://github.com/mcpg-dev/mcpg-plugin-backend-http --tag v0.1.0-alpha.46 mcpg-plugin-backend-http, 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-plugin-backend-http

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-alpha.45

Release of mcpg-plugin-backend-http at v0.1.0-alpha.45.
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-plugin-backend-http = { git = "https://github.com/mcpg-dev/mcpg-plugin-backend-http", tag = "v0.1.0-alpha.45" }

(binaries: cargo install --git https://github.com/mcpg-dev/mcpg-plugin-backend-http --tag v0.1.0-alpha.45 mcpg-plugin-backend-http, 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-plugin-backend-http

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-alpha.44

Release of mcpg-plugin-backend-http at v0.1.0-alpha.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-plugin-backend-http = { git = "https://github.com/mcpg-dev/mcpg-plugin-backend-http", tag = "v0.1.0-alpha.44" }

(binaries: cargo install --git https://github.com/mcpg-dev/mcpg-plugin-backend-http --tag v0.1.0-alpha.44 mcpg-plugin-backend-http, 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-plugin-backend-http

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-alpha.43

Release of mcpg-plugin-backend-http at v0.1.0-alpha.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-plugin-backend-http = { git = "https://github.com/mcpg-dev/mcpg-plugin-backend-http", tag = "v0.1.0-alpha.43" }

(binaries: cargo install --git https://github.com/mcpg-dev/mcpg-plugin-backend-http --tag v0.1.0-alpha.43 mcpg-plugin-backend-http, 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-plugin-backend-http

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-alpha.41

Release of mcpg-plugin-backend-http at v0.1.0-alpha.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-plugin-backend-http = { git = "https://github.com/mcpg-dev/mcpg-plugin-backend-http", tag = "v0.1.0-alpha.41" }

(binaries: cargo install --git https://github.com/mcpg-dev/mcpg-plugin-backend-http --tag v0.1.0-alpha.41 mcpg-plugin-backend-http, 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-plugin-backend-http

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-alpha.40

Release of mcpg-plugin-backend-http at v0.1.0-alpha.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-plugin-backend-http = { git = "https://github.com/mcpg-dev/mcpg-plugin-backend-http", tag = "v0.1.0-alpha.40" }

(binaries: cargo install --git https://github.com/mcpg-dev/mcpg-plugin-backend-http --tag v0.1.0-alpha.40 mcpg-plugin-backend-http, 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-plugin-backend-http

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-alpha.39

Release of mcpg-plugin-backend-http at v0.1.0-alpha.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-plugin-backend-http = { git = "https://github.com/mcpg-dev/mcpg-plugin-backend-http", tag = "v0.1.0-alpha.39" }

(binaries: cargo install --git https://github.com/mcpg-dev/mcpg-plugin-backend-http --tag v0.1.0-alpha.39 mcpg-plugin-backend-http, 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-plugin-backend-http

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-alpha.33

Release of mcpg-plugin-backend-http at v0.1.0-alpha.33.
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-plugin-backend-http = { git = "https://github.com/mcpg-dev/mcpg-plugin-backend-http", tag = "v0.1.0-alpha.33" }

(binaries: cargo install --git https://github.com/mcpg-dev/mcpg-plugin-backend-http --tag v0.1.0-alpha.33 mcpg-plugin-backend-http, 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-plugin-backend-http

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-alpha.32

Release of mcpg-plugin-backend-http at v0.1.0-alpha.32.
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-plugin-backend-http = { git = "https://github.com/mcpg-dev/mcpg-plugin-backend-http", tag = "v0.1.0-alpha.32" }

(binaries: cargo install --git https://github.com/mcpg-dev/mcpg-plugin-backend-http --tag v0.1.0-alpha.32 mcpg-plugin-backend-http, 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-plugin-backend-http

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>