What’s new

• bin/nibble-upgrade takes this site to a release: it snapshots the database, gates on the incoming release’s requirements, merges, installs dependencies and migrates. It runs on a workstation only.
• The upgrade offers to re-render the files you own that we generate, and reports what changed in our copy of anything you ejected.
• Updates in the sidebar: releases newer than the one you are running, what each one changed, and the command that takes it, with a count on the menu item that turns red when one of them is a security fix. A daily background check remembers the count; the page itself reads the file again when you open it, so no other page ever waits on it and there is nothing to set up. Nothing about your site is sent, and a switch on that screen stops the checks entirely.
• Settings a person changes in the control panel are kept in a settings table, separate from config/nibble.yml, which stays a file you edit by hand.

Changed

• The first administrator is made by asking, not by environment variables: bin/rails nibble:admin:create asks for a name, email address and password, and refuses a password the rules reject. ADMIN_EMAIL, ADMIN_PASSWORD and ADMIN_NAME no longer do anything — db:seed seeds roles and tells you to run the command.
• .nibble/install.yml now records the answers the install was given, which is what lets an upgrade re-render your settings without asking again. Installs made before this keep working; the upgrade says it cannot re-render them.