Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Releases

Protocol-Canary
Current versionv0.1.1
DistributionA git tag (v0.1.1), installed via cargo install --git ... --tag v0.1.1 --locked.
GitHub Releasev0.1.1 is published (target commit 919668859bc1bef3d58737f13695b486d67632ea). It carries no prebuilt binary and no checksum artifact — installation still builds from source via the tag, exactly as before. If prebuilt binaries are ever added, this page and Installation will be updated to reflect it.
What changed in 0.1.1canary-xdr gained support for the "ContractExecutable" XDR type (previously only "StellarValue"), needed to test CAP-0085’s CONTRACT_EXECUTABLE_EXTERNAL_REF case.

ProtocolCanary-Action
Current releasev0.1.1 (a real GitHub Release, since this is a JavaScript/Node action whose bundled dist/index.js is committed and released)
Floating tagv1 — currently resolves to the same commit as the v0.1.1 release tag, per standard GitHub Actions convention for major-version tags.
Default version input0.1.1 (the Protocol-Canary release it installs and runs)

ProtocolCanary-Fixtures
Current packprotocol-28/ — Active
DistributionThe protocol-28/ pack is published as a tagged snapshot and GitHub Release — tag protocol-28, commit 75ec2c293a44f09d9c8c1f76722a24a2334ac20a — the immutable, verified Protocol 28 fixture pack. It is not a compiled or binary artifact: consumers still use a git checkout/clone (actions/checkout with repository: StellarCanary/ProtocolCanary-Fixtures, or a plain git clone, optionally at the protocol-28 tag/ref) and point --fixtures-dir at the resulting declarative TOML fixture corpus.
Other packsprotocol-27/ exists but is not yet populated — fixtures are added only after their upstream behavior is independently verified, never as placeholders.

Version compatibility

Protocol-CanaryFixture packTarget protocolProtocolCanary-Action
v0.1.1ProtocolCanary-Fixtures protocol-28/28v1 (default version: "0.1.1")

This is the only combination that has actually been run together and verified end-to-end (5/5 PASS against live Testnet). v0.1.0 is installable but predates ContractExecutable XDR support (needed by two current Protocol 28 fixtures) and the counts field in its JSON report — the Action tolerates the missing field, but v0.1.1 is the version this table verifies against.

Tags vs. releases vs. binaries — what actually exists

Git tagsGitHub ReleasesPrebuilt binaries
Protocol-CanaryYes (v0.1.0, v0.1.1)Yes (v0.1.1)No
ProtocolCanary-ActionYes (v0.1.1, v1)YesN/A (a JS action; its “binary” is the committed dist/index.js)
ProtocolCanary-FixturesYes (protocol-28)Yes (protocol-28)N/A (not a distributable binary)

Do not assume a Protocol-Canary binary download exists anywhere — every documented install path in Installation builds from source.