You have commit messages with errors ⧗ input: fix: Add missing CLI optional dependencies and entry point Add the missing [cli] optional dependencies (click>=8.0.0, rich>=13.0.0) and [project.scripts] entry point configuration to pyproject.toml. This fixes the inconsistency between the documented CLI installation method in ADVANCED-USEAGE.MD and the actual package configuration. The CLI module was already implemented but could not be properly installed using 'pip install "nocodb-simple-client[cli]"' as documented, because the required dependencies and console script entry point were missing from the package configuration. Changes: - Add [project.optional-dependencies.cli] with click and rich - Add [project.scripts] with nocodb entry point - Enables proper installation: pip install "nocodb-simple-client[cli]" ✖ subject must not be sentence-case, start-case, pascal-case, upper-case [subject-case] ✖ found 1 problems, 0 warnings ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint ⧗ input: fix: Reorganize optional dependencies and add tomllib support Reorganize optional dependencies into proper runtime feature groups and fix TOML loading to use stdlib tomllib for Python 3.11+. Changes to pyproject.toml: - Add [async] optional dependencies (aiohttp, aiofiles) - Add [config] optional dependencies (PyYAML, tomli) - Add [dotenv] optional dependencies (python-dotenv) - Reorganize [cli] to runtime section - Remove runtime features from [dev] dependencies - Group dependencies by purpose (runtime vs development) Changes to config.py: - Update TOML loading to use stdlib tomllib for Python 3.11+ - Fall back to tomli for Python < 3.11 - Improve error message to indicate stdlib availability These changes fix several issues: 1. Config file support (YAML/TOML) now properly declared as optional 2. Async client dependencies separated from dev dependencies 3. Users can install only needed features (e.g., pip install ".[async]") 4. Better Python 3.11+ support using stdlib tomllib 5. Clearer separation between runtime and development dependencies ✖ subject must not be sentence-case, start-case, pascal-case, upper-case [subject-case] ✖ found 1 problems, 0 warnings ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint ⧗ input: docs: Add documentation for optional dependencies installation Update documentation to include all new optional dependency groups introduced in the previous commits. This ensures users know how to install the exact features they need. Changes to README.template.MD: - Add "Optional Features" section with installation examples - Document all available extras: cli, async, config, dotenv, dev, docs - Include descriptions of what each extra provides - Show how to combine multiple extras Changes to ADVANCED-USEAGE.MD: - Add installation instructions for async support - Add installation instructions for config file support - Document both YAML/TOML support and .env support - Use consistent formatting for dependency sections This documentation matches the package structure changes made in previous commits where runtime features were properly separated into optional dependency groups. ✖ subject must not be sentence-case, start-case, pascal-case, upper-case [subject-case] ✖ found 1 problems, 0 warnings ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint ⧗ input: fix: Add python-dotenv back to dev dependencies Re-add python-dotenv to [dev] dependencies as it is required by the test fixtures in conftest.py. While dotenv is optional for end users (via [dotenv] extra), it is mandatory for running tests. The test suite uses python-dotenv in conftest.py to load .env files for test configuration, making it a development dependency rather than just a runtime optional feature. Fixes test failure: ImportError while loading conftest.py tests/conftest.py:12: from dotenv import load_dotenv This ensures CI/CD tests can run successfully while keeping dotenv optional for library