npm - specweave - Versions diffs - 1.0.506 → 1.0.508 - Mend

specweave 1.0.506 → 1.0.508

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (1038) hide show

package/plugins/specweave-release/README.md DELETED Viewed

@@ -1,508 +0,0 @@
-# SpecWeave Release Management Plugin
-**Comprehensive release management for single-repo, multi-repo, and monorepo architectures.**
-## Overview
-The **specweave-release** plugin provides end-to-end release management capabilities including:
-- **Release Strategy Design** - Analyze architecture and recommend optimal versioning approach
-- **Version Alignment** - Coordinate versions across multiple repositories
-- **RC Workflows** - Manage release candidates from creation to production promotion
-- **Multi-Repo Coordination** - Orchestrate complex releases across dozens of services
-- **Brownfield Detection** - Automatically detect and document existing release patterns
-- **Living Documentation** - Maintain release strategy and version matrices
-## Components
-### Skills (3 total)
-| Skill | Purpose | When to Use |
-|-------|---------|-------------|
-| **release-strategy-advisor** | Analyze architecture and recommend release strategy | "What release strategy should we use?" |
-| **release-expert** | Full release orchestration: version alignment, multi-repo coordination, dependency management | "Coordinate release across 5 microservices", "Align versions before release" |
-| **rc-manager** | Manage release candidate lifecycle and testing | "Create RC for v2.0.0" |
-### Agents (1 total)
-| Agent | Purpose | Tools |
-|-------|---------|-------|
-| **release-manager** | Master orchestrator for all release activities | Read, Write, Edit, Bash, Glob, Grep |
-### Commands (4+ total)
-| Command | Purpose |
-|---------|---------|
-| `/sw-release:init` | Initialize or analyze release strategy |
-| `/sw-release:align` | Align versions across repositories |
-| `/sw-release:rc` | Manage release candidates |
-| `/sw-release:coordinate` | Plan coordinated multi-repo releases |
-| `/sw-release:publish` | Execute releases (single or multi-repo) |
-| `/sw-release:rollback` | Rollback failed releases |
-| `/sw-release:matrix` | Show/update version matrix |
-## Installation
-**Automatic** (via SpecWeave init):
-```bash
-# Already installed if you ran specweave init
-npx specweave init .
-```
-**Manual** (if needed):
-```bash
-/plugin install sw-release@specweave
-```
-## Quick Start
-### Greenfield Project (New Release Strategy)
-```bash
-# 1. Initialize release strategy
-/sw-release:init
-# Answer questions:
-# - How many repositories? [3]
-# - Team structure? [One team]
-# - Deployment frequency? [Weekly]
-# - Coupling? [Moderate]
-# → Creates: .specweave/docs/internal/delivery/release-strategy.md
-# → Recommends: Umbrella versioning strategy
-# 2. Create first release
-/sw:increment "0001-v1-0-0-release"
-# 3. Align versions
-/sw-release:align
-# 4. Create RC
-/sw-release:rc create 1.0.0
-# 5. Test and promote
-/sw-release:rc promote 1.0.0-rc.3
-```
-### Brownfield Project (Existing Release Process)
-```bash
-# 1. Analyze existing release patterns
-/sw-release:init
-# → Detects:
-#   - Git tags (v1.0.0, v1.1.0, ...)
-#   - CI/CD (.github/workflows/release.yml)
-#   - Monorepo tools (Lerna, Nx)
-#   - Current strategy (independent versioning)
-# → Creates: .specweave/docs/internal/delivery/release-strategy.md
-# → Documents: Existing process + recommendations
-# 2. Start using SpecWeave for next release
-/sw:increment "0010-v2-0-0-release"
-/sw-release:align
-/sw-release:rc create 2.0.0
-```
-## Use Cases
-### Single-Repo Release
-**Scenario**: NPM package with semantic versioning
-```bash
-# Current: v1.5.0
-# Goal: Release v2.0.0 (breaking changes)
-# 1. Initialize strategy (if not done)
-/sw-release:init
-# 2. Create release increment
-/sw:increment "0050-v2-release"
-# 3. Align version (analyze commits → suggest v2.0.0)
-/sw-release:align
-# 4. Create RC
-/sw-release:rc create 2.0.0
-# → v2.0.0-rc.1 → staging → testing
-# 5. Iterate if needed
-# Fix bugs → /sw-release:rc iterate 2.0.0-rc.1
-# → v2.0.0-rc.2
-# 6. Promote to production
-/sw-release:rc promote 2.0.0-rc.3
-# → v2.0.0 → gradual rollout
-```
-### Multi-Repo Coordinated Release
-**Scenario**: 5 microservices with umbrella versioning
-```bash
-# Repos:
-# - frontend v4.2.0
-# - backend v2.8.0
-# - api-gateway v3.1.0
-# - auth-service v2.0.0
-# - shared-lib v1.5.0
-# Goal: Product v5.0.0 (breaking changes in 3 services)
-# 1. Create product release increment
-/sw:increment "0060-product-v5-release"
-# 2. Analyze and align versions
-/sw-release:align
-# → Suggests:
-#   frontend: v5.0.0 (breaking)
-#   backend: v2.9.0 (feature)
-#   api-gateway: v4.0.0 (breaking)
-#   auth-service: v2.0.0 (no change)
-#   shared-lib: v2.0.0 (breaking)
-# 3. Create coordinated RC
-/sw-release:rc create-multi product-v5.0.0
-# → Tags all repos with rc.1
-# 4. Test cross-service
-# → Staging deployment (all services)
-# → E2E tests (cross-service flows)
-# 5. Promote when ready
-/sw-release:rc promote-multi product-v5.0.0-rc.2
-# → Wave-by-wave deployment
-# → Updates version matrix
-```
-### Monorepo Release (Lerna/Nx)
-**Scenario**: Lerna monorepo with 12 packages (independent versioning)
-```bash
-# Current: 12 packages with different versions
-# 1. Initialize strategy (detects Lerna)
-/sw-release:init
-# → Detects: Lerna independent mode
-# → Documents: Current approach
-# 2. Align versions (only changed packages)
-/sw-release:align
-# → Analyzes commits per package
-# → Suggests bumps for changed packages only
-# → Validates inter-package dependencies
-# 3. Execute release
-# → Integration with Lerna: lerna publish
-# → Or manual: npm version + npm publish per package
-```
-## Release Strategies
-### Lockstep Versioning
-**Use When**:
-- Tight coupling between repos
-- Small team (all work together)
-- Breaking changes affect all repos
-**How It Works**:
-```yaml
-All repos share same version:
-  frontend: v3.0.0
-  backend: v3.0.0
-  api: v3.0.0
-Bump together:
-  Breaking change in any repo → All bump to v4.0.0
-```
-### Independent Versioning
-**Use When**:
-- Loose coupling between repos
-- Large team (autonomous squads)
-- Frequent releases (daily/weekly)
-**How It Works**:
-```yaml
-Each repo has own version:
-  frontend: v5.0.0
-  backend: v2.9.0
-  api: v4.0.0
-Bump independently:
-  frontend breaking → v6.0.0
-  backend feature → v2.10.0
-  api unchanged → v4.0.0
-```
-### Umbrella Versioning
-**Use When**:
-- Medium/large team
-- Product-level milestones important
-- Services evolve at different rates
-**How It Works**:
-```yaml
-Product version + service versions:
-  Product v5.0.0:
-    frontend: v5.0.0
-    backend: v2.9.0
-    api: v4.0.0
-Version matrix tracks combinations
-```
-## Release Candidate Workflow
-**Three-Stage Pre-Release**:
-```mermaid
-graph LR
-    A[Alpha] -->|Stable API| B[Beta]
-    B -->|Production Ready| C[RC]
-    C -->|Validated| D[Production]
-```
-**Alpha** (Early Development):
-- Tag: v1.0.0-alpha.1, v1.0.0-alpha.2
-- Audience: Internal developers
-- Stability: Unstable (breaking changes OK)
-- Duration: Weeks to months
-**Beta** (Feature Complete):
-- Tag: v1.0.0-beta.1, v1.0.0-beta.2
-- Audience: Beta testers, QA team
-- Stability: Mostly stable
-- Duration: 2-6 weeks
-**RC** (Production Ready):
-- Tag: v1.0.0-rc.1, v1.0.0-rc.2
-- Audience: Pre-production, canary users
-- Stability: Production-ready
-- Duration: 1-2 weeks
-**Production**:
-- Tag: v1.0.0 (final)
-- Audience: All users
-- Stability: Stable
-## Living Documentation
-**Release Strategy Document**:
-```
-.specweave/docs/internal/delivery/release-strategy.md
-```
-**Contains**:
-- Repository overview
-- Versioning strategy (lockstep/independent/umbrella)
-- RC workflow
-- CI/CD integration
-- Changelog management
-- Hotfix strategy
-- Release checklist
-- DORA metrics
-- Decision history
-**Version Matrix** (Umbrella Releases):
-```
-.specweave/docs/internal/delivery/version-matrix.md
-```
-**Contains**:
-- Product version history
-- Service version mappings
-- Compatibility matrix
-- Breaking changes per release
-## Integration with Brownfield Analyzer
-**Automatic Release Pattern Detection**:
-When brownfield-analyzer skill runs, it:
-1. Detects repository structure
-2. Scans git tags for version patterns
-3. Analyzes CI/CD configurations
-4. Checks package manager files
-5. Identifies monorepo tools
-Then invokes release-strategy-advisor to:
-- Classify release strategy
-- Document in living docs
-- Suggest improvements
-**Example Output**:
-```markdown
-## Detected Release Strategy
-Type: Monorepo with independent versioning
-Evidence:
-  - lerna.json found (12 packages)
-  - Independent mode enabled
-  - Git tags: 145 total (per-package versioning)
-  - CI/CD: GitHub Actions + semantic-release
-  - Frequency: Weekly
-Recommendations:
-  ✓ Current strategy is solid
-  → Consider: Umbrella versioning for product milestones
-  → Add: Version matrix documentation
-```
-## Best Practices
-**Version Discipline**:
-- Always follow semantic versioning
-- Never skip version numbers
-- Use pre-release tags for testing
-- Document breaking changes clearly
-**Release Safety**:
-- Always use RC for major versions
-- Gradual rollout (canary → 10% → 25% → 50% → 100%)
-- Monitor for 1+ hour at each stage
-- Have rollback plan ready
-**Documentation**:
-- Update living docs after every release
-- Maintain version matrix for umbrella releases
-- Document lessons learned
-- Link to ADRs for major decisions
-**Testing**:
-- Run ALL tests before releasing
-- Validate cross-repo compatibility
-- Load test at 150% expected capacity
-- Security scan for every release
-## Configuration
-**In `.specweave/config.json`**:
-```json
-{
-  "release": {
-    "strategy": "independent",
-    "rcRequired": ["major"],
-    "gradualRollout": {
-      "canary": 0.05,
-      "wave1": 0.10,
-      "wave2": 0.25,
-      "wave3": 0.50,
-      "wave4": 1.00
-    },
-    "monitoring": {
-      "errorRateThreshold": 0.05,
-      "latencyThreshold": 2.0
-    }
-  }
-}
-```
-## Advanced Topics
-### Coordinated RC Across Repos
-```bash
-# Tag all repos with same RC iteration
-/sw-release:rc create-multi product-v3.0.0
-# Creates:
-# - frontend: v5.0.0-rc.1
-# - backend: v3.0.0-rc.1
-# - api-gateway: v4.0.0-rc.1
-# Test cross-service compatibility
-# Deploy all to staging
-# Run E2E tests
-# Found bugs → iterate
-/sw-release:rc iterate-multi product-v3.0.0-rc.1
-# Creates:
-# - frontend: v5.0.0-rc.2 (bug fixed)
-# - api-gateway: v4.0.0-rc.2 (bug fixed)
-# - backend: v3.0.0-rc.1 (unchanged)
-# All pass → promote
-/sw-release:rc promote-multi product-v3.0.0-rc.2
-```
-### Hotfix Workflow
-```bash
-# Production: v2.0.0
-# Critical bug discovered
-# 1. Create hotfix branch from tag
-git checkout -b hotfix/v2.0.1 v2.0.0
-# 2. Fix bug
-# ... make changes ...
-# 3. Fast-track testing
-npm test  # Critical tests only
-# 4. Release hotfix
-git tag v2.0.1
-git push origin v2.0.1
-# 5. Merge back to main
-git checkout main
-git merge hotfix/v2.0.1
-```
-## Troubleshooting
-**Issue**: Version conflicts detected
-```bash
-# Solution: Update dependencies to compatible versions
-# Then retry alignment
-```
-**Issue**: RC testing failed
-```bash
-# Solution: Fix issues, iterate to next RC
-/sw-release:rc iterate 1.0.0-rc.1
-```
-**Issue**: Canary deployment showing errors
-```bash
-# Solution: Rollback immediately
-/sw-release:rc rollback 1.0.0-rc.3
-```
-## Examples
-See `/examples` directory for:
-- Single-repo release workflow
-- Multi-repo coordinated release
-- Monorepo (Lerna) release
-- RC workflow with testing
-- Version matrix for umbrella releases
-## Related Documentation
-- **SpecWeave Core**: Main framework documentation
-- **Living Docs**: `.specweave/docs/internal/delivery/`
-- **ADRs**: Architecture decision records
-- **Release Strategy**: Project-specific strategy docs
-## Support
-- **Issues**: https://github.com/anton-abyzov/specweave/issues
-- **Discussions**: https://github.com/anton-abyzov/specweave/discussions
-- **Website**: https://verified-skill.com
----
-**Version**: 1.0.0
-**Author**: Anton Abyzov
-**License**: MIT

