Skip to content

Add the secret type to env:add, and keep env validations in step on configure

Latest

Choose a tag to compare

@github-actions github-actions released this 19 Nov 06:48
Immutable release. Only release title and notes can be modified.

7.7.0 (2026-11-19)

Features

  • env:add accepts the secret type, from the prompt or with --type=secret. node ace env:add API_KEY my_secret --type=secret writes API_KEY: Env.schema.secret() to start/env.ts, and leaves the value out of .env.example. (#5157)
  • node ace configure <package> logs a warning for each env validation in start/env.ts that it keeps. Before, it kept them with no message, so a validation could disagree with the new package config. (ed6bb1f)

Bug fixes

  • node ace configure <package> --force replaces the env validations of the package in start/env.ts. Before, it kept them, so for example --store=redis for @adonisjs/session left SESSION_DRIVER without redis and the app failed to type-check. (4a83aee)

What's Changed

Full Changelog: v7.6.0...v7.7.0