Behind the scenes
- Release checks now stop a broken release. The release script's checks for the aircraft-shape data, and for the JavaScript in every page template and in Aerodrome's own script files, now actually stop a release when they fail. Before, they only printed a warning. Python files are syntax-checked too.
- A failed check leaves nothing half-updated, and re-running the release command repeats every check.
- Each release zip is checked to be exactly the source it was built from before it is staged, and exactly the tagged source (same files, same contents) before it is published.
- The overview PDF is rebuilt with the right tools on every release, a failed rebuild is reported, and rebuilding unchanged sources gives the identical file.
- The parts the installer scripts share (package detection and the permission rules) are now checked on every release to stay in sync.