Skip to content

Releases

goat 0.7.2

Choose a tag to compare

@github-actions github-actions released this 16 Nov 06:16
goatcore/v0.7.2
e720562

goatcore/v0.7.2 is a release of the whole tree, and the commit stable points at.
Build on this tag, or on the stable branch, when you want a fixed reference.

Versions that go together

Each of these was released from commit e7205628370d or from an earlier commit that it contains.

Component Release
goatbuilder goatbuilder/v0.7.2
goat (the operator CLI) goat-cli-v0.5.19
goat-relay goat-relay/v0.1.0
snitch snitch-v0.1.1
grant-crypto SDK grant-crypto-sdk-v0.1.0

Works with

Other project Version Why
saltlick, the peering directory v0.5.0 or later goatbuilder federate publishes one directory package per partner. An older directory has one package per party; the goatbuilder release notes say what to set for it

goat 0.7.1

Choose a tag to compare

@github-actions github-actions released this 15 Nov 16:25
goatcore/v0.7.1
56d0f65

goatcore/v0.7.1 is a release of the whole tree, and the commit stable points at.
Build on this tag, or on the stable branch, when you want a fixed reference.

Versions that go together

Each of these was released from commit 56d0f6506dd7 or from an earlier commit that it contains.

Component Release
goatbuilder goatbuilder/v0.7.1
goat (the operator CLI) goat-cli-v0.5.19
goat-relay goat-relay/v0.1.0
snitch snitch-v0.1.1
grant-crypto SDK grant-crypto-sdk-v0.1.0

Works with

Other project Version Why
saltlick, the peering directory v0.5.0 or later goatbuilder federate publishes one directory package per partner. An older directory has one package per party; the goatbuilder release notes say what to set for it

goatbuilder/v0.7.2

Choose a tag to compare

@github-actions github-actions released this 15 Nov 20:52
goatbuilder/v0.7.2
e720562

goatbuilder, the build, release, deploy and standup tool for a goatnet.

