Radicle 1.3.0

Summary

Radicle is a peer-to-peer, local-first code collaboration stack built on Git. The Radicle team is delighted to announce the release of Radicle 1.3.0 (29043134a). This release contains 48 commits by 7 contributors. We would like to thank everyone for their continued effort in helping us improve the Radicle protocol and tooling via their contributions and usage reports 👾 Installation curl -sSf https://radicle.xyz/install | sh -s -- --no-modify-path --version=1.3.0 Canonical References This feature has been under way for quite some time, and we are proud to announce that it’s ready for you to use! Canonical reference rules have been introduced via an identity payload entry under the identifier xyz.radicle.crefs. Here’s an example of the payload that includes a single rule for tags that live under refs/tags/releases/*: "xyz.radicle.crefs": { "rules": { "refs/tags/releases/*": { "allow": [ "did:key:z6MkkPvBfjP4bQmco5Dm7UGsX2ruDBieEHi8n9DVJWX5sTEz", "did:key:z6MkgFq6z5fkF2hioLLSNu1zP2qEL1aHXHZzGH1FLFGAnBGz", "did:key:z6MkireRatUThvd3qzfKht1S44wpm4FEWSSa4PRMTSQZ3voM" ], "threshold": 2 } } } The canonical reference rules are now used to check for canonical updates. The rule for the defaultBranch of an xyz.radicle.project is synthesized from the identity document fields: threshold and delegates. This means that a rule for that reference is not allowed within the rule set. This is checked when performing a rad id update. For a more detailed history and usage of canonical references, check out the accompanying post. Introducing radicle-protocol This set of changes is mostly cosmetic for the time being. A new crate, radicle-protocol, was introduced to provide a home for a sans I/O implementation of the Radicle protocol. The crate currently defines the inner workings of the protocol, and radicle-node depends on this. Note here that we switched to use the bytes crate, and we witnessed a panic from this crate while using a pre-release. It has not showed up again, but we introduced...