doc and script fixes. Pushing v0.15.0

Author: aryonoco

.version

@@ -1 +1 @@
-0.14.0
+0.15.0

Directory.Build.props

@@ -1,7 +1,7 @@
 <Project>
   <PropertyGroup>
-    <Version>0.14.0</Version>
-    <AssemblyVersion>0.14.0.0</AssemblyVersion>
-    <FileVersion>0.14.0.0</FileVersion>
+    <Version>0.15.0</Version>
+    <AssemblyVersion>0.15.0.0</AssemblyVersion>
+    <FileVersion>0.15.0.0</FileVersion>
   </PropertyGroup>
 </Project>

docs/VERSIONING.md

@@ -11,7 +11,7 @@ Version is defined in a few central locations and automatically propagated throu
    - Used by: .NET build system, F# assemblies
    - Provides: Assembly version, file version, product version
 
-3. **`README.md`** - Manually updated for documentation
+3. **`README.md`** - Automatically updated by the version script
    - Shows the current version to users
 
 ## How Versions Are Used
@@ -20,22 +20,37 @@ Version is defined in a few central locations and automatically propagated throu
 - **Makefile**: Reads from `.version` file via `$(shell cat .version)`
 - **Docker Compose**: Uses `${VERSION}` environment variable set by Makefile
 - **Export Metadata**: Automatically includes version in exported JSONL files
+- **GitHub Releases**: Uses version from `Directory.Build.props` plus build number (e.g., `v0.14.0-11`)
 
 ## Updating the Version
 
 Use the provided script to update all version references:
 
 ```bash
+# Can be run from any directory
+./scripts/update-version.sh 0.11.0
+
+# Or from within scripts directory
 ./update-version.sh 0.11.0
 ```
 
 This will update:
 - `.version` file
-- `Directory.Build.props` 
-- `README.md`
+- `Directory.Build.props` (Version, AssemblyVersion, FileVersion)
+- `README.md` (all "Version X.Y.Z" references)
 
 All other references will automatically pick up the new version.
 
+## GitHub Release Versioning
+
+The GitHub Actions workflow creates releases with the format: `v{version}-{run_number}`
+
+For example:
+- Local version: `0.14.0`
+- GitHub release: `v0.14.0-11` (where 11 is the GitHub Actions run number)
+
+This ensures each release is unique even if the version hasn't changed.
+
 ## Version Format
 
 Use semantic versioning: `MAJOR.MINOR.PATCH`

scripts/update-version.sh

@@ -1,8 +1,12 @@
 #!/bin/bash
 
+# Get the directory where this script is located
+SCRIPT_DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )"
+PROJECT_ROOT="$( cd "$SCRIPT_DIR/.." && pwd )"
+
 if [ $# -eq 0 ]; then
-    echo "Usage: ./update-version.sh <new-version>"
-    echo "Example: ./update-version.sh 0.11.0"
+    echo "Usage: $0 <new-version>"
+    echo "Example: $0 0.11.0"
     exit 1
 fi
 
@@ -15,15 +19,15 @@ fi
 
 echo "Updating version to $NEW_VERSION..."
 
-echo "$NEW_VERSION" > ../.version
+echo "$NEW_VERSION" > "$PROJECT_ROOT/.version"
 
-sed -i.bak "s|<Version>.*</Version>|<Version>$NEW_VERSION</Version>|g" ../Directory.Build.props
-sed -i.bak "s|<AssemblyVersion>.*</AssemblyVersion>|<AssemblyVersion>$NEW_VERSION.0</AssemblyVersion>|g" ../Directory.Build.props
-sed -i.bak "s|<FileVersion>.*</FileVersion>|<FileVersion>$NEW_VERSION.0</FileVersion>|g" ../Directory.Build.props
-rm ../Directory.Build.props.bak
+sed -i.bak "s|<Version>.*</Version>|<Version>$NEW_VERSION</Version>|g" "$PROJECT_ROOT/Directory.Build.props"
+sed -i.bak "s|<AssemblyVersion>.*</AssemblyVersion>|<AssemblyVersion>$NEW_VERSION.0</AssemblyVersion>|g" "$PROJECT_ROOT/Directory.Build.props"
+sed -i.bak "s|<FileVersion>.*</FileVersion>|<FileVersion>$NEW_VERSION.0</FileVersion>|g" "$PROJECT_ROOT/Directory.Build.props"
+rm "$PROJECT_ROOT/Directory.Build.props.bak"
 
-sed -i.bak "s|Version [0-9]\+\.[0-9]\+\.[0-9]\+|Version $NEW_VERSION|g" ../README.md
-rm ../README.md.bak
+sed -i.bak "s|Version [0-9]\+\.[0-9]\+\.[0-9]\+|Version $NEW_VERSION|g" "$PROJECT_ROOT/README.md"
+rm "$PROJECT_ROOT/README.md.bak"
 
 echo "✓ Version updated to $NEW_VERSION"
 echo ""