Homebrew Upgrade Safety Policy

This rule applies to files matching the patterns above.

# Homebrew Upgrade Safety Policy

## Rule
Never run `brew upgrade` without first reviewing outdated packages. Pin version-sensitive tools. Backup databases before upgrading their formulae.

## Safe Upgrade Procedure
```bash
# Step 1: Update definitions
brew update

# Step 2: Review what will change
brew outdated

# Step 3: Upgrade by category
brew upgrade git gh neovim ripgrep    # CLI tools (safe)
brew upgrade volta node               # Runtime tools (test after)
# Do NOT upgrade databases without backup

# Step 4: Verify
brew doctor

# Step 5: Clean
brew cleanup --prune=30
```

## Database Upgrades (High Risk)
```bash
# BEFORE upgrading PostgreSQL:
pg_dumpall > ~/backup/pg_backup_$(date +%Y%m%d).sql
brew services stop postgresql@16
brew upgrade postgresql@16
brew services start postgresql@16
# Verify data integrity
```

## Version Pinning
```bash
# Pin critical versions
brew pin postgresql@16
brew pin python@3.12

# Check pinned packages
brew list --pinned

# Upgrade pinned packages explicitly when ready
brew unpin postgresql@16
brew upgrade postgresql@16
brew pin postgresql@16
```

## Good
```bash
brew outdated           # Review first
brew upgrade git gh     # Selective upgrade
```

## Bad
```bash
brew upgrade            # Upgrades EVERYTHING without review
brew upgrade postgresql # No backup taken first
```