The browser terminal no longer saves your vault key
A custom vault key set with apivault config set vaultKey in the docs browser terminal's live mode now stays in memory. Until now it was saved in plain text in your browser's local storage, where it stayed after you closed the browser and could be read by any script running on the site.
The key is now cleared when the page reloads or closes, so you'll need to set it again after that. Any key saved by an earlier version is removed the next time you open a docs page, and it isn't restored.
config get, config set, and config delete work as before. Other terminal settings, such as run.env, are still saved in your browser. The apivault CLI on your computer isn't affected.
For more on custom vault keys, see the encryption documentation.