@programinglive/commiter 1.0.12 → 1.1.0

package/.github/ISSUE_TEMPLATE/bug_report.md

@@ -1,28 +1,28 @@
----
-name: Bug report
-about: Create a report to help us improve
-labels: bug
----
-
-## Describe the bug
-A clear and concise description of what the bug is.
-
-## To Reproduce
-Steps to reproduce the behavior:
-1. Go to '...'
-2. Click on '...'
-3. See error
-
-## Expected behavior
-A clear and concise description of what you expected to happen.
-
-## Screenshots or logs
-If applicable, add screenshots, logs, or stack traces to help explain your problem.
-
-## Environment
-- Package version:
-- Node.js version:
-- OS:
-
-## Additional context
-Add any other context about the problem here.
+---
+name: Bug report
+about: Create a report to help us improve
+labels: bug
+---
+
+## Describe the bug
+A clear and concise description of what the bug is.
+
+## To Reproduce
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '...'
+3. See error
+
+## Expected behavior
+A clear and concise description of what you expected to happen.
+
+## Screenshots or logs
+If applicable, add screenshots, logs, or stack traces to help explain your problem.
+
+## Environment
+- Package version:
+- Node.js version:
+- OS:
+
+## Additional context
+Add any other context about the problem here.

package/.github/ISSUE_TEMPLATE/config.yml

@@ -1,5 +1,5 @@
-blank_issues_enabled: false
-contact_links:
-  - name: Security Report
-    url: https://github.com/programinglive/commiter/security/policy
-    about: Please read our security policy before reporting vulnerabilities.
+blank_issues_enabled: false
+contact_links:
+  - name: Security Report
+    url: https://github.com/programinglive/commiter/security/policy
+    about: Please read our security policy before reporting vulnerabilities.

package/.github/ISSUE_TEMPLATE/feature_request.md

@@ -1,20 +1,20 @@
----
-name: Feature request
-about: Suggest an idea for this project
-labels: enhancement
----
-
-## Summary
-Describe the feature you would like to see.
-
-## Problem or Use Case
-What problem does this feature solve? Why is it needed?
-
-## Proposed Solution
-Describe your proposed solution or implementation ideas.
-
-## Alternatives
-List any alternative solutions or features you've considered.
-
-## Additional context
-Add any other context, mockups, or screenshots about the feature request here.
+---
+name: Feature request
+about: Suggest an idea for this project
+labels: enhancement
+---
+
+## Summary
+Describe the feature you would like to see.
+
+## Problem or Use Case
+What problem does this feature solve? Why is it needed?
+
+## Proposed Solution
+Describe your proposed solution or implementation ideas.
+
+## Alternatives
+List any alternative solutions or features you've considered.
+
+## Additional context
+Add any other context, mockups, or screenshots about the feature request here.

package/.github/PULL_REQUEST_TEMPLATE.md

