From 16757d3452a966318e70be772c137302b8ce891a Mon Sep 17 00:00:00 2001 From: Paul Delafosse Date: Tue, 30 Nov 2021 09:34:30 +0100 Subject: [PATCH] fea!: bump cocogitto version --- README.md | 8 ++++++-- install.sh | 2 +- 2 files changed, 7 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 8718eb1..94e82e4 100644 --- a/README.md +++ b/README.md @@ -33,7 +33,7 @@ If you are familiar with cocogitto this will run `cog check` and nothing else. ## Check commits since latest tag In some case you might want to perform check only since the latest tagged version. -If your repository has not alway been conventional commit compliant, then you probably want to +If your repository has not always been conventional commits compliant, then you probably want to use this option. ```yaml @@ -53,7 +53,7 @@ Let us assume the following git history : ``` Using `check-latest-tag-only: true` here would make cocogitto check for the two commits made since -tag `0.1.0`, the action would fail on *HEAD* which contains the non conventional commit +tag `0.1.0`, the action would fail on *HEAD* which contains the non-conventional commit type 'WIP'. ## Performing release @@ -79,6 +79,10 @@ Note that you probably want to set the `git-user` and `git-user-email` options t If you are not familiar with how cocogitto perform release, you might want to read the [auto bump](https://github.com/oknozor/cocogitto#auto-bump) and [hook](https://github.com/oknozor/cocogitto#auto-bump) sections on cocogitto's documentation. +## Post step run + +Once the step is finished cocogitto's binary will be available in your path. + ## Reference Here are all the inputs available through `with`: diff --git a/install.sh b/install.sh index 7e9639c..cddd4d3 100755 --- a/install.sh +++ b/install.sh @@ -1,7 +1,7 @@ #!/bin/sh CUR_DIR=$(pwd) -VERSION=3.0.0 +VERSION=4.0.0 TAR="cocogitto-$VERSION-x86_64-unknown-linux-musl.tar.gz" BIN_DIR="$HOME/.local/bin"