mozbridge-cli 0.1.0__tar.gz → 0.2.0__tar.gz

{mozbridge_cli-0.1.0 → mozbridge_cli-0.2.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: mozbridge-cli
-Version: 0.1.0
+Version: 0.2.0
 Summary: Command-line client for the Mozbridge deployment platform: SSO login, build, publish, status, and rollback for any project hosted on Mozbridge.
 Project-URL: Homepage, https://mozbridge.com
 Project-URL: Documentation, https://github.com/jessin01/mozbridge/blob/main/cli/docs/commands.md

{mozbridge_cli-0.1.0 → mozbridge_cli-0.2.0}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "mozbridge-cli"
-version = "0.1.0"
+version = "0.2.0"
 description = "Command-line client for the Mozbridge deployment platform: SSO login, build, publish, status, and rollback for any project hosted on Mozbridge."
 readme = "README.md"
 requires-python = ">=3.10"

mozbridge_cli-0.2.0/scripts/release.sh

@@ -0,0 +1,69 @@
+#!/usr/bin/env bash
+# Bump mozbridge-cli's version, build, and print the exact publish command.
+# Mirrors cruxhive-mcp's own proven release checklist (Development/cruxhive/
+# CLAUDE.md) — same build backend (hatchling), same publish tool (uv) —
+# rather than inventing a separate convention for a sibling package in the
+# same workspace.
+#
+# Does NOT publish. The upload step stays a deliberate, separate, human-run
+# action — same reasoning as cruxhive's own checklist keeps it manual.
+set -euo pipefail
+
+ROOT="$(cd "$(dirname "${BASH_SOURCE[0]}")/.." && pwd)"
+PYPROJECT="$ROOT/pyproject.toml"
+
+usage() {
+  echo "Usage: $0 [--patch|--minor|--major] [--dry-run]" >&2
+  echo "  Default bump: patch" >&2
+  exit 1
+}
+
+BUMP="patch"
+DRY_RUN=0
+for arg in "$@"; do
+  case "$arg" in
+    --patch) BUMP="patch" ;;
+    --minor) BUMP="minor" ;;
+    --major) BUMP="major" ;;
+    --dry-run) DRY_RUN=1 ;;
+    -h|--help) usage ;;
+    *) echo "Unknown argument: $arg" >&2; usage ;;
+  esac
+done
+
+CURRENT=$(grep -m1 '^version' "$PYPROJECT" | sed -E 's/version = "(.*)"/\1/')
+IFS='.' read -r MAJOR MINOR PATCH <<< "$CURRENT"
+
+case "$BUMP" in
+  patch) PATCH=$((PATCH + 1)) ;;
+  minor) MINOR=$((MINOR + 1)); PATCH=0 ;;
+  major) MAJOR=$((MAJOR + 1)); MINOR=0; PATCH=0 ;;
+esac
+
+NEW="${MAJOR}.${MINOR}.${PATCH}"
+
+echo "→ ${CURRENT} → ${NEW} (${BUMP})"
+
+if [ "$DRY_RUN" = "1" ]; then
+  echo "--dry-run: not writing pyproject.toml, not building."
+  exit 0
+fi
+
+sed -i.bak -E "s/^version = \".*\"/version = \"${NEW}\"/" "$PYPROJECT"
+rm -f "$PYPROJECT.bak"
+
+echo "→ Building..."
+rm -rf "$ROOT/dist"
+(cd "$ROOT" && uv build)
+
+echo ""
+echo "✓ ${NEW} built. Review the version bump, then:"
+echo ""
+echo "    git add cli/pyproject.toml"
+echo "    git commit -m \"chore(cli): release v${NEW}\""
+echo "    git push"
+echo "    cd cli && uv publish --token \"\$(awk '/password/{print \$3}' ~/.pypirc)\""
+echo ""
+echo "The publish step is deliberately not automated here — same reasoning"
+echo "as cruxhive-mcp's own release checklist: it's a real, public,"
+echo "largely-permanent action."