@programinglive/commiter 1.2.12 → 1.2.17

package/docs/CREATE_RELEASES.md

@@ -1,103 +1,103 @@
-# Creating GitHub Releases
-
-This guide explains how to populate your GitHub releases page with releases from your tags.
-
-## Problem
-
-You have tags in your repository (v1.0.0, v1.1.9, etc.) but the GitHub releases page is empty. GitHub doesn't automatically create releases from tags - you need to create them manually.
-
-## Solution Options
-
-### Option 1: Use the Automated Script (Recommended)
-
-We've created a script that will automatically create releases for all your tags using the content from CHANGELOG.md.
-
-#### Prerequisites
-1. Create a GitHub Personal Access Token:
-   - Go to https://github.com/settings/tokens
-   - Click "Generate new token" → "Generate new token (classic)"
-   - Give it a name like "Commiter Releases"
-   - Select scope: `repo` (Full control of private repositories)
-   - Click "Generate token"
-   - **Copy the token immediately** (you won't see it again!)
-
-#### Steps
-1. Set your GitHub token as an environment variable:
-   ```powershell
-   # Windows PowerShell
-   $env:GITHUB_TOKEN="your_token_here"
-   ```
-
-2. Run the script:
-   ```bash
-   node scripts/create-releases.js
-   ```
-
-3. The script will:
-   - Read all your local tags
-   - Parse CHANGELOG.md for release notes
-   - Create GitHub releases for each tag
-   - Skip tags that already have releases
-
-### Option 2: Create Releases Manually
-
-If you prefer to create releases manually or just want to create the latest release:
-
-1. Go to https://github.com/programinglive/commiter/releases
-2. Click "Draft a new release"
-3. Click "Choose a tag" and select `v1.1.9`
-4. Set the release title to `v1.1.9`
-5. Copy the release notes from CHANGELOG.md (lines 5-10):
-   ```markdown
-   ### 🐛 Bug Fixes
-
-   * convert release scripts to CJS to support ESM projects ([842da02](https://github.com/programinglive/commiter/commit/842da0298f1c4df7aa93b43ca8698e3669ef6450))
-   ```
-6. Click "Publish release"
-7. Repeat for other versions if needed
-
-### Option 3: Use GitHub CLI (if installed)
-
-If you have GitHub CLI installed (`gh`):
-
-```bash
-# Create release for v1.1.9
-gh release create v1.1.9 \
-  --title "v1.1.9" \
-  --notes "### 🐛 Bug Fixes
-
-* convert release scripts to CJS to support ESM projects"
-
-# Or create from CHANGELOG
-gh release create v1.1.9 --notes-file CHANGELOG.md
-```
-
-## After Creating Releases
-
-Once releases are created, they will appear on:
-- https://github.com/programinglive/commiter/releases
-- The right sidebar of your repository
-- In the repository's release feed
-
-## Automating Future Releases
-
-To automatically create GitHub releases during your release process, you can:
-
-1. **Add to your release script** - Modify `scripts/release.cjs` to create GitHub releases
-2. **Use GitHub Actions** - Set up a workflow that creates releases when tags are pushed
-3. **Use the script** - Run `scripts/create-releases.js` after each release
-
-## Troubleshooting
-
-### "GITHUB_TOKEN not set"
-Make sure you've set the environment variable in your current terminal session.
-
-### "API rate limit exceeded"
-GitHub API has rate limits. The script waits 1 second between requests to avoid this. If you hit the limit, wait an hour and try again.
-
-### "Resource not accessible by integration"
-Your token doesn't have the right permissions. Make sure you selected the `repo` scope when creating the token.
-
-## Security Note
-
-**Never commit your GitHub token to the repository!** Always use environment variables or secure secret management.
+# Creating GitHub Releases
+
+This guide explains how to populate your GitHub releases page with releases from your tags.
+
+## Problem
+
+You have tags in your repository (v1.0.0, v1.1.9, etc.) but the GitHub releases page is empty. GitHub doesn't automatically create releases from tags - you need to create them manually.
+
+## Solution Options
+
+### Option 1: Use the Automated Script (Recommended)
+
+We've created a script that will automatically create releases for all your tags using the content from CHANGELOG.md.
+
+#### Prerequisites
+1. Create a GitHub Personal Access Token:
+   - Go to https://github.com/settings/tokens
+   - Click "Generate new token" → "Generate new token (classic)"
+   - Give it a name like "Commiter Releases"
+   - Select scope: `repo` (Full control of private repositories)
+   - Click "Generate token"
+   - **Copy the token immediately** (you won't see it again!)
+
+#### Steps
+1. Set your GitHub token as an environment variable:
+   ```powershell
+   # Windows PowerShell
+   $env:GITHUB_TOKEN="your_token_here"
+   ```
+
+2. Run the script:
+   ```bash
+   node scripts/create-releases.js
+   ```
+
+3. The script will:
+   - Read all your local tags
+   - Parse CHANGELOG.md for release notes
+   - Create GitHub releases for each tag
+   - Skip tags that already have releases
+
+### Option 2: Create Releases Manually
+
+If you prefer to create releases manually or just want to create the latest release:
+
+1. Go to https://github.com/programinglive/commiter/releases
+2. Click "Draft a new release"
+3. Click "Choose a tag" and select `v1.1.9`
+4. Set the release title to `v1.1.9`
+5. Copy the release notes from CHANGELOG.md (lines 5-10):
+   ```markdown
+   ### 🐛 Bug Fixes
+
+   * convert release scripts to CJS to support ESM projects ([842da02](https://github.com/programinglive/commiter/commit/842da0298f1c4df7aa93b43ca8698e3669ef6450))
+   ```
+6. Click "Publish release"
+7. Repeat for other versions if needed
+
+### Option 3: Use GitHub CLI (if installed)
+
+If you have GitHub CLI installed (`gh`):
+
+```bash
+# Create release for v1.1.9
+gh release create v1.1.9 \
+  --title "v1.1.9" \
+  --notes "### 🐛 Bug Fixes
+
+* convert release scripts to CJS to support ESM projects"
+
+# Or create from CHANGELOG
+gh release create v1.1.9 --notes-file CHANGELOG.md
+```
+
+## After Creating Releases
+
+Once releases are created, they will appear on:
+- https://github.com/programinglive/commiter/releases
+- The right sidebar of your repository
+- In the repository's release feed
+
+## Automating Future Releases
+
+To automatically create GitHub releases during your release process, you can:
+
+1. **Add to your release script** - Modify `scripts/release.cjs` to create GitHub releases
+2. **Use GitHub Actions** - Set up a workflow that creates releases when tags are pushed
+3. **Use the script** - Run `scripts/create-releases.js` after each release
+
+## Troubleshooting
+
+### "GITHUB_TOKEN not set"
+Make sure you've set the environment variable in your current terminal session.
+
+### "API rate limit exceeded"
+GitHub API has rate limits. The script waits 1 second between requests to avoid this. If you hit the limit, wait an hour and try again.
+
+### "Resource not accessible by integration"
+Your token doesn't have the right permissions. Make sure you selected the `repo` scope when creating the token.
+
+## Security Note
+
+**Never commit your GitHub token to the repository!** Always use environment variables or secure secret management.

package/{PRD.md → docs/PRD.md}

@@ -1,96 +1,96 @@
-# Commiter Product Requirements Document (PRD)
-
-## 1. Overview
-Commiter is a CLI utility that bootstraps and automates conventional release workflows for JavaScript/TypeScript projects. It enforces commit conventions, orchestrates semantic version bumps, keeps release tooling configured, and surfaces feedback during release execution so teams can ship confidently.
-
-## 2. Problem Statement
-Growing teams often struggle to keep release processes consistent: commit messages drift from convention, changelogs become stale, and release scripts accumulate manual steps. Commiter removes this friction by installing opinionated tooling, providing curated scripts, and running guard rails (tests, linters) before invoking `standard-version` to publish a release.
-
-## 3. Goals & Success Metrics
-- **Consistent releases**: Every release run through Commiter formats commits, updates changelogs, tags, and version bumps without manual editing.
-- **Low ceremony onboarding**: A single `npx commiter` command prepares repositories (Husky, commitlint, release scripts).
-- **Signal-rich automation**: Release logs clearly show which steps ran, including any warnings (e.g., tests skipped). Zero noisy deprecation warnings.
-- **Reliability**: New releases do not regress existing behavior; the automated test suite passes (`node --test`).
-- **Adoption Metric**: Track installations (npm downloads) and successful release script exits.
-
-## 4. Personas
-1. **Solo Maintainer** – wants painless semantic releases without memorizing commands.
-2. **Team Lead** – enforces commit standards across contributors and ensures releases produce accurate changelogs.
-3. **DevOps/CI Engineer** – integrates Commiter’s release command into CI pipelines and expects deterministic, machine-readable output.
-
-## 5. Key Features
-- **Setup CLI (`index.js`)**
-  - Installs dev dependencies (`standard-version`, `commitlint`, `husky`).
-  - Configures package scripts (`npm run release`, `release:major/minor/patch`, `release:first`).
-  - Creates Husky hooks and commitlint configuration.
-  - Generates release helper script and ensures executable permissions (POSIX-friendly).
-- **Release Helper (`scripts/release.js`)**
-  - Detects release type from CLI args or npm context.
-  - Runs project tests via detected package manager before releasing.
-  - Invokes `standard-version`, passing the preload script via `NODE_OPTIONS`.
-  - Supports first release mode that sets version to 0.0.1 for new projects.
-  - Stays focused on repository assets only (website updates are intentionally manual to avoid cross-project impacts).
-- **Preload Patching (`scripts/preload/fs-f-ok.cjs`)**
-  - Hooks Node’s module loader to transparently replace deprecated `fs.F_OK` usages in `standard-version` without altering `node_modules`.
-- **Website & Documentation**
-  - Professional landing page in `web/` directory.
-  - Automated GitHub Releases generation.
-  - Open Graph social media preview support.
-- **Testing**
-  - Suite executed via `node --test` covers setup utilities, release argument parsing, and the preload patch.
-
-## 6. Functional Requirements
-1. Running `npx @programinglive/commiter` inside a Node project should configure release tooling without manual edits.
-2. `npm run release` must:
-   - Run the project’s tests (if defined) with the correct package manager.
-   - Execute `standard-version`, passing the preload script via `NODE_OPTIONS`.
-   - Exit with non-zero status if tests or standard-version commands fail.
-3. CLI should provide friendly console output (status icons, instructions).
-4. The preload script must eliminate `[DEP0176] fs.F_OK` warnings on supported Node versions.
-5. Documentation (README, PRD, release notes) remains shipped with the package.
-
-## 7. Non-Functional Requirements
-- **Compatibility**: Supports Node.js 18+ (aligning with dependencies); tested on Windows/macOS/Linux.
-- **Maintainability**: Avoid direct edits to dependencies; wrap behavior in Commiter-controlled modules.
-- **Performance**: Release command overhead minimal (<1s additional startup time) beyond running tests and standard-version.
-- **Security**: No network requests during CLI execution beyond npm installs triggered by the user.
-
-## 8. User Journeys
-1. **Initial Setup**
-   - Run `npx @programinglive/commiter`.
-   - Tool installs dependencies, updates `package.json`, and scaffolds Husky hooks.
-   - Maintainer confirms success message and new scripts.
-2. **First Release**
-   - Developer runs `npm run release:first` for new projects.
-   - Commiter sets version to 0.0.1, runs tests, creates initial changelog and git tag.
-   - Project foundation established with proper semantic versioning.
-3. **Standard Release**
-   - Developer runs `npm run release minor` or `npm run release` (defaults to patch).
-   - Commiter runs tests, ensures preload patch prevents deprecation warnings, executes `standard-version`.
-   - Release completes with updated changelog and git tag.
-4. **CI Pipeline**
-   - CI job executes `npm run release -- --prerelease beta`.
-   - Logs show tests executed, no deprecation warnings, and release artifacts generated.
-
-## 9. Milestones & Roadmap
-- **v1.1.x** (current)
-  - Deprecation warning mitigation, enhanced tests, PRD + release documentation.
-- **Future Considerations**
-  - Support for monorepo detection (Lerna/Nx) to run scoped releases.
-  - Optional lint/test command customization via config file.
-  - Telemetry opt-in for release statistics (downloads, success rates).
-
-## 10. Risks & Mitigations
-- **Dependency API Changes**: Upstream packages may alter file paths. Mitigate with targeted module resolution and tests.
-- **User Customization Conflicts**: Custom scripts might skip tests. Provide documentation for overriding behavior.
-- **Platform Differences**: Windows path quoting; addressed via `buildPreloadFlag` helper.
-
-## 11. Release & QA Checklist
-- [x] `npm test` (alias for `node --test`) passes.
-- [x] Manual run of `node scripts/release.js --help` shows no `[DEP0176]` warning.
-- [ ] Update `CHANGELOG.md` (handled by standard-version during actual release).
-- [ ] Verify README reflects latest setup instructions before shipping.
-
-## 12. Appendices
-- **Release Notes**: See `docs/release-notes/` for per-change summaries.
-- **Testing Artifacts**: `test/` directory contains Node test runner suites.
+# Commiter Product Requirements Document (PRD)
+
+## 1. Overview
+Commiter is a CLI utility that bootstraps and automates conventional release workflows for JavaScript/TypeScript projects. It enforces commit conventions, orchestrates semantic version bumps, keeps release tooling configured, and surfaces feedback during release execution so teams can ship confidently.
+
+## 2. Problem Statement
+Growing teams often struggle to keep release processes consistent: commit messages drift from convention, changelogs become stale, and release scripts accumulate manual steps. Commiter removes this friction by installing opinionated tooling, providing curated scripts, and running guard rails (tests, linters) before invoking `standard-version` to publish a release.
+
+## 3. Goals & Success Metrics
+- **Consistent releases**: Every release run through Commiter formats commits, updates changelogs, tags, and version bumps without manual editing.
+- **Low ceremony onboarding**: A single `npx commiter` command prepares repositories (Husky, commitlint, release scripts).
+- **Signal-rich automation**: Release logs clearly show which steps ran, including any warnings (e.g., tests skipped). Zero noisy deprecation warnings.
+- **Reliability**: New releases do not regress existing behavior; the automated test suite passes (`node --test`).
+- **Adoption Metric**: Track installations (npm downloads) and successful release script exits.
+
+## 4. Personas
+1. **Solo Maintainer** – wants painless semantic releases without memorizing commands.
+2. **Team Lead** – enforces commit standards across contributors and ensures releases produce accurate changelogs.
+3. **DevOps/CI Engineer** – integrates Commiter’s release command into CI pipelines and expects deterministic, machine-readable output.
+
+## 5. Key Features
+- **Setup CLI (`index.js`)**
+  - Installs dev dependencies (`standard-version`, `commitlint`, `husky`).
+  - Configures package scripts (`npm run release`, `release:major/minor/patch`, `release:first`).
+  - Creates Husky hooks and commitlint configuration.
+  - Generates release helper script and ensures executable permissions (POSIX-friendly).
+- **Release Helper (`scripts/release.js`)**
+  - Detects release type from CLI args or npm context.
+  - Runs project tests via detected package manager before releasing.
+  - Invokes `standard-version`, passing the preload script via `NODE_OPTIONS`.
+  - Supports first release mode that sets version to 0.0.1 for new projects.
+  - Stays focused on repository assets only (website updates are intentionally manual to avoid cross-project impacts).
+- **Preload Patching (`scripts/preload/fs-f-ok.cjs`)**
+  - Hooks Node’s module loader to transparently replace deprecated `fs.F_OK` usages in `standard-version` without altering `node_modules`.
+- **Website & Documentation**
+  - Professional landing page in `web/` directory.
+  - Automated GitHub Releases generation.
+  - Open Graph social media preview support.
+- **Testing**
+  - Suite executed via `node --test` covers setup utilities, release argument parsing, and the preload patch.
+
+## 6. Functional Requirements
+1. Running `npx @programinglive/commiter` inside a Node project should configure release tooling without manual edits.
+2. `npm run release` must:
+   - Run the project’s tests (if defined) with the correct package manager.
+   - Execute `standard-version`, passing the preload script via `NODE_OPTIONS`.
+   - Exit with non-zero status if tests or standard-version commands fail.
+3. CLI should provide friendly console output (status icons, instructions).
+4. The preload script must eliminate `[DEP0176] fs.F_OK` warnings on supported Node versions.
+5. Documentation (README, PRD, release notes) remains shipped with the package. Each project integrating Commiter must keep a `docs/PRD.md` file present in the repository. The release helper enforces this by warning when the PRD is missing so maintainers remember to author or update the document before tagging releases.
+
+## 7. Non-Functional Requirements
+- **Compatibility**: Supports Node.js 18+ (aligning with dependencies); tested on Windows/macOS/Linux.
+- **Maintainability**: Avoid direct edits to dependencies; wrap behavior in Commiter-controlled modules.
+- **Performance**: Release command overhead minimal (<1s additional startup time) beyond running tests and standard-version.
+- **Security**: No network requests during CLI execution beyond npm installs triggered by the user.
+
+## 8. User Journeys
+1. **Initial Setup**
+   - Run `npx @programinglive/commiter`.
+   - Tool installs dependencies, updates `package.json`, and scaffolds Husky hooks.
+   - Maintainer confirms success message and new scripts.
+2. **First Release**
+   - Developer runs `npm run release:first` for new projects.
+   - Commiter sets version to 0.0.1, runs tests, creates initial changelog and git tag.
+   - Project foundation established with proper semantic versioning.
+3. **Standard Release**
+   - Developer runs `npm run release minor` or `npm run release` (defaults to patch).
+   - Commiter runs tests, ensures preload patch prevents deprecation warnings, executes `standard-version`.
+   - Release completes with updated changelog and git tag.
+4. **CI Pipeline**
+   - CI job executes `npm run release -- --prerelease beta`.
+   - Logs show tests executed, no deprecation warnings, and release artifacts generated.
+
+## 9. Milestones & Roadmap
+- **v1.1.x** (current)
+  - Deprecation warning mitigation, enhanced tests, PRD + release documentation.
+- **Future Considerations**
+  - Support for monorepo detection (Lerna/Nx) to run scoped releases.
+  - Optional lint/test command customization via config file.
+  - Telemetry opt-in for release statistics (downloads, success rates).
+
+## 10. Risks & Mitigations
+- **Dependency API Changes**: Upstream packages may alter file paths. Mitigate with targeted module resolution and tests.
+- **User Customization Conflicts**: Custom scripts might skip tests. Provide documentation for overriding behavior.
+- **Platform Differences**: Windows path quoting; addressed via `buildPreloadFlag` helper.
+
+## 11. Release & QA Checklist
+- [x] `npm test` (alias for `node --test`) passes.
+- [x] Manual run of `node scripts/release.js --help` shows no `[DEP0176]` warning.
+- [ ] Update `CHANGELOG.md` (handled by standard-version during actual release).
+- [ ] Verify README reflects latest setup instructions before shipping.
+
+## 12. Appendices
+- **Release Notes**: See `docs/release-notes/` for per-change summaries.
+- **Testing Artifacts**: `test/` directory contains Node test runner suites.

package/docs/QUICK_RELEASE_GUIDE.md

@@ -1,101 +1,101 @@
-# Quick Guide: Create GitHub Release for v1.1.9
-
-Follow these simple steps to create your first GitHub release:
-
-## Step 1: Navigate to New Release Page
-1. Make sure you're logged into GitHub
-2. Go to: https://github.com/programinglive/commiter/releases/new
-
-## Step 2: Fill in the Form
-
-### Choose a tag
-- Click "Choose a tag"
-- Type: `v1.1.9`
-- Click "Create new tag: v1.1.9 on publish"
-
-### Release title
-- Type: `v1.1.9`
-
-### Describe this release
-Copy and paste this content:
-
-```markdown
-### 🐛 Bug Fixes
-
-* convert release scripts to CJS to support ESM projects ([842da02](https://github.com/programinglive/commiter/commit/842da0298f1c4df7aa93b43ca8698e3669ef6450))
-```
-
-## Step 3: Publish
-- Click the green "Publish release" button
-
-## Done! ✅
-
-Your release will now appear at: https://github.com/programinglive/commiter/releases
-
----
-
-## Create More Releases (Optional)
-
-If you want to create releases for older versions, here's the content for each:
-
-### v1.1.8
-**Title:** `v1.1.8`  
-**Description:**
-```markdown
-### 🐛 Bug Fixes
-
-* update installation script to copy missing files and update gitignore ([5d56259](https://github.com/programinglive/commiter/commit/5d562592fe35b684fa12bd89748b24551ae28a66))
-```
-
-### v1.1.7
-**Title:** `v1.1.7`  
-**Description:**
-```markdown
-### 📝 Documentation
-
-* recommend dev workflow mcp server ([58a5054](https://github.com/programinglive/commiter/commit/58a5054fafd627ef23c448fd93b1383518590ad2))
-```
-
-### v1.1.6
-**Title:** `v1.1.6`  
-**Description:**
-```markdown
-### 🐛 Bug Fixes
-
-* revert to simple release notes staging to avoid git ref conflicts ([2f6a40e](https://github.com/programinglive/commiter/commit/2f6a40ed7259cffdb0b1de1633af3e43df475044))
-```
-
-### v1.1.5
-**Title:** `v1.1.5`  
-**Description:**
-```markdown
-### ✨ Features
-
-* include release notes in release commit via amendment ([3f2afa8](https://github.com/programinglive/commiter/commit/3f2afa8bd0bd264d047df06ae791384e74dc827e))
-
-### 📝 Documentation
-
-* update release notes for v1.1.5 ([cb3dbe6](https://github.com/programinglive/commiter/commit/cb3dbe62a85a174bfb074e3d2526a005fc83d0d7))
-```
-
-### v1.1.1
-**Title:** `v1.1.1`  
-**Description:**
-```markdown
-### 🐛 Bug Fixes
-
-* remove fs.F_OK deprecation warning ([1b0652b](https://github.com/programinglive/commiter/commit/1b0652b88d1b095e1045994948f75ce8194f9d3a))
-```
-
-### v1.0.12
-**Title:** `v1.0.12`  
-**Description:**
-```markdown
-### ✨ Features
-
-* auto-detect test command during release ([602e30e](https://github.com/programinglive/commiter/commit/602e30e94ff7c58b35f8c54bd495c0334352c72c))
-```
-
----
-
-**Tip:** You only need to create releases for the major versions (1.1.9, 1.1.8, 1.1.7, etc.). You can skip the older patch versions if you want to save time.
+# Quick Guide: Create GitHub Release for v1.1.9
+
+Follow these simple steps to create your first GitHub release:
+
+## Step 1: Navigate to New Release Page
+1. Make sure you're logged into GitHub
+2. Go to: https://github.com/programinglive/commiter/releases/new
+
+## Step 2: Fill in the Form
+
+### Choose a tag
+- Click "Choose a tag"
+- Type: `v1.1.9`
+- Click "Create new tag: v1.1.9 on publish"
+
+### Release title
+- Type: `v1.1.9`
+
+### Describe this release
+Copy and paste this content:
+
+```markdown
+### 🐛 Bug Fixes
+
+* convert release scripts to CJS to support ESM projects ([842da02](https://github.com/programinglive/commiter/commit/842da0298f1c4df7aa93b43ca8698e3669ef6450))
+```
+
+## Step 3: Publish
+- Click the green "Publish release" button
+
+## Done! ✅
+
+Your release will now appear at: https://github.com/programinglive/commiter/releases
+
+---
+
+## Create More Releases (Optional)
+
+If you want to create releases for older versions, here's the content for each:
+
+### v1.1.8
+**Title:** `v1.1.8`  
+**Description:**
+```markdown
+### 🐛 Bug Fixes
+
+* update installation script to copy missing files and update gitignore ([5d56259](https://github.com/programinglive/commiter/commit/5d562592fe35b684fa12bd89748b24551ae28a66))
+```
+
+### v1.1.7
+**Title:** `v1.1.7`  
+**Description:**
+```markdown
+### 📝 Documentation
+
+* recommend dev workflow mcp server ([58a5054](https://github.com/programinglive/commiter/commit/58a5054fafd627ef23c448fd93b1383518590ad2))
+```
+
+### v1.1.6
+**Title:** `v1.1.6`  
+**Description:**
+```markdown
+### 🐛 Bug Fixes
+
+* revert to simple release notes staging to avoid git ref conflicts ([2f6a40e](https://github.com/programinglive/commiter/commit/2f6a40ed7259cffdb0b1de1633af3e43df475044))
+```
+
+### v1.1.5
+**Title:** `v1.1.5`  
+**Description:**
+```markdown
+### ✨ Features
+
+* include release notes in release commit via amendment ([3f2afa8](https://github.com/programinglive/commiter/commit/3f2afa8bd0bd264d047df06ae791384e74dc827e))
+
+### 📝 Documentation
+
+* update release notes for v1.1.5 ([cb3dbe6](https://github.com/programinglive/commiter/commit/cb3dbe62a85a174bfb074e3d2526a005fc83d0d7))
+```
+
+### v1.1.1
+**Title:** `v1.1.1`  
+**Description:**
+```markdown
+### 🐛 Bug Fixes
+
+* remove fs.F_OK deprecation warning ([1b0652b](https://github.com/programinglive/commiter/commit/1b0652b88d1b095e1045994948f75ce8194f9d3a))
+```
+
+### v1.0.12
+**Title:** `v1.0.12`  
+**Description:**
+```markdown
+### ✨ Features
+
+* auto-detect test command during release ([602e30e](https://github.com/programinglive/commiter/commit/602e30e94ff7c58b35f8c54bd495c0334352c72c))
+```
+
+---
+
+**Tip:** You only need to create releases for the major versions (1.1.9, 1.1.8, 1.1.7, etc.). You can skip the older patch versions if you want to save time.