bump: version 0.3.0 → 0.3.1

fix(astrolabe): update commitizen pattern to properly update info.xml version
The pattern 'version' was too broad and matched multiple lines: - <?xml version="1.0"?> - <version>0.2.1</version> - min-version="30" max-version="32" Changed to '<version>' to specifically match only the version tag. Also fixed version mismatch: info.xml now correctly shows 0.3.0 to match the version in .cz.toml and package.json.
2025-12-19 21:04:50 +00:00 · 2025-12-19 22:04:26 +01:00 · 2025-12-19 20:55:59 +00:00 · 2025-12-19 21:55:36 +01:00 · 2025-12-19 21:48:27 +01:00
5 changed files with 33 additions and 6 deletions
@@ -85,7 +85,7 @@ jobs:

          # Count conventional commits that are NOT scoped to helm or astrolabe
          mcp_commit_count=$(git log "$commit_range" --oneline --grep="^(feat|fix|docs|refactor|perf|test|build|ci|chore)" -E | \
-            grep -v "(helm)" | grep -v "(astrolabe)" | wc -l)
+            { grep -v "(helm)" || true; } | { grep -v "(astrolabe)" || true; } | wc -l)

          if [ "$mcp_commit_count" -gt 0 ]; then
            echo "Found $mcp_commit_count commits for MCP server since $last_mcp_tag"
@@ -1,6 +1,6 @@
 [tool.commitizen]
 name = "cz_conventional_commits"
-version = "0.2.0"
+version = "0.3.1"
 tag_format = "astrolabe-v$version"
 version_scheme = "semver"
 update_changelog_on_bump = true
@@ -8,7 +8,7 @@ major_version_zero = true

 # Update Astrolabe-specific files only
 version_files = [
-    "appinfo/info.xml:version",
+    "appinfo/info.xml:<version>",
    "package.json:version"
 ]

@@ -25,6 +25,33 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Requires external MCP server deployment
 - See documentation for setup: https://github.com/cbcoutinho/nextcloud-mcp-server

+## astrolabe-v0.3.1 (2025-12-19)
+
+### Fix
+
+- **astrolabe**: update commitizen pattern to properly update info.xml version
+
+## astrolabe-v0.3.0 (2025-12-19)
+
+### Fix
+
+- **astrolabe**: prevent workflow failure when only helm/astrolabe commits exist
+- **astrolabe**: info.xml
+
+## astrolabe-v0.2.1 (2025-12-19)
+
+### BREAKING CHANGE
+
+- MCP server now bumps for ANY conventional commit except
+those explicitly scoped to helm or astrolabe.
+
+### Fix
+
+- **ci**: push all tags explicitly in bump workflow
+- **ci**: make MCP server default bump target for all non-scoped commits
+- **ci**: restrict docker build to MCP server tags only
+- **ci**: correct appstore-push-action version to v1.0.4
+
 ## astrolabe-v0.2.0 (2025-12-19)

 ### BREAKING CHANGE
@@ -29,9 +29,9 @@ Astrolabe connects to a semantic search service that understands the meaning of

 See [documentation](https://github.com/cbcoutinho/nextcloud-mcp-server) for configuration details.
 	]]></description>
-	<version>0.2.0</version>
+	<version>0.3.1</version>
 	<licence>agpl</licence>
-	<author mail="chris@coutinho.io" homepage="https://github.com/cbcoutinho">Chris Coutinho</author>
+	<author homepage="https://github.com/cbcoutinho">Chris Coutinho</author>
 	<namespace>Astrolabe</namespace>
 	<category>ai</category>
 	<bugs>https://github.com/cbcoutinho/nextcloud-mcp-server/issues</bugs>
@@ -1,6 +1,6 @@
 {
  "name": "astrolabe",
-  "version": "0.2.0",
+  "version": "0.3.1",
  "license": "AGPL-3.0-or-later",
  "engines": {
    "node": "^22.0.0",
Author	SHA1	Message	Date
github-actions[bot]	9cfadbfc04	bump: version 0.3.0 → 0.3.1	2025-12-19 21:04:50 +00:00
Chris Coutinho	6fed78196e	fix(astrolabe): update commitizen pattern to properly update info.xml version The pattern 'version' was too broad and matched multiple lines: - <?xml version="1.0"?> - <version>0.2.1</version> - min-version="30" max-version="32" Changed to '<version>' to specifically match only the version tag. Also fixed version mismatch: info.xml now correctly shows 0.3.0 to match the version in .cz.toml and package.json.	2025-12-19 22:04:26 +01:00
github-actions[bot]	db430dd2c9	bump: version 0.2.0 → 0.3.0	2025-12-19 20:55:59 +00:00
Chris Coutinho	3618aed39e	fix(astrolabe): prevent workflow failure when only helm/astrolabe commits exist When filtering commits with grep -v, if all commits are filtered out, grep returns exit code 1 which causes the pipeline to fail with set -e. Wrap grep commands in { ... \|\| true; } to ensure they don't fail the pipeline when they filter out all results. This fixes the workflow failure when a fix(astrolabe): commit is pushed without any MCP server changes.	2025-12-19 21:55:36 +01:00
Chris Coutinho	4c083c7314	fix(astrolabe): info.xml	2025-12-19 21:48:27 +01:00