Upgrade from 0.16

Export each environment with 0.16 still installed.

penv generate --env development --out .env.development --allow-decrypt
penv generate --env production --out .env.production --allow-decrypt

--allow-decrypt writes sealed values as plaintext; without it generate skips them and the file is incomplete.

Move the files outside your repository. They are plaintext, and a later step deletes the tree they came from.

mkdir -p ~/penv-move
mv .env.development .env.production ~/penv-move/

Remove 0.16: the global launcher and its engine store.

npm rm -g @penvhq/launcher
rm -rf ~/.penv/engines ~/.penv/extensions

Install 1.0. Windows and npm: install the CLI.

curl -fsSL https://penv.cloud/install | sh

Write the schema from the development values.

cp ~/penv-move/.env.development .env
penv init
penv check

penv init writes .env.schema, inferring a type and sensitivity per key. Review the guesses with penv check; inference rules: from a .env file.

Push the first environment.

penv login
penv push

penv login signs you in; penv push creates the project with development and the environment it pushes, writes the @penv= header into .env.schema, sends us the values and deletes the value files it read.

Create and push each remaining environment. push reads .env and .env.<env>, so copy the file back first.

penv env new production
cp ~/penv-move/.env.production .env
penv push --env production

penv env new creates the environment; penv refuses a push to one that does not exist as no_such_environment. Console alternative: projects and environments.

Confirm every environment lists its keys, with penv ls or in the console. Until then your plaintext copies are the only source.

penv ls --env production

Delete the 0.16 leftovers, then the holding directory. Keep .penv/config.toml, which 1.0 writes.

rm -f penv.config.ts penv.schema.ts .penv/env.ts
rm -rf .penv/state ~/penv-move

Also remove any @env or #env path mapping from tsconfig.json or package.json.