add blog release for 0.28,0.29,0.30,0.31

Author: Chemaclass

docs/blog/2025-12-01-release-0-28.md

@@ -0,0 +1,78 @@
+---
+date: '2025-12-01'
+title: 'Release 0.28.0'
+description: 'Introducing subcommand-based CLI, inline filter syntax, and smarter test execution behavior.'
+coverAlt: 'Subcommand-based CLI, inline filter syntax, and smarter test execution'
+
+aside: false
+---
+
+# {{ $frontmatter.title }}
+
+<time>{{ $formatDate($frontmatter.date) }}</time>
+
+## 🔧 New features
+
+### Subcommand-based CLI architecture
+
+bashunit now uses a subcommand-based CLI design, making the interface cleaner and more intuitive:
+
+::: code-group
+```bash [Commands]
+bashunit test [path]      # Run tests (default)
+bashunit bench [path]     # Run benchmarks
+bashunit doc [filter]     # Show assertion documentation
+bashunit init [dir]       # Initialize a new project
+bashunit learn            # Interactive tutorial
+bashunit upgrade          # Upgrade to latest version
+```
+:::
+
+The previous flags (`--bench`, `--doc`, `--init`, `--learn`, `--upgrade`) continue to work for backward compatibility.
+
+### Inline filter syntax
+
+Run specific tests directly from the command line using the new inline filter syntax:
+
+::: code-group
+```bash [By function name]
+bashunit tests/example_test.sh::test_my_function
+```
+```bash [By line number]
+bashunit tests/example_test.sh:42
+```
+:::
+
+This makes it faster to rerun a single failing test during development.
+
+### Stop at first assertion failure
+
+Tests now stop at the first assertion failure by default, matching the behavior of PHPUnit and Jest. This prevents cascading failures and makes debugging easier.
+
+If you prefer to run all assertions regardless of failures, use the new `--run-all` flag or set `BASHUNIT_STOP_ON_ASSERTION_FAILURE=false`.
+
+### Display skipped and incomplete tests
+
+New options to display skipped and incomplete tests at the end of the test run:
+
+::: code-group
+```bash [Usage]
+bashunit --show-skipped tests/
+bashunit --show-incomplete tests/
+```
+:::
+
+## 🐛 Bug fixes
+
+- Stop executing remaining commands in `set_up`/`tear_down` after first failure
+- Count all tests as failed when `set_up_before_script` fails
+- Fixed acceptance tests forcing not showing skipped and incomplete tests
+
+## 🌾 Miscellaneous
+
+- Optimize assertion guard: use integer comparison instead of string comparison
+- Optimize string operations with `str::strip_ansi` refactoring
+
+---
+
+See the full changelog on <a href="https://github.com/TypedDevs/bashunit/releases/tag/0.28.0">GitHub</a>

docs/blog/2025-12-08-release-0-29.md

@@ -0,0 +1,109 @@
+---
+date: '2025-12-08'
+title: 'Release 0.29.0'
+description: 'Namespaced internal functions, bootstrap arguments, strict mode, login shell support, and the new assert subcommand.'
+coverAlt: 'Namespaced internals, strict mode, and standalone assertions'
+
+aside: false
+---
+
+# {{ $frontmatter.title }}
+
+<time>{{ $formatDate($frontmatter.date) }}</time>
+
+## 🔧 New features
+
+### Namespaced internal functions
+
+All internal functions and variables are now prefixed with `bashunit::` to prevent naming collisions with your code:
+
+::: code-group
+```bash [Before]
+skip "reason"
+helper::trim "$value"
+```
+```bash [After]
+bashunit::skip "reason"
+bashunit::helper::trim "$value"
+```
+:::
+
+Internal variables are also prefixed: `_TESTS_PASSED` becomes `_BASHUNIT_TESTS_PASSED`. The public API (`assert_*` functions) remains unchanged.
+
+### Bootstrap argument passing
+
+Pass arguments to your bootstrap script using the `--env` flag:
+
+::: code-group
+```bash [Usage]
+bashunit --env "bootstrap.sh arg1 arg2" tests/
+```
+```bash [Environment variable]
+BASHUNIT_BOOTSTRAP_ARGS="arg1 arg2" bashunit tests/
+```
+:::
+
+### Login shell support
+
+Run tests in a login shell context with the new `-l, --login` flag:
+
+::: code-group
+```bash [Usage]
+bashunit --login tests/
+```
+:::
+
+This loads your shell profile, useful when testing scripts that depend on login shell configuration.
+
+### Strict mode
+
+Enable strict shell mode (`set -euo pipefail`) for your tests:
+
+::: code-group
+```bash [Usage]
+bashunit --strict tests/
+```
+```bash [Configuration]
+BASHUNIT_STRICT_MODE=true
+```
+:::
+
+Strict mode catches unset variables and pipeline failures, helping you write more robust scripts.
+
+### Run all assertions
+
+Override the default stop-on-failure behavior with `-R, --run-all`:
+
+::: code-group
+```bash [Usage]
+bashunit --run-all tests/
+```
+:::
+
+### Standalone assert subcommand
+
+Use assertions directly from the command line:
+
+::: code-group
+```bash [Usage]
+bashunit assert equals "expected" "actual"
+bashunit assert contains "needle" "haystack"
+```
+:::
+
+## 🐛 Bug fixes
+
+- Custom assertions now display correct test function name in failure messages
+- Data providers work when `set_up_before_script` changes directory
+- Resolved race conditions in parallel test execution
+- Test doubles are now strict mode compatible
+- Catch intermediate failing commands in `set_up_before_script` and `tear_down_after_script`
+
+## 🌾 Miscellaneous
+
+- Improved `assert` command output: shows `assert <fn>` instead of internal function name
+- `--preserve-env` option to skip `.env` loading and use shell environment only
+
+---
+
+See the full changelog on <a href="https://github.com/TypedDevs/bashunit/releases/tag/0.29.0">GitHub</a>

