Environment Variable Versioning

Managing secrets and configuration safely is critical for production applications. LaunchVerse treats environment variables as immutable, versioned objects rather than simple key-value pairs.

Every time you modify an environment variable, LaunchVerse creates a new version of your environment configuration state.

Version History & Rollbacks

When a deployment fails due to a misconfigured secret (e.g., an invalid API key), you don't need to manually try to remember what the previous value was.

1. Navigate to your Project Settings > Environment Variables.
2. Click the History icon next to any modified variable.
3. You will see an audit log of who changed the value and when.
4. Click Restore on any previous version to instantly revert the value.

> [!CAUTION]

> Restoring a previous environment variable version does not automatically redeploy your application. You must trigger a new deployment to inject the restored value into your running container.

Environment Scoping

You can scope environment variables to specific deployment contexts:

1. Production: Injected only into your main production deployments.
2. Preview: Injected into PR Preview environments.
3. Development: Available for local development (pulled via the API).

Bulk Imports

If you are migrating from another platform or have a .env file locally, you can use the Bulk Import tool in the dashboard to paste raw .env contents. LaunchVerse will parse the keys and values, encrypt them, and add them to your project seamlessly.