description: "The Radicle forge is an open source, peer-to-peer code collaboration stack built on Git."

fedi: "@radicle@toot.radicle.xyz"

node: "seed.radicle.xyz"

atproto: radicle.xyz

# jekyll-feed configuration

[git-v2]: https://git-scm.com/docs/protocol-v2

[Tor]: https://torproject.org/

[Ed25519]: https://ed25519.cr.yp.to/

[reverse-dns]: https://en.wikipedia.org/wiki/Reverse_domain_name_notation

[tuf]: https://theupdateframework.github.io/specification/latest/

[noise]: http://www.noiseprotocol.org/noise.html

### Adding support for HTTPS

For your HTTP Daemon to be accessible from a frontend such as

we recommend using [Caddy][caddy].

Start by installing `caddy`; most Linux distributions have a package you can

    curl https://seed.radicle.example/api/v1

You should now be able to visit your seed node via any Radicle web frontend as

> On some distributions, installing `caddy` will start the system service

> automatically. If you're not able to connect to your HTTP daemon from the

      <h1>{{ page.title }}</h1>

      <p class="subtitle">{{ page.subtitle }}</p>

      <span class="author">

	{% if author.atproto %}<a href="{{ author.atproto | prepend: "https://bsky.app/profile/" }}">🦋</a>{% endif %}

	{% if author.fedi %}<a href="{{ author.fedi | fedi_to_https }}">🐘</a>{% endif %}

	{% if author.web %}<a href="https://{{ author.web }}">🌐</a>{% endif %}

module Jekyll

  module Explorer

      else

      end

    end

  end

## What Radicle Desktop (currently) is not

## Why we’re excited 🎊

There are adapters for running CI locally on the host or in a

container, GitHub actions, Woodpecker, and several others. See [`CI

broker

and [integration

documentation](https://explorer.radicle.gr/nodes/seed.radicle.gr/rad:z4Uh671FzoooaHjLvmtW9BtGMF9qm)

for a more complete list. The adapter interface is intentionally easy

There you go. I now have a Radicle repository to play with. As of

publishing this blog post, the repository is alive on the Radicle

network, if you want to [look at

or clone it.

# CI configuration in the repository

run to finish on a server and then try to deduce from the run log what

went wrong. I've alleviated this by writing an extension to `rad` to

run CI locally:

It can produce a huge amount of output, so I've abbreviated that

below.

appreciate help with expanding that documentation.

It's probably easiest to install

from source code or with `cargo install`, but I have a `deb` package

for those using Debian or derivatives in my [APT

repository](http://apt.liw.fi/).

image: radicle-1.png

---

Spring has sprung, where we're writing from, and Daffodils are in season!

### Improved `rad/sigrefs`

The "Signed References" feature was reimplemented.

The commits in `refs/rad/sigrefs` will now only verify if they carry an appropriate value for `refs/rad/root` in the associated `refs` blob.

image: radicle-1.png

---

The Radicle team would like to announce the release of Radicle 1.7.1 ([`d9915d2`]).

After releasing [1.7.0]({% post_url 2026-03-18-radicle-1.7.0 %}), our users reported issues after upgrading.

### Signed References compatibility

In commit [`d3bc868e84c334f113806df1737f52cc57c5453d`] which was released in version 1.7.0, the criteria for verification of Signed References was changed to be more strict.

In particular, to require the reference `refs/rad/root` pointing at the root commit in the history of the repository identity.

[Collaborative Objects]: https://radicle.xyz/guides/protocol#collaborative-objects

[signed pushes]: https://people.kernel.org/monsieuricon/signed-git-pushes

[push certificates]: https://git-scm.com/docs/pack-protocol#_push_certificate

\ No newline at end of file

\ No newline at end of file

image: radicle-1.png

---

[Drosera]: https://en.wikipedia.org/wiki/Drosera

The Radicle team are back sooner than later for this important release, Radicle 1.8.0, code name *[Drosera]*.