aboutsummaryrefslogtreecommitdiffhomepage
diff options
context:
space:
mode:
authorClement Delafargue <clement.delafargue@fretlink.com>2019-10-08 11:51:48 +0200
committerClement Delafargue <clement.delafargue@fretlink.com>2019-10-08 11:59:48 +0200
commitf55a64c688209e625e7e1ccb50e4db00ee1d8ec3 (patch)
tree2fed81e562802c9d539ac944fb7c684606c00ef8
parent7175382714b9c3ef3c754cbd6431bd0f0ee4465a (diff)
downloadclever-tools-nix-f55a64c688209e625e7e1ccb50e4db00ee1d8ec3.tar.gz
clever-tools-nix-f55a64c688209e625e7e1ccb50e4db00ee1d8ec3.tar.zst
clever-tools-nix-f55a64c688209e625e7e1ccb50e4db00ee1d8ec3.zip
Add contributing help in the readme
-rw-r--r--README.md12
1 files changed, 12 insertions, 0 deletions
diff --git a/README.md b/README.md
index 3d9894a..9d744f5 100644
--- a/README.md
+++ b/README.md
@@ -5,3 +5,15 @@ Nix derivation to install clever-tools - see https://github.com/CleverCloud/clev
5## How to use it 5## How to use it
6 6
7[See the example.nix](https://github.com/fretlink/clever-tools-nix/blob/master/example.nix) 7[See the example.nix](https://github.com/fretlink/clever-tools-nix/blob/master/example.nix)
8
9## How to publish a new version
10
11First, edit `clever-tools/default.nix`, to update the version number. For the expected hash, you can put `0000000000000000000000000000000000000000000000000000` (52 zeroes).
12
13Then, edit `default.nix`, update the `callPackage` line to the new version, as well as the `latest` value.
14
15Once you've done that, add a `mkOlderVersion` for the previous latest version. Once again, you can use the null hash for `sha256`.
16
17Then, run `nix build`. It will give you the correct values for the hashes. Correct those, run it again and you'll see `result-` directories, one per version. Go ahead and make sure they all work.
18
19Finally, don't forget to update `check.sh` with the latest version number.