prepare release v2.3.3

Author: pgrange

bash_unit

@@ -19,7 +19,7 @@
 # shellcheck disable=2317  # Ignore unreachable - most function are not called.
 # shellcheck disable=2155  # Ignore Declare and assign separately
 
-VERSION=v2.3.2
+VERSION=v2.3.3
 
 ESCAPE=$(printf "\033")
 NOCOLOR="${ESCAPE}[0m"

docs/man/man1/bash_unit.1

@@ -2,12 +2,12 @@
 .\"     Title: bash_unit
 .\"    Author: [see the "AUTHOR(S)" section]
 .\" Generator: Asciidoctor 2.0.23
-.\"      Date: 2025-01-08
+.\"      Date: 2025-07-02
 .\"    Manual: \ \&
 .\"    Source: \ \&
 .\"  Language: English
 .\"
-.TH "BASH_UNIT" "1" "2025-01-08" "\ \&" "\ \&"
+.TH "BASH_UNIT" "1" "2025-07-02" "\ \&" "\ \&"
 .ie \n(.g .ds Aq \(aq
 .el       .ds Aq '
 .ss \n[.ss] 0
@@ -38,9 +38,10 @@ bash_unit \- bash unit testing enterprise edition framework for professionals!
 run them and, in case of failure, displays the stack trace
 with source file and line number indications to locate the problem.
 .sp
-You might want to take a look at \c
-.URL "getting_started" "how to get started"
-before continuing reading this documentation.
+Need a quick start? The
+\c
+.URL "https://github.com/bash\-unit/getting_started/" "getting started project"
+will help you get on track in no time.
 .sp
 The following functions are available in your tests (see below for detailed documentation):
 .sp
@@ -240,14 +241,14 @@ jobs:
     \- uses: actions/checkout@v4
     \- name: Unit testing with bash_unit
       run: |
-        curl \-s https://raw.githubusercontent.com/bash-unit/bash_unit/master/install.sh | bash
+        curl \-s https://raw.githubusercontent.com/bash\-unit/bash_unit/master/install.sh | bash
         FORCE_COLOR=true ./bash_unit tests/test_*
 .fam
 .fi
 .if n .RE
 .sp
 See this bash_unit \c
-.URL "https://github.com/pgrange/bash_unit_getting_started" "getting started gitlab project" ""
+.URL "https://github.com/pgrange/bash_unit_getting_started" "getting started github project" ""
 for a working example.
 .SS "GitLab CI"
 .sp
@@ -262,7 +263,7 @@ test:
   script:
     \- apt\-get update
     \- apt\-get install \-\-no\-install\-recommends \-y curl ca\-certificates
-    \- curl \-s https://raw.githubusercontent.com/bash-unit/bash_unit/master/install.sh | bash
+    \- curl \-s https://raw.githubusercontent.com/bash\-unit/bash_unit/master/install.sh | bash
     \- FORCE_COLOR=true ./bash_unit tests/test_*
 .fam
 .fi
@@ -283,7 +284,7 @@ Add the following to your pre\-commit configuration. By default it will run scri
 .nf
 .fam C
 repos:
-  \- repo: https://github.com/bash-unit/bash_unit
+  \- repo: https://github.com/bash\-unit/bash_unit
     rev: v2.2.0
     hooks:
       \- id: bash\-unit
@@ -495,7 +496,7 @@ your file is a bash script and \fBbash_unit\fP sources it before running your te
 \fBsetup_suite\fP function and avoid any code outside a bash function. you must not use any bash_unit assertion
 in setup_suite or use exit in setup_suite for teardown_suite to be run.
 See \c
-.URL "https://github.com/bash-unit/bash_unit/issues/43" "issue 43" ""
+.URL "https://github.com/bash\-unit/bash_unit/issues/43" "issue 43" ""
 for more details.
 .sp
 If you want to keep an eye on a test not yet implemented, prefix the name of the function by \fBtodo\fP instead of test.