New in 0.7.2. For someone deploying: goatbuilder federate rotate <partner> ipsec-leaf rotates an ipsec-fips peering's IPsec leaf. It runs phases 11 to 14 and passes the rotation to the edge role, goat-peering-edge, which checks the leaf an operator staged beside the live files, sets the live pair aside once, re-authenticates, and puts the old pair back if the IKE SA does not come up. rotate <partner> ipsec-ca also needs --partner-holds-ipsec-ca <sha256>, the partner's read-back of our new CA's fingerprint (GB-303). A stopped rotation resumes with the same id, and --retire <id> removes the set-aside key only once phase 14 has passed here (#763, #828). federate rotate <partner> ca is still refused with GB-282, and its message now says the CA rotation is decided (ADR 1242) but not built in this goatbuilder; rotate the leaves under the same CA with rotate <partner> leaves meanwhile (#894). A failed phase prints its fix once, on its Fix: line, and an INCOMPLETE phase 14 (X-ACCEPT-001) names goatbuilder federate <peering> --from 14 to resume it (#911). goatbuilder grow hands a goatlite over to the full preset: it shows the difference leaf by leaf, the files it writes and hands over and the renderer command, asks (or needs --yes), then writes ops/goatbuilder/goatbuilder.yaml, takes the generated header off the files the goatlite's render wrote, and removes goatlite.yaml. It changes the checkout only, never a host, and refuses with nothing changed on GB-304, GB-305 or GB-306; it is step 3 of the growth design and has not run on hardware (#804). One behaviour change: the role now sets make_before_break = yes on every IPsec peering edge, so the first apply after this release restarts strongSwan once on each ipsec-fips edge and drops that peering's link briefly: apply both sides of a peering in one window (#763). Known issue: in 0.7.2, goatbuilder federate rotate <partner> carrier does not complete a carrier rotation, and the partner's acceptance then fails; on a peering with no carrier it reports success and changes nothing. Do not rotate a carrier key with 0.7.2. The fix is #839, not yet released. For someone contributing: the compatibility check is held to goatbuilder/v0.7.1 (#886). To be removed: nothing new. goat federate <verb>, deprecated in 0.5.0, is removed from goat no earlier than 2026-12-11 and only after one peering between two standing environments has been completed with goatbuilder federate. The full list is in crates/goatbuilder/CHANGELOG.md.

New in 0.7.1. For someone deploying: join-node builds a node in the Linux VM of an Android phone with --class phone --via usb, built on a fixture and not yet measured on a phone (#747); runs a joining site's own mesh DNS, so a site cut off from its founder still resolves the goatnet's service names (#678); refuses a node whose clock is off before changing it (#766); and, like teardown, keeps a timings file as standup does (#802). standup for a joiner site turns signal federation on with join-node's own steps (#824), and every timings row names its cause, with phase 11 timed and the slowest phases named (#805, #814). Every site's end state declares every service a cut-off site needs, and what a joining site does not run yet is named as a gap with the gate row that closes it (#671). goatbuilder federate rotate <partner> leaves replaces a running peering's leaves, and a leaf rotation that was interrupted finishes or rolls back (#689). goatbuilder federate test <partner> --bilateral completes the partner's half of acceptance on a session both sides derive from the agreement, opt-in (#720); phase 14's round trip resends fresh probes until one is acknowledged (#808), and in a bilateral session, our own staging row no longer fails by construction (#789). On a two-driver peering the edge driver runs phase 1's edge checks and phase 3's edge half and prints the way back (#717, #736). Backing out one of two peerings keeps the core leaf the other still uses (#716), and a back-out removes the peering's entry from the edge's host firewall (#788). After a signing-key rotation, phase 5 hands the peering directory over to the new key (#683). A host-allocation SKIP says which case it is and what clears it, and federate plan --accept host-allocation records a judged SKIP in the plan (#753, #779). The C3 comparison (ops/goatbuilder/c3-agreement.py) exits 2 and names a verify report that read no machine (#809). Acceptance on a derived session ignores a partner sample left by an earlier run (#786). goatbuilder.yaml takes three optional fields, deploy.cloud, deploy.owner and deploy.cross_goatnet; undeclared, nothing changes (#765). Three behaviour changes: an environment that declares converger: pull-agent is refused by doctor and by every verb that pushes to real hosts, with GB-307, until the pull converger is built (#803); join-node refuses a node whose clock is unsynchronized or more than 250 ms off, with GB-297 (#766); and a back-out with no other peering set up, and no record of what the core leaf's paths held before, stops with GB-293 where it stopped with GB-221 (#716). For someone contributing: a deprecated command, flag or value warns on stderr, and a report's -o json document lists it; the list is empty today (#798, #818); CI holds ADR 1228's deprecation period and kept exit codes once the last release is 1.0 (#800, #813, #826); a changelog entry title written in quotes renders without them (#764); the compatibility check is held to goatbuilder/v0.7.0 (#776); join-node's peer-groups query is measured against NetBird's own schema (#754); before tagging, a diff between the checked commit and the merge commit decides whether a stage runs again (#772). To be removed: nothing new. goat federate <verb>, deprecated in 0.5.0, is removed from goat no earlier than 2026-12-11 and only after one peering between two standing environments has been completed with goatbuilder federate. The full list is in crates/goatbuilder/CHANGELOG.md.

New in 0.7.0. For someone deploying: every refusal now names its error code, and an undeclared peering exits 1, refused, where it exited 2 (#560, #656). A failed phase of federate, standup, join-node or deploy names the error in its output with its fix and the command that runs the phase again (#646, #652, #669, #703). A run records every value it uses and where each came from, in goatbuilder show and runs diff (#649). Every verb's phases are in the phase catalog, and goatbuilder explain <verb> <phase> answers for each (#651, #703). goatbuilder status reads real hosts (#648), and goatbuilder update verify-release checks a downloaded release without installing it (#655). join-node names what a joining site does not run, adds a node at a third site, has no manual phase after reaching the node, and deploys a joining site's data router, its leaves, the health publishers it declares and, with signal federation off, its front door (#612, #613, #661, #699, #715, #718, #721). A back-out stops on a probe that cannot tell, takes back what admission placed, drops a role core partner's store whole, and says why when it stops after its plan (#554, #629, #668). rollback --site reaches a goatnet through its door, as deploy does (#644), and an edge deployed from a workspace gets the certificates it mounts, or phase 12 says why (GB-275, #658). Phase 10 places and restarts nothing when its admission is already in place (#692), and its deploy no longer refuses an approved plan for an edge with the host firewall baseline on (GB-188, #740); phase 13 keeps a partner's newer SPIFFE bundle (#698), and on a peering declared drivers: two the controller imports phase 1's edge result and runs its core half; the edge driver's own run is not built yet (#690). Site bootstrap installs the hub-directive applier at Spock sites that name a hub (#596). Container memory limits and Postgres memory are settable, and the roles that schedule with cron install it (#615). For someone contributing: a changelog entry is a file of its own and a new ADR's index row is rendered from the ADR (#623, #636); the compatibility check holds more of the last release, now goatbuilder/v0.6.1 (#676); contract clause C11 is written (#647); rotating the forwarder carrier keys and the WireGuard peering key is built as a library and in the roles, not yet on the command line (#667, #680); CI runs on main to the end. To be removed: nothing new. goat federate <verb>, deprecated in 0.5.0, is removed from goat no earlier than 2026-12-11 and only after one peering between two standing environments has been completed with goatbuilder federate. The full list is in crates/goatbuilder/CHANGELOG.md.

New in 0.6.1. A patch release. For someone deploying: a goatbuilder federate run killed in phase 11, after it wrote the WireGuard link's files and before it restarted the link, now resumes and brings the link up; in 0.6.0 this was a known issue (#597). The Ory deploy reads the Postgres password itself and never recreates postgres-a (#593), and the audit-subscriber's lifecycle steps run with a writable HOME (#595). A peering can declare drivers: two; such a run stops at the first phase that needs the edge and prints what the edge driver runs (GB-265), and the parts not yet built are refused before acting (GB-267). federate <partner> --side edge alone is now refused with GB-267, and import is a reserved peering name (#601). For someone contributing: the federation test environment's required job runs as stages (#602). To be removed: nothing new. The full list is in crates/goatbuilder/CHANGELOG.md.

New in 0.6.0. The full list is in crates/goatbuilder/CHANGELOG.md.

For someone deploying: goatbuilder update verifies the release signature itself, with no cosign needed, and refu...

Read more

goatbuilder/v0.7.1

Choose a tag to compare

@github-actions github-actions released this 15 Nov 13:16
goatbuilder/v0.7.1
56d0f65

goatbuilder, the build, release, deploy and standup tool for a goatnet.

New in 0.7.1. For someone deploying: join-node builds a node in the Linux VM of an Android phone with --class phone --via usb, built on a fixture and not yet measured on a phone (#747); runs a joining site's own mesh DNS, so a site cut off from its founder still resolves the goatnet's service names (#678); refuses a node whose clock is off before changing it (#766); and, like teardown, keeps a timings file as standup does (#802). standup for a joiner site turns signal federation on with join-node's own steps (#824), and every timings row names its cause, with phase 11 timed and the slowest phases named (#805, #814). Every site's end state declares every service a cut-off site needs, and what a joining site does not run yet is named as a gap with the gate row that closes it (#671). goatbuilder federate rotate <partner> leaves replaces a running peering's leaves, and a leaf rotation that was interrupted finishes or rolls back (#689). goatbuilder federate test <partner> --bilateral completes the partner's half of acceptance on a session both sides derive from the agreement, opt-in (#720); phase 14's round trip resends fresh probes until one is acknowledged (#808), and in a bilateral session, our own staging row no longer fails by construction (#789). On a two-driver peering the edge driver runs phase 1's edge checks and phase 3's edge half and prints the way back (#717, #736). Backing out one of two peerings keeps the core leaf the other still uses (#716), and a back-out removes the peering's entry from the edge's host firewall (#788). After a signing-key rotation, phase 5 hands the peering directory over to the new key (#683). A host-allocation SKIP says which case it is and what clears it, and federate plan --accept host-allocation records a judged SKIP in the plan (#753, #779). The C3 comparison (ops/goatbuilder/c3-agreement.py) exits 2 and names a verify report that read no machine (#809). Acceptance on a derived session ignores a partner sample left by an earlier run (#786). goatbuilder.yaml takes three optional fields, deploy.cloud, deploy.owner and deploy.cross_goatnet; undeclared, nothing changes (#765). Three behaviour changes: an environment that declares converger: pull-agent is refused by doctor and by every verb that pushes to real hosts, with GB-307, until the pull converger is built (#803); join-node refuses a node whose clock is unsynchronized or more than 250 ms off, with GB-297 (#766); and a back-out with no other peering set up, and no record of what the core leaf's paths held before, stops with GB-293 where it stopped with GB-221 (#716). For someone contributing: a deprecated command, flag or value warns on stderr, and a report's -o json document lists it; the list is empty today (#798, #818); CI holds ADR 1228's deprecation period and kept exit codes once the last release is 1.0 (#800, #813, #826); a changelog entry title written in quotes renders without them (#764); the compatibility check is held to goatbuilder/v0.7.0 (#776); join-node's peer-groups query is measured against NetBird's own schema (#754); before tagging, a diff between the checked commit and the merge commit decides whether a stage runs again (#772). To be removed: nothing new. goat federate <verb>, deprecated in 0.5.0, is removed from goat no earlier than 2026-12-11 and only after one peering between two standing environments has been completed with goatbuilder federate. The full list is in crates/goatbuilder/CHANGELOG.md.

New in 0.7.0. For someone deploying: every refusal now names its error code, and an undeclared peering exits 1, refused, where it exited 2 (#560, #656). A failed phase of federate, standup, join-node or deploy names the error in its output with its fix and the command that runs the phase again (#646, #652, #669, #703). A run records every value it uses and where each came from, in goatbuilder show and runs diff (#649). Every verb's phases are in the phase catalog, and goatbuilder explain <verb> <phase> answers for each (#651, #703). goatbuilder status reads real hosts (#648), and goatbuilder update verify-release checks a downloaded release without installing it (#655). join-node names what a joining site does not run, adds a node at a third site, has no manual phase after reaching the node, and deploys a joining site's data router, its leaves, the health publishers it declares and, with signal federation off, its front door (#612, #613, #661, #699, #715, #718, #721). A back-out stops on a probe that cannot tell, takes back what admission placed, drops a role core partner's store whole, and says why when it stops after its plan (#554, #629, #668). rollback --site reaches a goatnet through its door, as deploy does (#644), and an edge deployed from a workspace gets the certificates it mounts, or phase 12 says why (GB-275, #658). Phase 10 places and restarts nothing when its admission is already in place (#692), and its deploy no longer refuses an approved plan for an edge with the host firewall baseline on (GB-188, #740); phase 13 keeps a partner's newer SPIFFE bundle (#698), and on a peering declared drivers: two the controller imports phase 1's edge result and runs its core half; the edge driver's own run is not built yet (#690). Site bootstrap installs the hub-directive applier at Spock sites that name a hub (#596). Container memory limits and Postgres memory are settable, and the roles that schedule with cron install it (#615). For someone contributing: a changelog entry is a file of its own and a new ADR's index row is rendered from the ADR (#623, #636); the compatibility check holds more of the last release, now goatbuilder/v0.6.1 (#676); contract clause C11 is written (#647); rotating the forwarder carrier keys and the WireGuard peering key is built as a library and in the roles, not yet on the command line (#667, #680); CI runs on main to the end. To be removed: nothing new. goat federate <verb>, deprecated in 0.5.0, is removed from goat no earlier than 2026-12-11 and only after one peering between two standing environments has been completed with goatbuilder federate. The full list is in crates/goatbuilder/CHANGELOG.md.

New in 0.6.1. A patch release. For someone deploying: a goatbuilder federate run killed in phase 11, after it wrote the WireGuard link's files and before it restarted the link, now resumes and brings the link up; in 0.6.0 this was a known issue (#597). The Ory deploy reads the Postgres password itself and never recreates postgres-a (#593), and the audit-subscriber's lifecycle steps run with a writable HOME (#595). A peering can declare drivers: two; such a run stops at the first phase that needs the edge and prints what the edge driver runs (GB-265), and the parts not yet built are refused before acting (GB-267). federate <partner> --side edge alone is now refused with GB-267, and import is a reserved peering name (#601). For someone contributing: the federation test environment's required job runs as stages (#602). To be removed: nothing new. The full list is in crates/goatbuilder/CHANGELOG.md.

New in 0.6.0. The full list is in crates/goatbuilder/CHANGELOG.md.

For someone deploying: goatbuilder update verifies the release signature itself, with no cosign needed, and refuses a release whose signature does not verify (GB-261). Every run that drives hosts keeps a record, read with goatbuilder runs, show and runs diff. Every process goatbuilder starts is named, with its phase, command, host and log, before it prints anything, and a dry run prints the commands the real run executes. Each of federate's fourteen phases is described in one catalog. goatbuilder explain federate <phase> answers from it. A failed federate phase carries the matching error code and its fix. Several peerings each keep their own directory package by default (a behaviour change; a directory older than saltlick v0.5.0 keeps one package, so move it before adding a second peering). Admission keeps every other variable in the core's peerings file and refuses one it cannot read as literal entries (GB-237). A back-out reads the core the way admission wrote it, stops on anything it cannot read, and leaves the core's org fragment byte for byte as it was before admission. A run journal written by a later goatbuilder is read, not refused. The edge's checks read only the configuration path the core router names and refuse a key storage wider than the key-bundle grant; each stops when it cannot tell (a behaviour change). Values reach standup's and deploy's commands as one word each, and every error's "read more" path is a document that ships with goatcore. The isitup status page's probe list can be refreshed on its own, and a list behind its declaration is detected. Nothing half built ships switched on: what is not in 0.6.0 is listed in the changelog.

For someone contributing: every pull request checks configuration, commands, documents and error codes against the last release (gate rows A2 to A5). ADR 1228 sets the deprecation period, and the library that prints the warning is built. The 1.0 gate gains group H (a node on a phone) and group I (a joined site that runs cut off). ADR 1231 adds a stable line: the branch stable follows each whole-tree release goatcore/vX.Y.Z, and all work lands on main. Outside pull requests carry the label community. The federation test environment proves one directory package per partner against saltlick v0.5.0.

To be removed: goat federate <verb>, in the goat client, as announced in 0.5.0, no earlier than 30 days after 0.5.0 and not before a peering between two standing environments has been completed with goatbuilder federate. Nothing in goatbuilder.

New in 0.5.3: the first published release since 0.5.1; 0.5.2 was tagged but its release did not r...

Read more

goat 0.7.0

Choose a tag to compare

@github-actions github-actions released this 14 Nov 21:42
goatcore/v0.7.0
9a35afb

goatcore/v0.7.0 is a release of the whole tree, and the commit stable points at.
Build on this tag, or on the stable branch, when you want a fixed reference.

Versions that go together

Each of these was released from commit 9a35afb5e8b1 or from an earlier commit that it contains.

Component Release
goatbuilder goatbuilder/v0.7.0
goat (the operator CLI) goat-cli-v0.5.19
goat-relay goat-relay/v0.1.0
snitch snitch-v0.1.1
grant-crypto SDK grant-crypto-sdk-v0.1.0

Works with

Other project Version Why
saltlick, the peering directory v0.5.0 or later goatbuilder federate publishes one directory package per partner. An older directory has one package per party; the goatbuilder release notes say what to set for it

goat 0.6.1

Choose a tag to compare

@github-actions github-actions released this 14 Nov 12:42
goatcore/v0.6.1
8f96b39

goatcore/v0.6.1 is a release of the whole tree, and the commit stable points at.
Build on this tag, or on the stable branch, when you want a fixed reference.

Versions that go together

Each of these was released from commit 8f96b39f5d4b or from an earlier commit that it contains.

Component Release
goatbuilder goatbuilder/v0.6.1
goat (the operator CLI) goat-cli-v0.5.19
goat-relay goat-relay/v0.1.0
snitch snitch-v0.1.1
grant-crypto SDK grant-crypto-sdk-v0.1.0

Works with

Other project Version Why
saltlick, the peering directory v0.5.0 or later goatbuilder federate publishes one directory package per partner. An older directory has one package per party; the goatbuilder release notes say what to set for it

goatbuilder/v0.7.0

Choose a tag to compare

@github-actions github-actions released this 14 Nov 20:21
goatbuilder/v0.7.0
9a35afb

goatbuilder, the build, release, deploy and standup tool for a goatnet.

New in 0.7.0. For someone deploying: every refusal now names its error code, and an undeclared peering exits 1, refused, where it exited 2 (#560, #656). A failed phase of federate, standup, join-node or deploy names the error in its output with its fix and the command that runs the phase again (#646, #652, #669, #703). A run records every value it uses and where each came from, in goatbuilder show and runs diff (#649). Every verb's phases are in the phase catalog, and goatbuilder explain <verb> <phase> answers for each (#651, #703). goatbuilder status reads real hosts (#648), and goatbuilder update verify-release checks a downloaded release without installing it (#655). join-node names what a joining site does not run, adds a node at a third site, has no manual phase after reaching the node, and deploys a joining site's data router, its leaves, the health publishers it declares and, with signal federation off, its front door (#612, #613, #661, #699, #715, #718, #721). A back-out stops on a probe that cannot tell, takes back what admission placed, drops a role core partner's store whole, and says why when it stops after its plan (#554, #629, #668). rollback --site reaches a goatnet through its door, as deploy does (#644), and an edge deployed from a workspace gets the certificates it mounts, or phase 12 says why (GB-275, #658). Phase 10 places and restarts nothing when its admission is already in place (#692), and its deploy no longer refuses an approved plan for an edge with the host firewall baseline on (GB-188, #740); phase 13 keeps a partner's newer SPIFFE bundle (#698), and on a peering declared drivers: two the controller imports phase 1's edge result and runs its core half; the edge driver's own run is not built yet (#690). Site bootstrap installs the hub-directive applier at Spock sites that name a hub (#596). Container memory limits and Postgres memory are settable, and the roles that schedule with cron install it (#615). For someone contributing: a changelog entry is a file of its own and a new ADR's index row is rendered from the ADR (#623, #636); the compatibility check holds more of the last release, now goatbuilder/v0.6.1 (#676); contract clause C11 is written (#647); rotating the forwarder carrier keys and the WireGuard peering key is built as a library and in the roles, not yet on the command line (#667, #680); CI runs on main to the end. To be removed: nothing new. goat federate <verb>, deprecated in 0.5.0, is removed from goat no earlier than 2026-12-11 and only after one peering between two standing environments has been completed with goatbuilder federate. The full list is in crates/goatbuilder/CHANGELOG.md.

New in 0.6.1. A patch release. For someone deploying: a goatbuilder federate run killed in phase 11, after it wrote the WireGuard link's files and before it restarted the link, now resumes and brings the link up; in 0.6.0 this was a known issue (#597). The Ory deploy reads the Postgres password itself and never recreates postgres-a (#593), and the audit-subscriber's lifecycle steps run with a writable HOME (#595). A peering can declare drivers: two; such a run stops at the first phase that needs the edge and prints what the edge driver runs (GB-265), and the parts not yet built are refused before acting (GB-267). federate <partner> --side edge alone is now refused with GB-267, and import is a reserved peering name (#601). For someone contributing: the federation test environment's required job runs as stages (#602). To be removed: nothing new. The full list is in crates/goatbuilder/CHANGELOG.md.

New in 0.6.0. The full list is in crates/goatbuilder/CHANGELOG.md.

For someone deploying: goatbuilder update verifies the release signature itself, with no cosign needed, and refuses a release whose signature does not verify (GB-261). Every run that drives hosts keeps a record, read with goatbuilder runs, show and runs diff. Every process goatbuilder starts is named, with its phase, command, host and log, before it prints anything, and a dry run prints the commands the real run executes. Each of federate's fourteen phases is described in one catalog. goatbuilder explain federate <phase> answers from it. A failed federate phase carries the matching error code and its fix. Several peerings each keep their own directory package by default (a behaviour change; a directory older than saltlick v0.5.0 keeps one package, so move it before adding a second peering). Admission keeps every other variable in the core's peerings file and refuses one it cannot read as literal entries (GB-237). A back-out reads the core the way admission wrote it, stops on anything it cannot read, and leaves the core's org fragment byte for byte as it was before admission. A run journal written by a later goatbuilder is read, not refused. The edge's checks read only the configuration path the core router names and refuse a key storage wider than the key-bundle grant; each stops when it cannot tell (a behaviour change). Values reach standup's and deploy's commands as one word each, and every error's "read more" path is a document that ships with goatcore. The isitup status page's probe list can be refreshed on its own, and a list behind its declaration is detected. Nothing half built ships switched on: what is not in 0.6.0 is listed in the changelog.

For someone contributing: every pull request checks configuration, commands, documents and error codes against the last release (gate rows A2 to A5). ADR 1228 sets the deprecation period, and the library that prints the warning is built. The 1.0 gate gains group H (a node on a phone) and group I (a joined site that runs cut off). ADR 1231 adds a stable line: the branch stable follows each whole-tree release goatcore/vX.Y.Z, and all work lands on main. Outside pull requests carry the label community. The federation test environment proves one directory package per partner against saltlick v0.5.0.

To be removed: goat federate <verb>, in the goat client, as announced in 0.5.0, no earlier than 30 days after 0.5.0 and not before a peering between two standing environments has been completed with goatbuilder federate. Nothing in goatbuilder.

New in 0.5.3: the first published release since 0.5.1; 0.5.2 was tagged but its release did not run. It carries everything listed for 0.5.2 below, plus: the release workflows grant the permission their shared workflow needs; the goatlite administrator's address and join-node's declared values reach their phases as one word each, and a bootstrap command missing its owner variable is refused; and verify reads a failed ledger read as unknown.

New in 0.5.2: the federation documents are corrected against the code, and GB-129 now says that a narrower offer: is refused only for a hand-written federation.toml. status reads the hosts themselves. Declared paths and profiles reach standup's phases as one word each. When the edge and the core are on separate hosts, the edge's ingress check now reads the core, and a check that cannot run stops phase 12 (a behaviour change). An interrupted phase 8 no longer leaves private keys in its staging directory. validate names GB-025 on every failing row, and release prints commits at a fixed 12 characters. CI no longer depends on the Ubuntu archive: when a runner cannot reach it, the jobs fail over to the project's own package cache.

New in 0.5.0 and 0.5.1: federation is in goatbuilder. (0.5.0 was tagged and not published; 0.5.1 is the same goatbuilder and the first published release that carries it.) You federate with a partner using goatbuilder alone. You make one decision (the partner, and the release sets it receives) and answer the run's prompts at phases 5, 6 and 10: the partner's key and CA fingerprint, the agreement digest, then the plan and what your core admits. The full list is in crates/goatbuilder/CHANGELOG.md.

  • goatbuilder federate <partner>: the whole procedure in one run. At a terminal it asks for the partner's key and CA fingerprint and for the agreement digest. It makes the plan and asks you to approve it, shows what our core will admit and asks again, then carries on through acceptance. A run that stops resumes where it stopped.

  • goatbuilder federate plan <partner>, deploy <partner>, test <partner>, status [<partner>] and backout <partner>: each stage on its own. backout --dry-run surveys what backing one peering out would remove.

  • goatbuilder federate allocate [<peering>]: allocates one peering's values and renders its inventory, both deployment halves and its federation.toml. It runs beside peerings that are still written by hand.

  • Admission on a core deployed by the goat-zenoh role: the role's own play, org fragment, router leaf and zenoh_sovereign_peerings. No restart command needs to be typed.

  • Values come from the declarations the deployment already has:

    • secrets.federation for the signing key and CA;
    • environments[].peering_directory for the directory and its CA;
    • the site inventory for the peering's machines.

    FED_* variables stay as overrides.

  • goatbuilder federate init|lint|compose|diff|verify|apply are the package verbs goat federate had, with the same flags and exit codes.

  • Deprecated: goat federate. It still works in 0.5.0 and tells you the goatbuilder command to run instead. It will be removed from goat 30 days after this release, and not before one peering between two standing environments has been completed with goatbuilder federate. After that, goat federate only answers with an error that names goatbuilder federate. The script ops/scripts/peering-standup.sh stays as it is: documented, not supported.

Assets. goatbuilder-linux-amd64, goatbuilder-linux-arm64 (both run on glibc 2.31 and later: Ubuntu 20...

Read more

goatbuilder/v0.6.1

Choose a tag to compare

@github-actions github-actions released this 14 Nov 11:33
goatbuilder/v0.6.1
8f96b39

goatbuilder, the build, release, deploy and standup tool for a goatnet.

New in 0.6.1. A patch release. For someone deploying: a goatbuilder federate run killed in phase 11, after it wrote the WireGuard link's files and before it restarted the link, now resumes and brings the link up; in 0.6.0 this was a known issue (#597). The Ory deploy reads the Postgres password itself and never recreates postgres-a (#593), and the audit-subscriber's lifecycle steps run with a writable HOME (#595). A peering can declare drivers: two; such a run stops at the first phase that needs the edge and prints what the edge driver runs (GB-265), and the parts not yet built are refused before acting (GB-267). federate <partner> --side edge alone is now refused with GB-267, and import is a reserved peering name (#601). For someone contributing: the federation test environment's required job runs as stages (#602). To be removed: nothing new. The full list is in crates/goatbuilder/CHANGELOG.md.

New in 0.6.0. The full list is in crates/goatbuilder/CHANGELOG.md.

For someone deploying: goatbuilder update verifies the release signature itself, with no cosign needed, and refuses a release whose signature does not verify (GB-261). Every run that drives hosts keeps a record, read with goatbuilder runs, show and runs diff. Every process goatbuilder starts is named, with its phase, command, host and log, before it prints anything, and a dry run prints the commands the real run executes. Each of federate's fourteen phases is described in one catalog. goatbuilder explain federate <phase> answers from it. A failed federate phase carries the matching error code and its fix. Several peerings each keep their own directory package by default (a behaviour change; a directory older than saltlick v0.5.0 keeps one package, so move it before adding a second peering). Admission keeps every other variable in the core's peerings file and refuses one it cannot read as literal entries (GB-237). A back-out reads the core the way admission wrote it, stops on anything it cannot read, and leaves the core's org fragment byte for byte as it was before admission. A run journal written by a later goatbuilder is read, not refused. The edge's checks read only the configuration path the core router names and refuse a key storage wider than the key-bundle grant; each stops when it cannot tell (a behaviour change). Values reach standup's and deploy's commands as one word each, and every error's "read more" path is a document that ships with goatcore. The isitup status page's probe list can be refreshed on its own, and a list behind its declaration is detected. Nothing half built ships switched on: what is not in 0.6.0 is listed in the changelog.

For someone contributing: every pull request checks configuration, commands, documents and error codes against the last release (gate rows A2 to A5). ADR 1228 sets the deprecation period, and the library that prints the warning is built. The 1.0 gate gains group H (a node on a phone) and group I (a joined site that runs cut off). ADR 1231 adds a stable line: the branch stable follows each whole-tree release goatcore/vX.Y.Z, and all work lands on main. Outside pull requests carry the label community. The federation test environment proves one directory package per partner against saltlick v0.5.0.

To be removed: goat federate <verb>, in the goat client, as announced in 0.5.0, no earlier than 30 days after 0.5.0 and not before a peering between two standing environments has been completed with goatbuilder federate. Nothing in goatbuilder.

New in 0.5.3: the first published release since 0.5.1; 0.5.2 was tagged but its release did not run. It carries everything listed for 0.5.2 below, plus: the release workflows grant the permission their shared workflow needs; the goatlite administrator's address and join-node's declared values reach their phases as one word each, and a bootstrap command missing its owner variable is refused; and verify reads a failed ledger read as unknown.

New in 0.5.2: the federation documents are corrected against the code, and GB-129 now says that a narrower offer: is refused only for a hand-written federation.toml. status reads the hosts themselves. Declared paths and profiles reach standup's phases as one word each. When the edge and the core are on separate hosts, the edge's ingress check now reads the core, and a check that cannot run stops phase 12 (a behaviour change). An interrupted phase 8 no longer leaves private keys in its staging directory. validate names GB-025 on every failing row, and release prints commits at a fixed 12 characters. CI no longer depends on the Ubuntu archive: when a runner cannot reach it, the jobs fail over to the project's own package cache.

New in 0.5.0 and 0.5.1: federation is in goatbuilder. (0.5.0 was tagged and not published; 0.5.1 is the same goatbuilder and the first published release that carries it.) You federate with a partner using goatbuilder alone. You make one decision (the partner, and the release sets it receives) and answer the run's prompts at phases 5, 6 and 10: the partner's key and CA fingerprint, the agreement digest, then the plan and what your core admits. The full list is in crates/goatbuilder/CHANGELOG.md.

  • goatbuilder federate <partner>: the whole procedure in one run. At a terminal it asks for the partner's key and CA fingerprint and for the agreement digest. It makes the plan and asks you to approve it, shows what our core will admit and asks again, then carries on through acceptance. A run that stops resumes where it stopped.

  • goatbuilder federate plan <partner>, deploy <partner>, test <partner>, status [<partner>] and backout <partner>: each stage on its own. backout --dry-run surveys what backing one peering out would remove.

  • goatbuilder federate allocate [<peering>]: allocates one peering's values and renders its inventory, both deployment halves and its federation.toml. It runs beside peerings that are still written by hand.

  • Admission on a core deployed by the goat-zenoh role: the role's own play, org fragment, router leaf and zenoh_sovereign_peerings. No restart command needs to be typed.

  • Values come from the declarations the deployment already has:

    • secrets.federation for the signing key and CA;
    • environments[].peering_directory for the directory and its CA;
    • the site inventory for the peering's machines.

    FED_* variables stay as overrides.

  • goatbuilder federate init|lint|compose|diff|verify|apply are the package verbs goat federate had, with the same flags and exit codes.

  • Deprecated: goat federate. It still works in 0.5.0 and tells you the goatbuilder command to run instead. It will be removed from goat 30 days after this release, and not before one peering between two standing environments has been completed with goatbuilder federate. After that, goat federate only answers with an error that names goatbuilder federate. The script ops/scripts/peering-standup.sh stays as it is: documented, not supported.

Assets. goatbuilder-linux-amd64, goatbuilder-linux-arm64 (both run on glibc 2.31 and later: Ubuntu 20.04, Debian 11 and later), goatbuilder-darwin-amd64 (Intel), goatbuilder-darwin-arm64 (Apple Silicon), each with a .sha256; goatbuilder-docs.tar.gz, the goatbuilder book built from this tag, with its .sha256; SHA256SUMS over all five; SHA256SUMS.cosign-bundle, a keyless cosign signature over SHA256SUMS made by this repository's release workflow.

Download, verify, install. Replace <tag> with this release's tag and <os>-<arch> with linux-amd64, linux-arm64, darwin-amd64 or darwin-arm64.

base=https://github.com/USAREUR-AF/goatcore/releases/download/<tag>
curl -fL --remote-name-all "$base/goatbuilder-<os>-<arch>" "$base/SHA256SUMS" "$base/SHA256SUMS.cosign-bundle"
cosign verify-blob --bundle SHA256SUMS.cosign-bundle \
  --certificate-identity-regexp '^https://github\.com/USAREUR-AF/goatcore/\.github/workflows/_release-binary\.yml@refs/tags/goatbuilder/v' \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com SHA256SUMS
sha256sum -c --ignore-missing SHA256SUMS        # on macOS: shasum -a 256 -c --ignore-missing SHA256SUMS
install -m 0755 goatbuilder-<os>-<arch> ~/.local/bin/goatbuilder
goatbuilder --version

The cosign step is optional and needs cosign; the checksum step is not.

macOS. The binary is ad-hoc signed and not notarized. A copy downloaded with a browser carries the quarantine attribute and macOS refuses to open it; clear it once after the checksum passes: xattr -d com.apple.quarantine ~/.local/bin/goatbuilder. A copy fetched with curl has no quarantine attribute.

Windows. No Windows build; run goatbuilder from Linux, macOS or WSL.

What's Changed

  • fix(audit-subscriber): the lifecycle steps run mc with a writable HOME by @dlf-dds in #595
  • docs(design): peer fault handling, one path for faults on peers we do not own (ADR 1232) by @dlf-dds in #594
  • fix(ory): deploy reads the Postgres password itself and never recreates the database by @dlf-dds in #593
  • docs(contributing): a fix shows its failure on main before its pull request opens by @dlf-dds in #588
  • docs(goatbuilder): 0.6.0's notes name the phase 11 resume gap and list #368 by @dlf-dds in #598
  • docs(island-mode): a pre-minted certificate batch fits the slot pool, with changes by @dlf-dds in #605
  • docs(goatbuilder): join-node builds the whole declared site, designed by @dlf-dds in https://github.com/USAREUR-AF/go...
Read more

goatbuilder/v0.6.0

Choose a tag to compare

@github-actions github-actions released this 13 Nov 17:34
goatbuilder/v0.6.0
1a77b72

goatbuilder, the build, release, deploy and standup tool for a goatnet.

Known issue in 0.6.0. A goatbuilder federate run killed in phase 11, after it wrote the WireGuard link's files and before it restarted the link, leaves the interface with no peer. Resuming with --from 11 then refuses phases 11 and 12 ("The interface does not hold what the agreement says"). To recover, restart the peering WireGuard unit on the edge host (the role's peering_wg_service), then resume with --from 11. A run that is not killed is not affected; 0.5.3 has the same gap. Fixed in the next release (#597).

New in 0.6.0. The full list is in crates/goatbuilder/CHANGELOG.md.

For someone deploying: goatbuilder update verifies the release signature itself, with no cosign needed, and refuses a release whose signature does not verify (GB-261). Every run that drives hosts keeps a record, read with goatbuilder runs, show and runs diff. Every process goatbuilder starts is named, with its phase, command, host and log, before it prints anything, and a dry run prints the commands the real run executes. Each of federate's fourteen phases is described in one catalog. goatbuilder explain federate <phase> answers from it. A failed federate phase carries the matching error code and its fix. Several peerings each keep their own directory package by default (a behaviour change; a directory older than saltlick v0.5.0 keeps one package, so move it before adding a second peering). Admission keeps every other variable in the core's peerings file and refuses one it cannot read as literal entries (GB-237). A back-out reads the core the way admission wrote it, stops on anything it cannot read, and leaves the core's org fragment byte for byte as it was before admission. A run journal written by a later goatbuilder is read, not refused. The edge's checks read only the configuration path the core router names and refuse a key storage wider than the key-bundle grant; each stops when it cannot tell (a behaviour change). Values reach standup's and deploy's commands as one word each, and every error's "read more" path is a document that ships with goatcore. The isitup status page's probe list can be refreshed on its own, and a list behind its declaration is detected. Nothing half built ships switched on: what is not in 0.6.0 is listed in the changelog.

For someone contributing: every pull request checks configuration, commands, documents and error codes against the last release (gate rows A2 to A5). ADR 1228 sets the deprecation period, and the library that prints the warning is built. The 1.0 gate gains group H (a node on a phone) and group I (a joined site that runs cut off). ADR 1231 adds a stable line: the branch stable follows each whole-tree release goatcore/vX.Y.Z, and all work lands on main. Outside pull requests carry the label community. The federation test environment proves one directory package per partner against saltlick v0.5.0.

To be removed: goat federate <verb>, in the goat client, as announced in 0.5.0, no earlier than 30 days after 0.5.0 and not before a peering between two standing environments has been completed with goatbuilder federate. Nothing in goatbuilder.

New in 0.5.3: the first published release since 0.5.1; 0.5.2 was tagged but its release did not run. It carries everything listed for 0.5.2 below, plus: the release workflows grant the permission their shared workflow needs; the goatlite administrator's address and join-node's declared values reach their phases as one word each, and a bootstrap command missing its owner variable is refused; and verify reads a failed ledger read as unknown.

New in 0.5.2: the federation documents are corrected against the code, and GB-129 now says that a narrower offer: is refused only for a hand-written federation.toml. status reads the hosts themselves. Declared paths and profiles reach standup's phases as one word each. When the edge and the core are on separate hosts, the edge's ingress check now reads the core, and a check that cannot run stops phase 12 (a behaviour change). An interrupted phase 8 no longer leaves private keys in its staging directory. validate names GB-025 on every failing row, and release prints commits at a fixed 12 characters. CI no longer depends on the Ubuntu archive: when a runner cannot reach it, the jobs fail over to the project's own package cache.

New in 0.5.0 and 0.5.1: federation is in goatbuilder. (0.5.0 was tagged and not published; 0.5.1 is the same goatbuilder and the first published release that carries it.) You federate with a partner using goatbuilder alone. You make one decision (the partner, and the release sets it receives) and answer the run's prompts at phases 5, 6 and 10: the partner's key and CA fingerprint, the agreement digest, then the plan and what your core admits. The full list is in crates/goatbuilder/CHANGELOG.md.

  • goatbuilder federate <partner>: the whole procedure in one run. At a terminal it asks for the partner's key and CA fingerprint and for the agreement digest. It makes the plan and asks you to approve it, shows what our core will admit and asks again, then carries on through acceptance. A run that stops resumes where it stopped.

  • goatbuilder federate plan <partner>, deploy <partner>, test <partner>, status [<partner>] and backout <partner>: each stage on its own. backout --dry-run surveys what backing one peering out would remove.

  • goatbuilder federate allocate [<peering>]: allocates one peering's values and renders its inventory, both deployment halves and its federation.toml. It runs beside peerings that are still written by hand.

  • Admission on a core deployed by the goat-zenoh role: the role's own play, org fragment, router leaf and zenoh_sovereign_peerings. No restart command needs to be typed.

  • Values come from the declarations the deployment already has:

    • secrets.federation for the signing key and CA;
    • environments[].peering_directory for the directory and its CA;
    • the site inventory for the peering's machines.

    FED_* variables stay as overrides.

  • goatbuilder federate init|lint|compose|diff|verify|apply are the package verbs goat federate had, with the same flags and exit codes.

  • Deprecated: goat federate. It still works in 0.5.0 and tells you the goatbuilder command to run instead. It will be removed from goat 30 days after this release, and not before one peering between two standing environments has been completed with goatbuilder federate. After that, goat federate only answers with an error that names goatbuilder federate. The script ops/scripts/peering-standup.sh stays as it is: documented, not supported.

Assets. goatbuilder-linux-amd64, goatbuilder-linux-arm64 (both run on glibc 2.31 and later: Ubuntu 20.04, Debian 11 and later), goatbuilder-darwin-amd64 (Intel), goatbuilder-darwin-arm64 (Apple Silicon), each with a .sha256; goatbuilder-docs.tar.gz, the goatbuilder book built from this tag, with its .sha256; SHA256SUMS over all five; SHA256SUMS.cosign-bundle, a keyless cosign signature over SHA256SUMS made by this repository's release workflow.

Download, verify, install. Replace <tag> with this release's tag and <os>-<arch> with linux-amd64, linux-arm64, darwin-amd64 or darwin-arm64.

base=https://github.com/USAREUR-AF/goatcore/releases/download/<tag>
curl -fL --remote-name-all "$base/goatbuilder-<os>-<arch>" "$base/SHA256SUMS" "$base/SHA256SUMS.cosign-bundle"
cosign verify-blob --bundle SHA256SUMS.cosign-bundle \
  --certificate-identity-regexp '^https://github\.com/USAREUR-AF/goatcore/\.github/workflows/_release-binary\.yml@refs/tags/goatbuilder/v' \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com SHA256SUMS
sha256sum -c --ignore-missing SHA256SUMS        # on macOS: shasum -a 256 -c --ignore-missing SHA256SUMS
install -m 0755 goatbuilder-<os>-<arch> ~/.local/bin/goatbuilder
goatbuilder --version

The cosign step is optional and needs cosign; the checksum step is not.

macOS. The binary is ad-hoc signed and not notarized. A copy downloaded with a browser carries the quarantine attribute and macOS refuses to open it; clear it once after the checksum passes: xattr -d com.apple.quarantine ~/.local/bin/goatbuilder. A copy fetched with curl has no quarantine attribute.

Windows. No Windows build; run goatbuilder from Linux, macOS or WSL.

What's Changed

  • fix(federation): back out through the admission's inventories and refuse an empty survey by @dlf-dds in #459
  • test(federation-e2e): backing a peering out leaves both hosts as they were before it by @dlf-dds in #452
  • docs(goatbuilder): gate row B3 names the leaf rotation built as a library by @dlf-dds in #513
  • docs(adr): 1229 a partner's new package under the same key is confirmed within confirmation 1 by @dlf-dds in #512
  • test(federation-e2e): a flow monitor that measures whether data keeps arriving while a step runs by @dlf-dds in #492
  • test(goatbuilder): update moves a 0.5.1 install to this build and back (gate E3) by @dlf-dds in #510
  • fix(federation): refuse admission when the sovereign peerings are not literal by @dlf-dds in #476
  • ci(workflows): refuse a called workflow that asks for a permission its caller does not grant by @dlf-dds in #505
  • docs(goatbuilder): gate row E4, a serving surface verifies a release's signature before it serves it by @dlf-dds in #517
  • docs(goatbuilder): E4...
Read more

goatbuilder/v0.5.3

Choose a tag to compare

@github-actions github-actions released this 12 Nov 23:09
goatbuilder/v0.5.3
19bdae8

goatbuilder, the build, release, deploy and standup tool for a goatnet.

New in 0.5.3: the first published release since 0.5.1; 0.5.2 was tagged but its release did not run. It carries everything listed for 0.5.2 below, plus: the release workflows grant the permission their shared workflow needs; the goatlite administrator's address and join-node's declared values reach their phases as one word each, and a bootstrap command missing its owner variable is refused; and verify reads a failed ledger read as unknown.

New in 0.5.2: the federation documents are corrected against the code, and GB-129 now says that a narrower offer: is refused only for a hand-written federation.toml. status reads the hosts themselves. Declared paths and profiles reach standup's phases as one word each. When the edge and the core are on separate hosts, the edge's ingress check now reads the core, and a check that cannot run stops phase 12 (a behaviour change). An interrupted phase 8 no longer leaves private keys in its staging directory. validate names GB-025 on every failing row, and release prints commits at a fixed 12 characters. CI no longer depends on the Ubuntu archive: when a runner cannot reach it, the jobs fail over to the project's own package cache.

New in 0.5.0 and 0.5.1: federation is in goatbuilder. (0.5.0 was tagged and not published; 0.5.1 is the same goatbuilder and the first published release that carries it.) You federate with a partner using goatbuilder alone. You make one decision (the partner, and the release sets it receives) and answer the run's prompts at phases 5, 6 and 10: the partner's key and CA fingerprint, the agreement digest, then the plan and what your core admits. The full list is in crates/goatbuilder/CHANGELOG.md.

  • goatbuilder federate <partner>: the whole procedure in one run. At a terminal it asks for the partner's key and CA fingerprint and for the agreement digest. It makes the plan and asks you to approve it, shows what our core will admit and asks again, then carries on through acceptance. A run that stops resumes where it stopped.

  • goatbuilder federate plan <partner>, deploy <partner>, test <partner>, status [<partner>] and backout <partner>: each stage on its own. backout --dry-run surveys what backing one peering out would remove.

  • goatbuilder federate allocate [<peering>]: allocates one peering's values and renders its inventory, both deployment halves and its federation.toml. It runs beside peerings that are still written by hand.

  • Admission on a core deployed by the goat-zenoh role: the role's own play, org fragment, router leaf and zenoh_sovereign_peerings. No restart command needs to be typed.

  • Values come from the declarations the deployment already has:

    • secrets.federation for the signing key and CA;
    • environments[].peering_directory for the directory and its CA;
    • the site inventory for the peering's machines.

    FED_* variables stay as overrides.

  • goatbuilder federate init|lint|compose|diff|verify|apply are the package verbs goat federate had, with the same flags and exit codes.

  • Deprecated: goat federate. It still works in 0.5.0 and tells you the goatbuilder command to run instead. It will be removed from goat 30 days after this release, and not before one peering between two standing environments has been completed with goatbuilder federate. After that, goat federate only answers with an error that names goatbuilder federate. The script ops/scripts/peering-standup.sh stays as it is: documented, not supported.

Assets. goatbuilder-linux-amd64, goatbuilder-linux-arm64 (both run on glibc 2.31 and later: Ubuntu 20.04, Debian 11 and later), goatbuilder-darwin-amd64 (Intel), goatbuilder-darwin-arm64 (Apple Silicon), each with a .sha256; goatbuilder-docs.tar.gz, the goatbuilder book built from this tag, with its .sha256; SHA256SUMS over all five; SHA256SUMS.cosign-bundle, a keyless cosign signature over SHA256SUMS made by this repository's release workflow.

Download, verify, install. Replace <tag> with this release's tag and <os>-<arch> with linux-amd64, linux-arm64, darwin-amd64 or darwin-arm64.

base=https://github.com/USAREUR-AF/goatcore/releases/download/<tag>
curl -fL --remote-name-all "$base/goatbuilder-<os>-<arch>" "$base/SHA256SUMS" "$base/SHA256SUMS.cosign-bundle"
cosign verify-blob --bundle SHA256SUMS.cosign-bundle \
  --certificate-identity-regexp '^https://github.com/USAREUR-AF/goatcore/' \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com SHA256SUMS
sha256sum -c --ignore-missing SHA256SUMS        # on macOS: shasum -a 256 -c --ignore-missing SHA256SUMS
install -m 0755 goatbuilder-<os>-<arch> ~/.local/bin/goatbuilder
goatbuilder --version

The cosign step is optional and needs cosign; the checksum step is not.

macOS. The binary is ad-hoc signed and not notarized. A copy downloaded with a browser carries the quarantine attribute and macOS refuses to open it; clear it once after the checksum passes: xattr -d com.apple.quarantine ~/.local/bin/goatbuilder. A copy fetched with curl has no quarantine attribute.

Windows. No Windows build; run goatbuilder from Linux, macOS or WSL.

What's Changed

  • docs(ci): a check's result follows its inputs by @dlf-dds in #412
  • fix(ci): expose fixture build errors and bound apt retries by @joshkor1982 in #425
  • fix(goat-zenoh): an expired issuer does not count as a dropped trust anchor by @joshkor1982 in #413
  • fix(audit-fifo-evict): fail loudly when over high-water with eviction disabled by @joshkor1982 in #414
  • fix(obs): make webhook-noop a true null receiver by @joshkor1982 in #420
  • feat(obs): scrape alertmanager and alert on failing notifications by @joshkor1982 in #421
  • fix(obs): deliver large ntfy alert groups as one bounded notification by @joshkor1982 in #419
  • fix(terraform): describe egress rules in host modules by @HaterAndrew in #334
  • docs(design): federated reach is what the sender forwarded, not an alliance-wide default by @dlf-dds in #367
  • docs(adr): 0112 browser-UI row follows engineering-baseline 12.4 by @dlf-dds in #439
  • fix(deploy): per-site health roll-ups skip a paired site's passive node by @dlf-dds in #440
  • perf(portal): parse the data roster once per change, not once per request by @0mlml in #76
  • fix(deploy): the single-home guard file stays identical to goatstuff's copy by @dlf-dds in #445
  • ci(apt): fail over to our own package cache when Ubuntu's mirror does not answer by @dlf-dds in #426
  • docs(federation): correct ten statements the 0.5.1 documents get wrong about the command by @dlf-dds in #427
  • docs(goatbuilder): the options for 1.0 and the pull converger by @dlf-dds in #451
  • ci(python-and-ansible): bound the Galaxy download and name the dependency that failed by @dlf-dds in #453
  • test(goatbuilder): a deployment made with 0.4.3 or 0.5.1 continues on this build (gate E1) by @dlf-dds in #454
  • docs(adr): 1228 proposes the 1.0 compatibility and deprecation rules, period left open by @dlf-dds in #457
  • test(federation-e2e): an offer narrower than the release sets, carried out for one partner by @dlf-dds in #455
  • fix(federation): remove key material an interrupted leaf mint left behind by @dlf-dds in #458
  • fix(panoscope-core): return the namespace test as an expression, for clippy 1.100 by @dlf-dds in #465
  • test(goatbuilder): pin goatlite's first-run budget so growth adds nothing to it by @dlf-dds in #480
  • fix(goatbuilder): a validate refusal names GB-025 on every failing row by @dlf-dds in #479
  • fix(goatbuilder): pass declared paths and profiles to the phases without shell interpolation by @dlf-dds in #478
  • feat(goatbuilder): status reads real hosts the way diff reads and verify grades by @dlf-dds in #474
  • test(goatbuilder): add the C11 legibility conformance test, failing, with its known-failing list by @dlf-dds in #473
  • docs(goatlite): design growth from a goatlite into a full environment without a tear-down by @dlf-dds in #468
  • docs(goatbuilder): what the hardware clock measures and what a timed run records (gate C1, C2) by @dlf-dds in #467
  • docs(federation): the options for a partner's stored data when a peering is backed out by @dlf-dds in #466
  • docs(federation): how to measure one peering between two standing goatnets by @dlf-dds in #463
  • docs(federation): the contract for federating from two drivers by @dlf-dds in #462
  • test(goatbuilder): a peering 0.5.1 took to phase 10 is finished by this bu...
Read more