Bump version to 0.1.1 and update README.md and PUBLISHING.md for clarity

- Updated version number in pyproject.toml from 0.1.0 to 0.1.1.
- Enhanced README.md with additional details on features, benefits, and use cases.
- Improved PUBLISHING.md with clearer instructions and formatting for publishing to PyPI.

Author: starkbaknet

README.md

@@ -322,12 +322,14 @@ pv index --smart /path/to/your/project
 ```
 
 **Features**:
+
 - **Priority-based processing**: New files → Modified files → Deleted files
 - **Partial reindexing**: Only updates changed chunks (60-70% faster)
 - **Automatic detection**: Compares file content hashes to detect real changes
 - **Smart categorization**: Distinguishes between new, modified, and deleted files
 
 **When to use**:
+
 - Large codebases with frequent changes
 - After making targeted edits to specific files
 - When you want detailed statistics about what changed
@@ -351,12 +353,14 @@ pv index-git . --since HEAD~10
 ```
 
 **Benefits**:
+
 - **Extremely fast**: Only processes files that actually changed in git
 - **Perfect for CI/CD**: Index only PR changes
 - **Branch-aware**: Compare against any branch or commit
 - **Automatic fallback**: Uses standard indexing if not a git repo
 
 **Use cases**:
+
 - After pulling changes from remote
 - Before code review (index only PR changes)
 - In CI/CD pipelines (index only new commits)
@@ -378,12 +382,14 @@ pv sync --watch --debounce 0.5 .
 ```
 
 **Debounce explained**:
+
 - Waits specified seconds after last file change before indexing
 - Batches multiple rapid changes together
 - Prevents redundant indexing when saving files multiple times
 - Reduces CPU usage during active development
 
 **Recommended debounce values**:
+
 - **0.5-1.0s**: Fast machines, instant feedback needed
 - **2.0s** (default): Balanced performance
 - **5.0-10.0s**: Slower machines, large codebases
@@ -553,7 +559,7 @@ pv status /path/to/your/project
 
 ## Changelog
 
-### v0.1.0
+### v0.1.1
 
 - **Enhanced Single-Word Search**: Optimized search for single keywords with high precision
 - **Multi-Level Chunking**: Added micro-chunks and word-level chunks for better granularity

docs/PUBLISHING.md

@@ -5,6 +5,7 @@ This guide explains how to publish the project-vectorizer package to PyPI.
 ## Prerequisites
 
 1. **PyPI Account**: Create accounts on both:
+
    - [TestPyPI](https://test.pypi.org/account/register/) (for testing)
    - [PyPI](https://pypi.org/account/register/) (for production)
 
@@ -19,20 +20,23 @@ This guide explains how to publish the project-vectorizer package to PyPI.
 This is the easiest method using GitHub Actions:
 
 1. **Update Version Number**:
+
    ```bash
    # Edit pyproject.toml and update the version
    vim pyproject.toml
-   # Change: version = "0.1.0" to version = "0.1.1"
+   # Change: version = "0.1.1" to version = "0.1.2"
    ```
 
 2. **Commit and Push Changes**:
+
    ```bash
    git add pyproject.toml
    git commit -m "Bump version to 0.1.1"
    git push
    ```
 
 3. **Create a GitHub Release**:
+
    ```bash
    # Create and push a tag
    git tag v0.1.1
@@ -58,6 +62,7 @@ This is the easiest method using GitHub Actions:
 You can manually trigger a publish to TestPyPI or PyPI:
 
 1. **Go to GitHub Actions**:
+
    - Navigate to your repository → Actions tab
    - Select "Publish to PyPI" workflow
 
@@ -73,11 +78,13 @@ You can manually trigger a publish to TestPyPI or PyPI:
 For local testing and publishing:
 
 1. **Install Build Tools**:
+
    ```bash
    pip install build twine
    ```
 
 2. **Build the Package**:
+
    ```bash
    # Clean previous builds
    rm -rf dist/ build/ *.egg-info/
@@ -87,6 +94,7 @@ For local testing and publishing:
    ```
 
 3. **Test the Build**:
+
    ```bash
    # Check the package
    twine check dist/*
@@ -96,6 +104,7 @@ For local testing and publishing:
    ```
 
 4. **Upload to TestPyPI** (Testing):
+
    ```bash
    twine upload --repository testpypi dist/*
 
@@ -186,18 +195,22 @@ rm -rf test_env
 ### Common Issues:
 
 1. **Version already exists**:
+
    - You cannot re-upload the same version
    - Increment the version number in `pyproject.toml`
 
 2. **Authentication failed**:
+
    - Verify your API token or Trusted Publisher setup
    - Check GitHub Actions secrets
 
 3. **Package not found**:
+
    - Wait a few minutes after publishing
    - Check PyPI for the package page
 
 4. **Import errors after install**:
+
    - Verify MANIFEST.in includes all necessary files
    - Check that `__init__.py` files exist in all packages
 
@@ -215,6 +228,7 @@ After publishing:
 ## Support
 
 For issues with publishing:
+
 - Check [PyPI Help](https://pypi.org/help/)
 - Review [Python Packaging Guide](https://packaging.python.org/)
 - Open an issue in the repository

pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "project-vectorizer"
-version = "0.1.0"
+version = "0.1.1"
 description = "CLI tool for vectorizing codebases and serving them via MCP"
 authors = [{name = "StarkBak", email = "bak.stark06@gmail.com"}]
 license = {text = "MIT"}