fadd614 httpd: Release 0.22.0 — radicle-explorer

rad:z4V1sjrXqjvFdnCUbxPFqd5p4DtH5

Radicle web interface

httpd: Release 0.22.0

Rūdolfs Ošiņš committed 3 months ago

commit fadd61463660187bb4bbd88ba6864e6d62113b0b
parent 699835d

3 files changed +6 -4

modified radicle-httpd/Cargo.lock

@@ -2086,7 +2086,7 @@ dependencies = [

 [[package]]
 name = "radicle-httpd"
 version = "0.21.0"
 version = "0.22.0"
 dependencies = [
  "anyhow",
  "axum",

modified radicle-httpd/Cargo.toml

@@ -3,7 +3,7 @@ name = "radicle-httpd"

 description = "Radicle HTTP daemon"
 homepage = "https://radicle.xyz"
 license = "MIT OR Apache-2.0"
 version = "0.21.0"
 version = "0.22.0"
 authors = ["cloudhead <cloudhead@radicle.xyz>", "sebastinez <me@sebastinez.dev>"]
 edition = "2021"
 default-run = "radicle-httpd"

modified radicle-httpd/build/README.md

@@ -22,7 +22,8 @@ one sub-directory per build target.

 Note that it will use `git describe` to get a version number for the build.
 You *must* have a commit tagged with a version in your history or the build
 will fail, eg. `v1.0.0`.
 Make sure to create a release commit where you update the `version` field in the `Cargo.toml` file and tag the commit with a version e.g. `build/tag 0.21.0`.
 Make sure to create a release commit where you update the `version` field in
 the `Cargo.toml` file and tag the commit with a version e.g. `build/tag 0.21.0`.
 When the build completes, the SHA-256 checksums of the artifacts are output.
 For a given Radicle version and source tree, the same set of checksums should

@@ -40,7 +41,8 @@ Here's an example output for a development version of Radicle:

 A script is included in `build/checksums` to output these checksums after
 the artifacts are built.
 Once you have the build artifacts and you have a user on our files.radicle.xyz you can upload them with the following command.
 Once you have the build artifacts and you have a user on our files.radicle.xyz
 you can upload them with the following command.
     SSH_LOGIN=<username> build/upload