v0.1.0-beta.52

Release of mcpg-cloud at v0.1.0-beta.52.
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-cloud = { git = "https://github.com/mcpg-dev/mcpg-cloud", tag = "v0.1.0-beta.52" }

(binaries: cargo install --git https://github.com/mcpg-dev/mcpg-cloud --tag v0.1.0-beta.52 mcpg-cloud, 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-cloud

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.51

Release of mcpg-cloud at v0.1.0-beta.51.
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-cloud = { git = "https://github.com/mcpg-dev/mcpg-cloud", tag = "v0.1.0-beta.51" }

(binaries: cargo install --git https://github.com/mcpg-dev/mcpg-cloud --tag v0.1.0-beta.51 mcpg-cloud, 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-cloud

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.50

Release of mcpg-cloud at v0.1.0-beta.50.
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-cloud = { git = "https://github.com/mcpg-dev/mcpg-cloud", tag = "v0.1.0-beta.50" }

(binaries: cargo install --git https://github.com/mcpg-dev/mcpg-cloud --tag v0.1.0-beta.50 mcpg-cloud, 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-cloud

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.49

Release of mcpg-cloud at v0.1.0-beta.49.
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-cloud = { git = "https://github.com/mcpg-dev/mcpg-cloud", tag = "v0.1.0-beta.49" }

(binaries: cargo install --git https://github.com/mcpg-dev/mcpg-cloud --tag v0.1.0-beta.49 mcpg-cloud, 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-cloud

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.48

Release of mcpg-cloud at v0.1.0-beta.48.
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-cloud = { git = "https://github.com/mcpg-dev/mcpg-cloud", tag = "v0.1.0-beta.48" }

(binaries: cargo install --git https://github.com/mcpg-dev/mcpg-cloud --tag v0.1.0-beta.48 mcpg-cloud, 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-cloud

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.47

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

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

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

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

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

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

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

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

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

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

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

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

Release of mcpg-cloud 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-cloud = { git = "https://github.com/mcpg-dev/mcpg-cloud", tag = "v0.1.0-beta.42" }

(binaries: cargo install --git https://github.com/mcpg-dev/mcpg-cloud --tag v0.1.0-beta.42 mcpg-cloud, 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-cloud

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>