package/plugins/specweave-release/hooks/post-task-completion.sh DELETED Viewed

@@ -1,113 +0,0 @@
-#!/bin/bash
-# Post-Increment-Completion Hook - DORA Metrics Tracking
-#
-# Fires after: /sw:done completes
-# Purpose: Automatically track DORA metrics and update living docs dashboard
-#
-# Integration: plugins/specweave-release/hooks/hooks.json
-# CRITICAL (v0.25.2): NEVER use 'set -e' in hooks - causes Claude Code crashes
-# See: CLAUDE.md Section 9a (Hook Safety Checklist), ADR-0060 (Hook Performance)
-# v1.0.33 - Fixed: removed set -o pipefail for hook safety
-set +e  # CRITICAL: Never use set -e or pipefail in hooks (causes cascading failures)
-# Constants
-SPECWEAVE_ROOT="${SPECWEAVE_ROOT:-$(pwd)}"
-METRICS_DIR="${SPECWEAVE_ROOT}/.specweave/metrics"
-HISTORY_FILE="${METRICS_DIR}/dora-history.jsonl"
-DASHBOARD_FILE="${SPECWEAVE_ROOT}/.specweave/docs/internal/delivery/dora-dashboard.md"
-DORA_CALCULATOR="${SPECWEAVE_ROOT}/dist/src/metrics/dora-calculator.js"
-LATEST_FILE="${METRICS_DIR}/dora-latest.json"
-# Logging
-LOG_FILE="${SPECWEAVE_ROOT}/.specweave/logs/dora-tracking.log"
-mkdir -p "$(dirname "$LOG_FILE")"
-log() {
-  echo "[$(date '+%Y-%m-%d %H:%M:%S')] $*" | tee -a "$LOG_FILE"
-}
-log "🎯 Post-Increment-Completion Hook Triggered"
-# Check if DORA calculator exists
-if [[ ! -f "$DORA_CALCULATOR" ]]; then
-  log "⚠️  DORA calculator not found at $DORA_CALCULATOR"
-  log "   Run: npm run build"
-  exit 0  # Non-blocking
-fi
-# Check if GitHub token is available
-if [[ -z "${GITHUB_TOKEN:-}" ]]; then
-  log "⚠️  GITHUB_TOKEN not set. DORA metrics require GitHub API access."
-  log "   Set GITHUB_TOKEN in environment or .env file"
-  exit 0  # Non-blocking
-fi
-# Step 1: Calculate DORA metrics
-log "📊 Calculating DORA metrics..."
-if ! node "$DORA_CALCULATOR"; then
-  log "❌ Failed to calculate DORA metrics"
-  exit 0  # Non-blocking
-fi
-# Step 2: Append to history (JSONL format)
-log "💾 Appending metrics to history..."
-mkdir -p "$METRICS_DIR"
-if [[ -f "$LATEST_FILE" ]]; then
-  cat "$LATEST_FILE" >> "$HISTORY_FILE"
-  log "   ✓ Appended to $HISTORY_FILE"
-else
-  log "⚠️  Latest metrics file not found: $LATEST_FILE"
-fi
-# Step 3: Update living docs dashboard
-log "📝 Updating DORA dashboard..."
-DASHBOARD_GENERATOR="${SPECWEAVE_ROOT}/dist/plugins/specweave-release/lib/dashboard-generator.js"
-if [[ -f "$DASHBOARD_GENERATOR" ]]; then
-  if node "$DASHBOARD_GENERATOR"; then
-    log "   ✓ Dashboard updated: $DASHBOARD_FILE"
-  else
-    log "⚠️  Failed to update dashboard"
-  fi
-else
-  log "⚠️  Dashboard generator not found: $DASHBOARD_GENERATOR"
-  log "   Manual dashboard update required"
-fi
-# Step 4: Check for degradation (optional)
-log "🔍 Checking for metric degradation..."
-# Calculate 30-day average and compare with current
-# (This would be implemented in a TypeScript utility)
-# For now, we'll just log a reminder
-log "   ℹ️  Degradation detection: Manual review recommended"
-log "   See: $DASHBOARD_FILE for trends"
-# Step 5: Update main DORA metrics doc
-DORA_METRICS_DOC="${SPECWEAVE_ROOT}/.specweave/docs/internal/delivery/dora-metrics.md"
-if [[ -f "$DORA_METRICS_DOC" && -f "$LATEST_FILE" ]]; then
-  log "📄 Updating dora-metrics.md with latest values..."
-  # Extract current values from latest metrics
-  # (This is a simplified version - production would use jq for proper parsing)
-  TIMESTAMP=$(date '+%Y-%m-%d %H:%M UTC')
-  # Update "Last Calculated" timestamp
-  if command -v sed &> /dev/null; then
-    sed -i.bak "s/Last Calculated: .*/Last Calculated: $TIMESTAMP/" "$DORA_METRICS_DOC" 2>/dev/null || true
-    rm -f "${DORA_METRICS_DOC}.bak" 2>/dev/null || true
-    log "   ✓ Updated timestamp in dora-metrics.md"
-  fi
-fi
-log "✅ DORA metrics tracking complete!"
-log ""
-log "📊 Next steps:"
-log "   1. Review dashboard: $DASHBOARD_FILE"
-log "   2. Check trends: Are metrics improving?"
-log "   3. Take action: Address any degradation"
-log ""
-exit 0