Run the deploy job's smoke test by default
Build, test, deploy / site (push) Successful in 7m22s

After publishing, the job asks the live site for its version and fails
if it is not the commit it published. The test ran only when the
repository variable SITE_URL was set, and it was not, so a job that
published to a directory nothing serves passed. The address defaults to
https://pplus.scient.ing; SITE_URL still overrides it.
This commit is contained in:
alexm committed 2026-11-13 06:50:58 -05:00
1 parent 3c5097d9d0
commit d1955ad358
3 files changed
+7 -5

No files matched your search

+1
View File
@@ -35,6 +35,7 @@ No version has been tagged yet. What programs mean is pplus-core's, and its chan
### Fixed
- The deploy job publishes to `/srv/www/pplus`, the directory the site is served from, unless `SITE_SLUG` says otherwise. Its default was the repository's name, so the job published to `/srv/www/pplus-web` and the live site did not change.
- The deploy job's smoke test always runs on `main`: it asks the live site for its version after publishing, at `https://pplus.scient.ing` unless `SITE_URL` names another address. It ran only when that variable was set, and it was not.
- `docs/Caddyfile` served the page in place at a missing nested path, where its own files could not be found (a blank page). A missing page is sent to `/`; a missing file is a plain 404.
- Core's limits reach the site: no text in a pane, a link or a file ends in the engine's own error; a CSV export cannot start a spreadsheet formula; a framed Quarto view cannot make itself taller than 4,000px.
- From the library, the nav's Problems and Reference links opened nothing.