diff --git a/_posts/2025-08-12-canonical-references.md b/_posts/2025-08-12-canonical-references.md index 81d68a6..c5d6aa2 100644 --- a/_posts/2025-08-12-canonical-references.md +++ b/_posts/2025-08-12-canonical-references.md @@ -23,7 +23,7 @@ Radicle repositories to also act like more traditional Git repositories that have the typical references `refs/heads/main`, `refs/tags/v1.0.0`, `refs/heads/qa/feature-1`. So we introduced a way to synthesise these references from the references under the set of `refs/namespaces//refs`. These -references become canon[^4] and can be considered for use, e.g. fetching a +references become canon[^1] and can be considered for use, e.g. fetching a specific tag object for building binaries. ## Git History in the Making @@ -47,7 +47,7 @@ ourselves, "Can the `defaultBranch` approach be generalised?" This way, the "It should be easy!", I said – famous last words. -What ensued was a RIP[^0] and two patches[^1][^2], over a time period that felt +What ensued was a RIP[^2] and two patches[^3][^4], over a time period that felt like forever. It turned out that evolving things in a protocol can be quite tricky when it comes to compatibility. You may notice that the merged patch and the RIP will differ slightly in the approach recommended. For now, the approach @@ -62,7 +62,7 @@ As alluded to above, we need three values to specify a rule for a canonical reference. We need a reference the rule applies to, a set of allowed DIDs (currently always `did:key`s), and a `threshold`. These three values form a canonical reference rule. In fact, we can generalise the reference value to use -a Git reference pattern[^3]. +a Git reference pattern[^5]. So, where do these new rules go? The new update of Radicle will now interpret a new payload identified by the key `xyz.radicle.crefs`. Under this key, it @@ -184,12 +184,12 @@ now take advantage of Radicle repositories! Now, it's time to go try out this feature and report back to us! Release tags to your hearts content ❤️🌱 -[^0]: RIP-4 Canonical References https://app.radicle.xyz/nodes/seed.radicle.xyz/rad:z3trNYnLWS11cJWC6BbxDs5niGo82/patches/1d1ce874f7c39ecdcd8c318bbae46ffd02fe1ea8?tab=changes +[^1]: Here we are using the term in the sense that some content made may not be considered part of the canon of some story or universe. For example, some Star Wars content may be considered as canon by George Lucas, but some may not be. -[^1]: First patch attempting to implement canonical references https://app.radicle.xyz/nodes/seed.radicle.xyz/rad:z3gqcJUoA1n9HaHKufZs5FCSGazv5/patches/c54883e5ffb1f8a99f432e3ac79c0b728cd0dab3 +[^2]: [RIP-4 Canonical References](https://app.radicle.xyz/nodes/seed.radicle.xyz/rad:z3trNYnLWS11cJWC6BbxDs5niGo82/patches/1d1ce874f7c39ecdcd8c318bbae46ffd02fe1ea8?tab=changes) -[^2]: Second patch implementing canonical references using the identity payload https://app.radicle.xyz/nodes/seed.radicle.xyz/rad:z3gqcJUoA1n9HaHKufZs5FCSGazv5/patches/bea09df15505cfcebc72ad40f629747d2e82f670 +[^3]: [First patch attempting to implement canonical references](https://app.radicle.xyz/nodes/seed.radicle.xyz/rad:z3gqcJUoA1n9HaHKufZs5FCSGazv5/patches/c54883e5ffb1f8a99f432e3ac79c0b728cd0dab3) -[^3]: Git ref format and reference patterns https://git-scm.com/docs/git-check-ref-format +[^4]: [Second patch implementing canonical references using the identity payload](https://app.radicle.xyz/nodes/seed.radicle.xyz/rad:z3gqcJUoA1n9HaHKufZs5FCSGazv5/patches/bea09df15505cfcebc72ad40f629747d2e82f670) -[^4]: Here we are using the term in the sense that some content made may not be considered part of the canon of some story or universe. For example, some Star Wars content may be considered as canon by George Lucas, but some may not be. +[^5]: [Git ref format and reference patterns](https://git-scm.com/docs/git-check-ref-format) diff --git a/_posts/2025-08-12-radicle-1.3.0.md b/_posts/2025-08-12-radicle-1.3.0.md index 9ce0cea..9a2e534 100644 --- a/_posts/2025-08-12-radicle-1.3.0.md +++ b/_posts/2025-08-12-radicle-1.3.0.md @@ -51,7 +51,7 @@ accompanying [post](/2025/08/12/canonical-references.html). ## 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-IO[sans-io] +`radicle-protocol`, was introduced to provide a home for a [sans I/O][sans-io] implementation of the Radicle protocol. The crate currently defines the inner workings of the protocol, and `radicle-node` depends on this. @@ -67,7 +67,7 @@ on Windows. The first step was taken for this, and you can now use the `rad` CLI on a Windows machine – without WSL. Currently, `git-remote-rad` and `radicle-node` are blockers for full Windows -support. However, the sans-IO approach mentioned above will provide a way +support. However, the sans I/O approach mentioned above will provide a way forward for implementing a `radicle-node` that works on Windows, and we will continue to look into other fixes required for getting full Windows support. @@ -173,5 +173,6 @@ f09b4203a47611e1e6a78ea9087b5cae2f94cacc649ed195840a0869d821c861 radicle-1.3.0- a25c67276a86c9fbadadbacbd2ea9763202e99701aa85cf7fe5815662696988d radicle-1.3.0-x86_64-unknown-linux-musl.tar.xz 3a615bb99bc998b3fca5ad8582599c8dfb3cffb0beec291f5939d4b559270227 radicle-1.3.0-aarch64-unknown-linux-musl.tar.xz 7939e1d1bce232730843d8975f205558b0885479c6666b630abb1500b67756db radicle-1.3.0-aarch64-apple-darwin.tar.xz +``` [sans-io]: https://sans-io.readthedocs.io diff --git a/index.md b/index.md index 95fe871..a6ffe3a 100644 --- a/index.md +++ b/index.md @@ -116,7 +116,6 @@ updated, join our community on 💬 [Zulip][zulip], or