# Version Control in Hush

Hush implements a version control system that ensures developers avoid conflicts from using different versions.

The version control system in Hush works on three levels:

1. Secret Versioning: Each secret in AWS SecretsManager is automatically versioned
2. Local Version Tracking: The .hushrc.json file tracks local versions
3. Conflict Prevention: Automatic checks before push operations

Hush automatically creates a .hushrc.json file in your project directory:

{
  "hush-project-dev": {
    "version": 5
  },
  "hush-project-prod": {
    "version": 12
  },
  "hush-api-keys": {
    "version": 3
  }
}

Note:

• The .hushrc.json file is automatically updated during pull operations
• The .hushrc.json file is used for conflict checking during push operations

With every hush push, the system goes through the following process:

1. Retrieve Current Version: Loads the current version from AWS SecretsManager
2. Check Local Version: Compares with the version in .hushrc.json
3. Conflict Detection: Warns about conflicts and prevents unintended overwrites
4. Version Increment: Automatically increases the version number by 1
5. Update Local Tracking: Updates the .hushrc.json file

# Current version in AWS: 5
# Local version in .hushrc.json: 3

hush push my-project .env
# ⚠️ Warning: Current version (5) is greater than your current version (3)
# ⚠️ Use "hush pull" to pull the latest version first

# Solution 1: Pull latest version
hush pull my-project .env
# Local version is updated to 5

hush push my-project .env
# ✅ Success! Version is incremented to 6

# Solution 2: Use force flag (only when sure)
hush push my-project .env --force
# ⚠️ May overwrite newer changes!

1. Read Local File: Analyzes the current .env file
2. Retrieve Remote Version: Loads the latest version from AWS
3. Detect Changes: Compares local and remote versions
4. Request Confirmation: Shows changes before overwriting
5. Update Version: Updates .hushrc.json after successful pull