@@ -1,24 +1,24 @@
-# Pull Request Checklist
-
-## Summary
-
-Describe the changes in this pull request.
-
-## Related Issues
-
-Link related issues (e.g. closes #123).
-
-## Testing
-
-- [ ] `npm install`
-- [ ] `npm test`
-- [ ] `npm run release -- --dry-run` (if release-related)
-
-## Checklist
-
-- [ ] I've read the [Code of Conduct](../CODE_OF_CONDUCT.md)
-- [ ] I've read the [Contributing Guidelines](../CONTRIBUTING.md)
-- [ ] My commits follow the Conventional Commits format (`type(scope): subject`)
-- [ ] Documentation has been updated if needed
-- [ ] New dependencies are justified and added to `package.json`
-- [ ] No `any` types were introduced (TypeScript rule)
+# Pull Request Checklist
+
+## Summary
+
+Describe the changes in this pull request.
+
+## Related Issues
+
+Link related issues (e.g. closes #123).
+
+## Testing
+
+- [ ] `npm install`
+- [ ] `npm test`
+- [ ] `npm run release -- --dry-run` (if release-related)
+
+## Checklist
+
+- [ ] I've read the [Code of Conduct](../CODE_OF_CONDUCT.md)
+- [ ] I've read the [Contributing Guidelines](../CONTRIBUTING.md)
+- [ ] My commits follow the Conventional Commits format (`type(scope): subject`)
+- [ ] Documentation has been updated if needed
+- [ ] New dependencies are justified and added to `package.json`
+- [ ] No `any` types were introduced (TypeScript rule)

package/CHANGELOG.md

@@ -2,6 +2,13 @@
 
 All notable changes to this project will be documented in this file. See [standard-version](https://github.com/conventional-changelog/standard-version) for commit guidelines.
 
+## [1.1.0](https://github.com/programinglive/commiter/compare/v1.0.12...v1.1.0) (2025-10-29)
+
+
+### 📝 Documentation
+
+* clarify release automation flow ([1cf7aa2](https://github.com/programinglive/commiter/commit/1cf7aa2432f371eac69d6931c8a497991686bfc6))
+
 ### [1.0.12](https://github.com/programinglive/commiter/compare/v1.0.11...v1.0.12) (2025-10-29)
 
 
@@ -39,46 +46,46 @@ All notable changes to this project will be documented in this file. See [standa
 
 * add release helper script and tests ([93f4235](https://github.com/programinglive/commiter/commit/93f4235c3cf2e34b77b78ba51c0337cf89e564df))
 
-### [1.0.6](https://github.com/programinglive/commiter/compare/v1.0.5...v1.0.6) (2025-10-19)
-
-### [1.0.5](https://github.com/programinglive/commiter/compare/v1.0.4...v1.0.5) (2025-10-19)
-
-
-### 🐛 Bug Fixes
-
-* allow release commits with emoji ([26c4afa](https://github.com/programinglive/commiter/commit/26c4afa26fc7c11c91ac576dcba197cba5d3d98a))
-
-### [1.0.4](https://github.com/programinglive/commiter/compare/v1.0.3...v1.0.4) (2025-10-19)
-
-
-### 🐛 Bug Fixes
-
-* ensure safe test default for initial release ([27d2ee3](https://github.com/programinglive/commiter/commit/27d2ee35d1e558ef459a61e41627305997621392))
-
-### [1.0.3](https://github.com/programinglive/commiter/compare/v1.0.2...v1.0.3) (2025-10-19)
-
-### [1.0.2](https://github.com/programinglive/commiter/compare/v1.0.1...v1.0.2) (2025-10-19)
-
-### [1.0.1](https://github.com/programinglive/commiter/compare/v1.0.0...v1.0.1) (2025-10-18)
-
-
-### 🐛 Bug Fixes
-
-* align commitlint config with project module type ([d051eac](https://github.com/programinglive/commiter/commit/d051eace5471d0c54fd8de6a3bede6a0df020dad))
-
-## 1.0.0 (2025-10-17)
-
-
-### ✨ Features
-
-* initial project setup with standard-version and conventional commits ([0accf6d](https://github.com/programinglive/commiter/commit/0accf6dba678c1946629aa3f1b691bea7e20cd95))
-
-
-### 📝 Documentation
-
-* add community health files and apply package tooling ([0fa802b](https://github.com/programinglive/commiter/commit/0fa802b6129053d3f32030cec561e5926dd09c42))
-
-
-### 🧹 Chores
-
-* update package metadata ([7c112f3](https://github.com/programinglive/commiter/commit/7c112f3d82e2c92ed31fa3e60fafd5ca0429184d))
+### [1.0.6](https://github.com/programinglive/commiter/compare/v1.0.5...v1.0.6) (2025-10-19)
+
+### [1.0.5](https://github.com/programinglive/commiter/compare/v1.0.4...v1.0.5) (2025-10-19)
+
+
+### 🐛 Bug Fixes
+
+* allow release commits with emoji ([26c4afa](https://github.com/programinglive/commiter/commit/26c4afa26fc7c11c91ac576dcba197cba5d3d98a))
+
+### [1.0.4](https://github.com/programinglive/commiter/compare/v1.0.3...v1.0.4) (2025-10-19)
+
+
+### 🐛 Bug Fixes
+
+* ensure safe test default for initial release ([27d2ee3](https://github.com/programinglive/commiter/commit/27d2ee35d1e558ef459a61e41627305997621392))
+
+### [1.0.3](https://github.com/programinglive/commiter/compare/v1.0.2...v1.0.3) (2025-10-19)
+
+### [1.0.2](https://github.com/programinglive/commiter/compare/v1.0.1...v1.0.2) (2025-10-19)
+
+### [1.0.1](https://github.com/programinglive/commiter/compare/v1.0.0...v1.0.1) (2025-10-18)
+
+
+### 🐛 Bug Fixes
+
+* align commitlint config with project module type ([d051eac](https://github.com/programinglive/commiter/commit/d051eace5471d0c54fd8de6a3bede6a0df020dad))
+
+## 1.0.0 (2025-10-17)
+
+
+### ✨ Features
+
+* initial project setup with standard-version and conventional commits ([0accf6d](https://github.com/programinglive/commiter/commit/0accf6dba678c1946629aa3f1b691bea7e20cd95))
+
+
+### 📝 Documentation
+
+* add community health files and apply package tooling ([0fa802b](https://github.com/programinglive/commiter/commit/0fa802b6129053d3f32030cec561e5926dd09c42))
+
+
+### 🧹 Chores
+
+* update package metadata ([7c112f3](https://github.com/programinglive/commiter/commit/7c112f3d82e2c92ed31fa3e60fafd5ca0429184d))

package/CODE_OF_CONDUCT.md

@@ -1,36 +1,36 @@
-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-We pledge to make participation in `@programinglive/commiter` open, welcoming, and harassment-free for everyone, regardless of age, body size, disability, ethnicity, gender identity or expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
-
-## Our Standards
-**Positive behaviours**
-- Showing empathy and kindness toward other people
-- Respecting differing opinions, viewpoints, and experiences
-- Giving and gracefully accepting constructive feedback
-- Accepting responsibility and apologizing when mistakes occur
-
-**Unacceptable behaviours**
-- Use of sexualized language or imagery, or unwelcome sexual attention
-- Trolling, insulting or derogatory comments, and personal attacks
-- Public or private harassment
-- Publishing others' private information without permission
-- Other conduct which would reasonably be considered inappropriate in a professional setting
-
-## Enforcement Responsibilities
-Project maintainers are responsible for clarifying standards of acceptable behaviour and will take appropriate corrective action in response to unacceptable behaviour. Maintainers have the right to remove, edit, or reject contributions that do not align with this Code of Conduct.
-
-## Scope
-This Code of Conduct applies within all project spaces and when an individual is officially representing the project in public spaces.
-
-## Enforcement
-Report incidents to `security@programinglive.com`. All complaints will be reviewed promptly and treated confidentially.
-
-## Enforcement Guidelines
-1. **Correction** – Private warning for minor violations and clarification of expectations.
-2. **Warning** – Consequence for a single serious violation or repeated minor violations.
-3. **Temporary Ban** – Temporary exclusion from community interactions when behaviour is unacceptable.
-4. **Permanent Ban** – Permanent removal from the community for sustained inappropriate behaviour or harassment.
-
-## Attribution
-Adapted from the [Contributor Covenant](https://www.contributor-covenant.org/version/2/1/code_of_conduct.html).
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+We pledge to make participation in `@programinglive/commiter` open, welcoming, and harassment-free for everyone, regardless of age, body size, disability, ethnicity, gender identity or expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+**Positive behaviours**
+- Showing empathy and kindness toward other people
+- Respecting differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing when mistakes occur
+
+**Unacceptable behaviours**
+- Use of sexualized language or imagery, or unwelcome sexual attention
+- Trolling, insulting or derogatory comments, and personal attacks
+- Public or private harassment
+- Publishing others' private information without permission
+- Other conduct which would reasonably be considered inappropriate in a professional setting
+
+## Enforcement Responsibilities
+Project maintainers are responsible for clarifying standards of acceptable behaviour and will take appropriate corrective action in response to unacceptable behaviour. Maintainers have the right to remove, edit, or reject contributions that do not align with this Code of Conduct.
+
+## Scope
+This Code of Conduct applies within all project spaces and when an individual is officially representing the project in public spaces.
+
+## Enforcement
+Report incidents to `security@programinglive.com`. All complaints will be reviewed promptly and treated confidentially.
+
+## Enforcement Guidelines
+1. **Correction** – Private warning for minor violations and clarification of expectations.
+2. **Warning** – Consequence for a single serious violation or repeated minor violations.
+3. **Temporary Ban** – Temporary exclusion from community interactions when behaviour is unacceptable.
+4. **Permanent Ban** – Permanent removal from the community for sustained inappropriate behaviour or harassment.
+
+## Attribution
+Adapted from the [Contributor Covenant](https://www.contributor-covenant.org/version/2/1/code_of_conduct.html).

package/LICENSE

@@ -1,21 +1,21 @@
-MIT License
-
-Copyright (c) 2025 Programming Live
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+MIT License
+
+Copyright (c) 2025 Programming Live
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/PUBLISH.md

@@ -1,142 +1,142 @@
-# Publishing to NPM
-
-This guide explains how to publish the `@programinglive/commiter` package to npm.
-
-## Prerequisites
-
-1. **NPM Account**: Create an account at [npmjs.com](https://www.npmjs.com/)
-2. **Login to NPM**: Run `npm login` in your terminal
-3. **Organization Access**: Ensure you have access to the `@programinglive` organization on npm
-
-## Publishing Steps
-
-### 1. Login to NPM
-
-```bash
-npm login
-```
-
-Enter your npm credentials when prompted.
-
-### 2. Verify Package Configuration
-
-Check that `package.json` is correctly configured:
-
-```bash
-npm pack --dry-run
-```
-
-This shows what files will be included in the package.
-
-### 3. Publish the Package
-
-For the first publish:
-
-```bash
-npm publish --access public
-```
-
-**Note**: The `--access public` flag is required for scoped packages (@programinglive/commiter) to be publicly accessible.
-
-### 4. Verify Publication
-
-Check your package on npm:
-```
-https://www.npmjs.com/package/@programinglive/commiter
-```
-
-## Releasing New Versions
-
-After the initial publish, use the built-in release commands:
-
-### Patch Release (1.0.0 → 1.0.1)
-```bash
-npm run release:patch
-git push --follow-tags origin main
-npm publish
-```
-
-### Minor Release (1.0.0 → 1.1.0)
-```bash
-npm run release:minor
-git push --follow-tags origin main
-npm publish
-```
-
-### Major Release (1.0.0 → 2.0.0)
-```bash
-npm run release:major
-git push --follow-tags origin main
-npm publish
-```
-
-## Automated Release Workflow
-
-### Option 1: Manual Publishing (Traditional)
-1. Make changes and commit using conventional commits
-2. Run the appropriate release command
-3. Push to GitHub with tags
-4. Publish to npm
-
-Example:
-```bash
-# Make changes
-git add .
-git commit -m "feat(cli): add interactive setup wizard"
-
-# Create release
-npm run release:minor
-
-# Push to GitHub
-git push --follow-tags origin main
-
-# Publish to npm
-npm publish
-```
-
-### Option 2: Automated Publishing (Recommended)
-1. Make changes and commit using conventional commits
-2. Run the appropriate release command
-3. Push to GitHub with tags - **npm publishing happens automatically**
-
-Example:
-```bash
-# Make changes
-git add .
-git commit -m "feat(cli): add interactive setup wizard"
-
-# Create release
-npm run release:minor
-
-# Push to GitHub (triggers automatic npm publish)
-git push --follow-tags origin main
-```
-
-**Setup Required for Automated Publishing:**
-1. Add `NPM_TOKEN` secret to your GitHub repository
-2. The GitHub Actions workflow (`.github/workflows/publish.yml`) will automatically:
-   - Run tests
-   - Publish to npm when a tag starting with `v` is pushed
-   - Use the `--access public` flag for scoped packages
-
-## Unpublishing (Emergency Only)
-
-If you need to unpublish a version within 72 hours:
-
-```bash
-npm unpublish @programinglive/commiter@1.0.0
-```
-
-**Warning**: Unpublishing is permanent and should only be used in emergencies.
-
-## Package Visibility
-
-- **Public**: Anyone can install and use the package
-- **Open Source**: MIT licensed - users can modify and distribute
-- **Free**: No cost to install or use
-
-## Support
-
-For issues or questions:
-- GitHub Issues: https://github.com/programinglive/commiter/issues
-- NPM Package: https://www.npmjs.com/package/@programinglive/commiter
+# Publishing to NPM
+
+This guide explains how to publish the `@programinglive/commiter` package to npm.
+
+## Prerequisites
+
+1. **NPM Account**: Create an account at [npmjs.com](https://www.npmjs.com/)
+2. **Login to NPM**: Run `npm login` in your terminal
+3. **Organization Access**: Ensure you have access to the `@programinglive` organization on npm
+
+## Publishing Steps
+
+### 1. Login to NPM
+
+```bash
+npm login
+```
+
+Enter your npm credentials when prompted.
+
+### 2. Verify Package Configuration
+
+Check that `package.json` is correctly configured:
+
+```bash
+npm pack --dry-run
+```
+
+This shows what files will be included in the package.
+
+### 3. Publish the Package
+
+For the first publish:
+
+```bash
+npm publish --access public
+```
+
+**Note**: The `--access public` flag is required for scoped packages (@programinglive/commiter) to be publicly accessible.
+
+### 4. Verify Publication
+
+Check your package on npm:
+```
+https://www.npmjs.com/package/@programinglive/commiter
+```
+
+## Releasing New Versions
+
+After the initial publish, use the built-in release commands:
+
+### Patch Release (1.0.0 → 1.0.1)
+```bash
+npm run release:patch
+git push --follow-tags origin main
+npm publish
+```
+
+### Minor Release (1.0.0 → 1.1.0)
+```bash
+npm run release:minor
+git push --follow-tags origin main
+npm publish
+```
+
+### Major Release (1.0.0 → 2.0.0)
+```bash
+npm run release:major
+git push --follow-tags origin main
+npm publish
+```
+
+## Automated Release Workflow
+
+### Option 1: Manual Publishing (Traditional)
+1. Make changes and commit using conventional commits
+2. Run the appropriate release command
+3. Push to GitHub with tags
+4. Publish to npm
+
+Example:
+```bash
+# Make changes
+git add .
+git commit -m "feat(cli): add interactive setup wizard"
+
+# Create release
+npm run release:minor
+
+# Push to GitHub
+git push --follow-tags origin main
+
+# Publish to npm
+npm publish
+```
+
+### Option 2: Automated Publishing (Recommended)
+1. Make changes and commit using conventional commits
+2. Run the appropriate release command
+3. Push to GitHub with tags - **npm publishing happens automatically**
+
+Example:
+```bash
+# Make changes
+git add .
+git commit -m "feat(cli): add interactive setup wizard"
+
+# Create release
+npm run release:minor
+
+# Push to GitHub (triggers automatic npm publish)
+git push --follow-tags origin main
+```
+
+**Setup Required for Automated Publishing:**
+1. Add `NPM_TOKEN` secret to your GitHub repository
+2. The GitHub Actions workflow (`.github/workflows/publish.yml`) will automatically:
+   - Run tests
+   - Publish to npm when a tag starting with `v` is pushed
+   - Use the `--access public` flag for scoped packages
+
+## Unpublishing (Emergency Only)
+
+If you need to unpublish a version within 72 hours:
+
+```bash
+npm unpublish @programinglive/commiter@1.0.0
+```
+
+**Warning**: Unpublishing is permanent and should only be used in emergencies.
+
+## Package Visibility
+
+- **Public**: Anyone can install and use the package
+- **Open Source**: MIT licensed - users can modify and distribute
+- **Free**: No cost to install or use
+
+## Support
+
+For issues or questions:
+- GitHub Issues: https://github.com/programinglive/commiter/issues
+- NPM Package: https://www.npmjs.com/package/@programinglive/commiter