v1.1.0

Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.

1.1.0 - 2026-01-21

Added

• Version support for Bitwarden keys: Save and manage multiple versions of keys

  • bw-save --name <version>: Save keys with a version name (e.g., "client-a", "v2", "backup")
  • bw-save --note <note>: Add a description to saved keys
  • bw-pull --name <version>: Pull a specific version
  • When multiple versions exist, bw-pull prompts to select which one to use

• bw-list command: View all saved keys in Bitwarden

  • Groups keys by project and environment
  • Shows version names, notes, and timestamps
  • Use --all to show all projects (not just current)

Fixed

• Support for base .env file (without environment suffix)
  • Keys for .env are now stored as DOTENV_PRIVATE_KEY (no suffix)
  • Properly detected and saved to Bitwarden as project/root

1.0.0 - 2026-01-21

Added

• init command: Initialize dotenvx encryption in Next.js and Vite projects

  • Auto-detects project type from package.json
  • Scans and displays all existing .env* files with encryption status
  • Shows variable preview for each environment file
  • Pre-selects unencrypted files for encryption
  • Installs @dotenvx/dotenvx package automatically
  • Updates package.json scripts with dotenvx run -- wrapper
  • Configures .gitignore and .vercelignore for security
  • Supports --yes flag for non-interactive mode (CI/CD)

• deploy command: Deploy encrypted environments to Vercel

  • Sets DOTENV_PRIVATE_KEY_<ENV> in Vercel environment variables
  • Supports production, preview, and development environments
  • Optional deployment trigger after key setup

• encrypt command: Encrypt environment variables

  • Encrypt entire .env.<environment> files
  • Add or update specific variables with -k and -v flags
  • Supports all environment types

• rotate command: Rotate encryption keys

  • Generates new encryption keys for selected environments
  • Re-encrypts all variables with new keys
  • Creates backup of existing keys before rotation
  • Supports --all flag to rotate all environments at once

• bw-save command: Save private keys to Bitwarden

  • Stores keys as secure notes in Bitwarden vault
  • Uses {package.json name}/{environment} naming pattern
  • Creates dedicated folder for organization
  • Updates existing entries on subsequent saves
  • Step-by-step setup instructions when Bitwarden CLI is not configured

• bw-pull command: Pull private keys from Bitwarden

  • Retrieves keys from Bitwarden vault
  • Supports filtering by environment
  • Merges with existing .env.keys file
  • Enables team onboarding and machine setup
  • Step-by-step setup instructions when Bitwarden CLI is not configured

• status command: Show encryption and deployment status

  • Displays project type and name
  • Lists all environment files with encryption status
  • Shows available private keys
  • Checks external tool availability (Vercel CLI, Bitwarden CLI)
  • Validates security configuration
  • Provides actionable recommendations

• Installation options:

  • Install from GitHub: npm install -g github:DmacMcgreg/dotenvx-deploy
  • Install via script: curl -fsSL .../install.sh | bash
  • Short alias: dxd

Security

• Private keys (.env.keys) are never committed to version control
• Encrypted environment files are safe to commit
• Bitwarden integration for secure key backup and sharing
• Key rotation support for security best practices

v1.0.0 - Initial Release

Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.

1.0.0 - 2026-01-21

Added

• init command: Initialize dotenvx encryption in Next.js and Vite projects

  • Auto-detects project type from package.json
  • Scans and displays all existing .env* files with encryption status
  • Shows variable preview for each environment file
  • Pre-selects unencrypted files for encryption
  • Installs @dotenvx/dotenvx package automatically
  • Updates package.json scripts with dotenvx run -- wrapper
  • Configures .gitignore and .vercelignore for security
  • Supports --yes flag for non-interactive mode (CI/CD)

• deploy command: Deploy encrypted environments to Vercel

  • Sets DOTENV_PRIVATE_KEY_<ENV> in Vercel environment variables
  • Supports production, preview, and development environments
  • Optional deployment trigger after key setup

• encrypt command: Encrypt environment variables

  • Encrypt entire .env.<environment> files
  • Add or update specific variables with -k and -v flags
  • Supports all environment types

• rotate command: Rotate encryption keys

  • Generates new encryption keys for selected environments
  • Re-encrypts all variables with new keys
  • Creates backup of existing keys before rotation
  • Supports --all flag to rotate all environments at once

• bw-save command: Save private keys to Bitwarden

  • Stores keys as secure notes in Bitwarden vault
  • Uses {package.json name}/{environment} naming pattern
  • Creates dedicated folder for organization
  • Updates existing entries on subsequent saves
  • Step-by-step setup instructions when Bitwarden CLI is not configured

• bw-pull command: Pull private keys from Bitwarden

  • Retrieves keys from Bitwarden vault
  • Supports filtering by environment
  • Merges with existing .env.keys file
  • Enables team onboarding and machine setup
  • Step-by-step setup instructions when Bitwarden CLI is not configured

• status command: Show encryption and deployment status

  • Displays project type and name
  • Lists all environment files with encryption status
  • Shows available private keys
  • Checks external tool availability (Vercel CLI, Bitwarden CLI)
  • Validates security configuration
  • Provides actionable recommendations

• Installation options:

  • Install from GitHub: npm install -g github:DmacMcgreg/dotenvx-deploy
  • Install via script: curl -fsSL .../install.sh | bash
  • Short alias: dxd

Security

• Private keys (.env.keys) are never committed to version control
• Encrypted environment files are safe to commit
• Bitwarden integration for secure key backup and sharing
• Key rotation support for security best practices