1.0.8 — CI/workflow bash fixes and stable version bump
Summary
- Bump package version to 1.0.8 (from 1.0.7) to mark a stable release.
- Fix several bash conditional syntax issues in GitHub Actions workflows that previously caused steps to fail.
- Include regenerated Node package artifacts produced after the version change (committed as part of the release commit).
What changed
- Version bump
- package.json: version changed from 1.0.7 → 1.0.8.
- Purpose: mark a stable release (remove the dev suffix indicated by prior pre-release state).
- Impact: consumers and package tooling will see 1.0.8 as the current release. There are no code/API changes connected to this bump.
- GitHub Actions workflow fixes (syntax errors in bash conditionals)
Files changed:
- .github/workflows/benchmark.yml
- .github/workflows/regenerate-reports.yml
Problems fixed:
- Several if [ ... ] conditionals lacked required spacing (for example "if [-f" instead of "if [ -f"), which leads to bash syntax errors and failing workflow steps.
- Specific fixes include (representative):
- if [-f visualizations.html]; then → if [ -f visualizations.html ]; then
- if [! -f index.html]; then → if [ ! -f index.html ]; then
- if [-n "${{ inputs.run_id }}"]; then → if [ -n "${{ inputs.run_id }}" ]; then
- if [-z "$RUN_ID"]; then → if [ -z "$RUN_ID" ]; then
- if ["$FILE_COUNT" -eq 0]; then → if [ "$FILE_COUNT" -eq 0 ]; then
Why it matters
- Workflows that previously failed (deploy-pages step in benchmark.yml and steps in regenerate-reports.yml) due to invalid bash conditional syntax will now run as intended.
- CI reliability is improved: benchmark artifact handling, creation of legacy single-page.html, index.html redirect creation, and the regenerate-reports download/validation logic are no longer vulnerable to the bash parsing errors that caused early exits.
Impact on users and developers
-
Users/consumers:
- No runtime or API behavioral changes. The package contents and public interfaces remain unchanged.
- The version number is updated to 1.0.8; package managers and consumers will see the new version.
-
Developers / maintainers:
- CI workflows should no longer fail due to these bash syntax errors. If you experienced failing runs on pages deploy or report regeneration, rerun the workflows to confirm the fixes.
- There are no code-level breaking changes — only workflow and metadata updates.
Committed node artifacts
- The release commit also includes regenerated node artifacts produced after the version change (examples mentioned in the commit message):
- node_modules/.package-lock.json
- node_modules/.vite/vitest/results.json
Notes and recommended actions:
- These node_modules artifacts were included as a side effect of installing or building after the version bump. Consider whether committing them is desired for this repository; if not, revert those files or add them to .gitignore.
- Verify release tagging/publishing: the version bump indicates a release candidate for publishing — ensure the release tag, changelog, and npm (or other registry) publish steps (if any) are in sync with this version.
- Run or watch CI workflows that were failing previously (benchmark and regenerate-reports) to confirm behavior is fixed in the repository's CI runs.
Compatibility and breaking changes
- No breaking changes to the package API or behavior.
- The only behavioral change is that GitHub Actions workflows that previously failed due to bash syntax will now execute properly.
Testing / Verification
- Confirm the following locally or in CI:
- benchmark.yml: deploy-pages job completes, index.html or legacy-single-page.html logic produces expected artifacts.
- regenerate-reports.yml: run_id selection, artifact download, and file count checks complete without syntax errors.
- package.json version is correct and, if you publish, that the published version aligns with 1.0.8.
Changelog highlights (TL;DR)
- Fix: correct bash conditional spacing in GitHub Actions workflows (benchmark & regenerate-reports) — prevents workflow failures.
- Chore: bump package version 1.0.7 → 1.0.8 (stable release).