publish

publish

Merge dev commits into main, create a release (planned or incremental), and deploy to production.

PARAMETER MODES:

1. No parameter (default): Publish main repository
2. Submodule name parameter (e.g., /publish foundation): Publish that specific submodule only

---

Release Numbering Strategy

Planned Releases (Milestones):

• Use semantic versioning: vX.Y.0 (major.minor.0)
• Examples: v1.0.0, v1.1.0, v2.0.0
• Created via /create_release command with full workflow
• Control major and minor version numbers

Incremental Releases (Continuous Deployments):

• Use semantic versioning as patches: vX.Y.Z where Z increments
• Examples: If last planned release is v1.1.0, incremental releases are v1.1.1, v1.1.2
• Auto-generated via /publish command
• Only patch version increments (never major or minor)

Relationship:

• Independent purposes: Planned releases are milestones, incremental releases are continuous deployments
• Example sequence: v1.0.0 (planned) → v1.0.1, v1.0.2 (incremental) → v1.1.0 (planned) → v1.1.1 (incremental)

---

Parameter Detection and Routing

STEP 1: Detect parameter and route to appropriate workflow:

# Check if parameter provided
if [ -n "$1" ]; then
  PARAM="$1"
  
  # Submodule mode: publish that submodule only
  echo "📦 SUBMODULE MODE: Publishing submodule '$PARAM'"
  # Verify submodule exists
  if ! git submodule status "$PARAM" >/dev/null 2>&1; then
    echo "❌ Submodule not found: $PARAM"
    exit 1
  fi
  # Proceed to submodule publish workflow
else
  # Main repo mode: publish main repository
  echo "📦 MAIN REPO MODE: Publishing main repository"
  # Proceed to main repository publish workflow
fi

---

Submodule Publish Workflow

When a specific submodule name is provided (e.g., /publish foundation):

1. Change to submodule directory:

   cd "$PARAM" || {
     echo "❌ Failed to change to submodule directory: $PARAM"
     exit 1
   }