release: 0.15.0

Author: Chemaclass

.github/RELEASE.md

@@ -5,15 +5,15 @@ This is a guide to know the steps to create a new release.
 1. Update the version in [BASHUNIT_VERSION](../bashunit)
 1. Update the version in [CHANGELOG.md](../CHANGELOG.md)
 1. Update the version in [package.json](../package.json)
+1. Build the project `./build.sh bin`
+    1. This will generate `bin/bashunit` and `bin/checksum`
 1. Update the checksum(sha256) in [package.json](../package.json)
-    - `./build.sh bin && shasum -a 256 "bin/bashunit" | awk '{ print $1 }'`
 1. Create a [new release](https://github.com/TypedDevs/bashunit/releases/new) from GitHub
-1. Attach the latest executable to the release
-    1. Generate a new bashunit with `build.sh`
-    1. Attach the generated file to the release page on GitHub
-    1. Keep the name `bashunit`
-1. Attach the sha256sum for that executable as a new file `checksum`
-    - `./build.sh bin && shasum -a 256 "bin/bashunit" > bin/checksum`
+1. Attach the latest executable and checksum to the release
+    1. `bin/bashunit`
+    1. `bin/checksum`
+    1. Keep the same name
 1. Commit and push
+    1. It is OK that `tests/acceptance/bashunit_upgrade_test.sh` fails
 1. Rebase `latest` branch from the newly created tag and push
     1. This will trigger "build and deploy" the docs

CHANGELOG.md

@@ -1,6 +1,6 @@
 # Changelog
 
-## [Unreleased](https://github.com/TypedDevs/bashunit/compare/0.14.0...main)
+## [0.15.0](https://github.com/TypedDevs/bashunit/compare/0.14.0...0.15.0) - 2024-09-01
 
 - Fixed `--filter|-f` to work with `test_*` matching function name input.
 - Added assertions to log file

bashunit

@@ -2,7 +2,7 @@
 set -euo pipefail
 
 # shellcheck disable=SC2034
-declare -r BASHUNIT_VERSION="0.14.0"
+declare -r BASHUNIT_VERSION="0.15.0"
 
 # shellcheck disable=SC2155
 declare -r BASHUNIT_ROOT_DIR="$(dirname "${BASH_SOURCE[0]}")"

docs/quickstart.md

@@ -45,7 +45,7 @@ Once **bashunit** is installed, you're ready to get started.
 
 4.  If everything works correctly, you should see an output similar to the following:
     ```
-    bashunit - 0.14.0 | Total tests: 1
+    bashunit - 0.15.0 | Total tests: 1
     Running local/example_test.sh
     ✓ Passed: Bashunit is working
 

package.json

@@ -1,7 +1,7 @@
 {
   "name": "bashunit-docs",
-  "version": "0.14.0",
-  "checksum": "84822a2f2d3a84646abad5fe26e6d49a952c6e5ea08e3752443d583346cc4d56",
+  "version": "0.15.0",
+  "checksum": "a201257512fe99e10016e223f21f9ae5689627016856729462a597306474f7a3",
   "description": "Docs for bashunit a simple testing library for bash scripts",
   "main": "index.js",
   "repository": "[email protected]:TypedDevs/bashunit.git",