release tags/versions

Closed { reason: Solved } did:key:z6MkkS9z...tY7R opened 2 years ago

I am currently creating AUR packages for radicle-cli, radicle-node and radicle-httpd.

Is there a way to link the binary releases on https://files.radicle.xyz/ to actual version (semver) tags?

z6MkkfM3...sVz5 commented 1 year ago

Hey tippfehlr, will mark this issue as solved, since we started to create tags for each release candidate and will continue to do so after the release candidate phase ends.

levitte commented 1 year ago

How are those tags propagating? I haven’t seen any in my pulls.

fintohaps commented 1 year ago

How are those tags propagating? I haven’t seen any in my pulls.

Currently, they’re only under cloudhead’s remote so you could add:

[remote "cloudhead"]
	url = rad://z3gqcJUoA1n9HaHKufZs5FCSGazv5/z6MksFqXN3Yhqk8pTJdUGLwATkRfQvwZXPqR2qMEhbS9wzpT
	fetch = +refs/heads/*:refs/remotes/cloudhead/*
    prune = true

and fetch with --tags.

We’re hoping to change this with a more general form of canonical references, which I’m proposing here https://app.radicle.xyz/nodes/seed.radicle.xyz/rad:z3trNYnLWS11cJWC6BbxDs5niGo82/patches/1d1ce874f7c39ecdcd8c318bbae46ffd02fe1ea8

z6MkkfM3...sVz5 commented 8 months ago

Hey @tippfehlr, so with the release of Radicle 1.3.0 the protocol now supports canonical references, which allow us to link the release commits to top level git tags. You can read more about them in our howto guide and or read the updates to 1.3.0