docs/blog/2025-12-14-release-0-30.md

@@ -0,0 +1,77 @@
+---
+date: '2025-12-14'
+title: 'Release 0.30.0'
+description: 'Failures-only mode, no-color option, human-readable test durations, and multiple standalone assertions.'
+coverAlt: 'Failures-only mode, no-color option, and display improvements'
+
+aside: false
+---
+
+# {{ $frontmatter.title }}
+
+<time>{{ $formatDate($frontmatter.date) }}</time>
+
+## 🔧 New features
+
+### Failures-only mode
+
+Focus on what matters with `--failures-only`, which suppresses passed, skipped, and incomplete tests:
+
+::: code-group
+```bash [Usage]
+bashunit --failures-only tests/
+```
+:::
+
+### No-color output
+
+Disable ANSI colors for cleaner logs in CI environments:
+
+::: code-group
+```bash [Flag]
+bashunit --no-color tests/
+```
+```bash [Environment variable]
+NO_COLOR=1 bashunit tests/
+```
+:::
+
+### Human-readable test duration
+
+Test durations are now displayed in a more readable format:
+
+::: code-group
+```[Output]
+✓ Passed: Fast test                            12 ms
+✓ Passed: Medium test                          1.5 s
+✓ Passed: Slow test                            2m 15s
+```
+:::
+
+Execution time is shown in minutes when tests run over 60 seconds (e.g., "2m 1s").
+
+### Multiple assertions in standalone mode
+
+Chain multiple assertions in a single command:
+
+::: code-group
+```bash [Usage]
+bashunit assert "my_command" exit_code "0" contains "success"
+```
+:::
+
+## 🐛 Bug fixes
+
+- Suppress stdout/stderr during `set_up_before_script` and `tear_down_after_script` (visible in verbose mode)
+- Prevent `.env` override in strict mode tests
+- Fixed internal flaky tests when running `--strict`
+
+## 🌾 Miscellaneous
+
+- **Breaking change**: `--preserve-env` renamed to `--skip-env-file` for clearer semantics
+- **Breaking change**: `BASHUNIT_PRESERVE_ENV` renamed to `BASHUNIT_SKIP_ENV_FILE`
+- Added `release.sh` script to automate the release process
+
+---
+
+See the full changelog on <a href="https://github.com/TypedDevs/bashunit/releases/tag/0.30.0">GitHub</a>

docs/blog/2025-12-19-release-0-31.md

@@ -0,0 +1,92 @@
+---
+date: '2025-12-19'
+title: 'Release 0.31.0'
+description: 'Code coverage tracking with LCOV and HTML reports, minimum coverage thresholds, and lifecycle hook visibility.'
+coverAlt: 'Code coverage tracking, HTML reports, and lifecycle visibility'
+
+aside: false
+---
+
+# {{ $frontmatter.title }}
+
+<time>{{ $formatDate($frontmatter.date) }}</time>
+
+## 🔧 New features
+
+### Code coverage tracking
+
+Track line coverage for your bash scripts using the new coverage options. See the full <a href="/coverage">coverage documentation</a> for details.
+
+::: code-group
+```bash [Console only]
+bashunit --coverage tests/
+```
+```bash [LCOV report]
+bashunit --coverage-report coverage/lcov.info tests/
+```
+```bash [HTML report]
+bashunit --coverage-report-html coverage/ tests/
+```
+:::
+
+Coverage is tracked using Bash's DEBUG trap mechanism. You can customize which paths to track and exclude:
+
+::: code-group
+```bash [Custom paths]
+bashunit --coverage --coverage-paths src/ lib/ tests/
+```
+```bash [Exclude patterns]
+bashunit --coverage --coverage-exclude "tests/*,vendor/*" tests/
+```
+:::
+
+The report shows covered and uncovered lines with color-coded highlighting, making it easy to identify gaps in your test coverage.
+
+### Minimum coverage threshold
+
+Enforce a minimum coverage percentage with `--coverage-min`:
+
+::: code-group
+```bash [Usage]
+bashunit --coverage --coverage-min 80 tests/
+```
+```[Output]
+Coverage: 75.5% (below minimum 80%)
+Exit code: 1
+```
+:::
+
+The test run fails if coverage falls below the threshold, useful for CI pipelines.
+
+### Color-coded coverage output
+
+Console coverage output uses color-coded thresholds:
+
+- Below 50%: red
+- 50-80%: yellow
+- Above 80%: green
+
+### Lifecycle hook visibility
+
+See exactly how long your setup and teardown scripts take:
+
+::: code-group
+```[Output]
+Running set_up_before_script... done (2.3s)
+✓ Passed: My test                              45 ms
+Running tear_down_after_script... done (0.5s)
+```
+:::
+
+This helps identify slow setup and teardown operations that may be affecting your test suite performance. The output is suppressed in failures-only and parallel modes.
+
+## 🐛 Bug fixes
+
+- Fixed `bench` command not working in standalone/installed bashunit (missing `benchmark.sh` in build)
+- Fixed `helper::get_latest_tag` returning version with `^{}` suffix from annotated git tags
+- Skip files with no matching tests when using `--filter`
+- Fixed simple output without before/after script timing
+
+---
+
+See the full changelog on <a href="https://github.com/TypedDevs/bashunit/releases/tag/0.31.0">GitHub</a>