Build, test, deploy / site (push) Successful in 6m43s
The deploy job's directory under /srv/www defaulted to the repository's name. This repository is pplus-web and the site is served from /srv/www/pplus, so the first job that passed here published to /srv/www/pplus-web and the live site stayed as it was. The default is pplus; SITE_SLUG still overrides it.
57 lines
6.0 KiB
Markdown
57 lines
6.0 KiB
Markdown
# Changelog
|
|
|
|
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
|
|
No version has been tagged yet. What programs mean is pplus-core's, and its changelog has those changes; this one says what changed on the site.
|
|
|
|
## [Unreleased]
|
|
|
|
### Changed
|
|
|
|
- The site runs on pplus-core for Mojo 1.2.0: generated Mojo the real compiler accepts and that prints what the pseudo prints, 18 prover rules that proved what a run breaks closed, and the interpreter audit's fixes. The pin is consistent again: a fresh clone's tests pass.
|
|
- The deployed site carries its license and the third-party notices (`LICENSE.md`, `NOTICE.md`, `THIRD_PARTY.md`).
|
|
- Compile & run asks before the first send to godbolt.org, builds every program one stated way (`--target-cpu x86-64-v3 --fp-mode contract=off`, shown on each compile), and shows the kept answer when the source, the input and the level are unchanged.
|
|
- The site serves its own fonts; nothing is asked of any other server except godbolt.org by Compile & run. A Content-Security-Policy and the other security headers are in `docs/Caddyfile`.
|
|
- The copy says what the site holds and no more: what runs in the browser and what does not, that the Hardware area is a model machine, and what "verified" means.
|
|
- A shared link never saves over the reader's own work on the same problem.
|
|
- Below 700px a workspace shows one part at a time; every page has a main landmark and a heading, and the contrast findings are fixed.
|
|
- The Quarto extension's syntax definitions state their license as Apache-2.0 (they said MIT), and `THIRD_PARTY.md` says that the stylesheets and syntax definitions that came from the course are under this repository's copyright and license.
|
|
|
|
- The deploy job is light: it runs the site's tests and core's `mojo-status-strict` at the pinned commit, then publishes. It no longer runs core's own tests (15 to 22 minutes on the deploy server, where they also failed for want of a C compiler and for the server's speed, so the site was not published). Core's tests and everything that builds Mojo are core's gate, on a runner of its own; run `pixi run core-test` before moving the pointer. `docs/deploy.md` and the workflow describe the runner as it is, a new container for every job, not a host shell.
|
|
- The site runs on a pplus-core whose gate does not depend on the machine: a pinned C compiler for the Mojo compiler to link with, a Dafny that starts without ICU, and a prover whose time on the clock is the caller's (the Prove tab keeps its 3 seconds).
|
|
|
|
### Added
|
|
|
|
- `THIRD_PARTY.md`, with the copyright notice of every package bundled into the editor, and a test that holds it to the bundle, the copied stylesheets, the fonts and the locks.
|
|
- The Apache License 2.0, a NOTICE, contributing rules, a security policy, a code of conduct, and a citation file.
|
|
- A footer with the license, the notices, the disclaimer about Modular, the build's commit, and "What this site stores and sends", each statement held to the code by a test.
|
|
- `pixi run caddy-check` serves an assembled site with a real Caddy under `docs/Caddyfile` and holds its headers, caching and missing-path answers; `pixi run release-check` says whether the three repositories' pointers line up; `site/build.json` names the three commits a site was built from.
|
|
- Tests for the copy, for every badge having a row in core's `docs/trust.md`, for what the site stores and sends, for load, accessibility and narrow screens.
|
|
|
|
### 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.
|
|
- `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.
|
|
- Open in Hardware on a large compiled function made work whose share link the app then refused to open (its setup was 2.5 MB); core writes the function's data compactly now, and a link for it opens.
|
|
- A Quarto page's Mojo run, and the page checker, build Mojo as the app does.
|
|
- `pixi run check-pages` read only shortcode names with one hyphen, so it skipped every `pplus-hw-<view>` shortcode: a missing file or a misspelled view went unreported.
|
|
- With `pplus-strict: true`, a program with `EXPECT` lines that does not run at all stops the render; it was only a warning.
|
|
- `quarto/README.md` is corrected against the extension: `follow` belongs to the stepper only, the defaults and limits of `height` and `max`, what a non-HTML format gets, what `check-pages` runs, and what `quarto-export` writes.
|
|
- From core: brackets that each hold a long chain are one `too-deep` error in the pseudo pane; they ended in the engine's own stack error.
|
|
|
|
## [0.1.0] - 2026-10-06
|
|
|
|
The first version of the site, as `main` holds it. Never tagged.
|
|
|
|
### Added
|
|
|
|
- Three areas: the Bridge (lingo, matho, pseudo and speco, kept in step as you type, with Mojo generated from the pseudo), the Developer area (Mojo with the checker, a Run view of every step, a fuzzer and Compile & run on godbolt.org), and the Hardware area (the code beside a board of registers, memory, caches, the pipeline and the out-of-order core).
|
|
- The library page (`#/library`): every verified routine with how its checks ended, its pseudo, cases, references and proof, and a way to open it in the Bridge.
|
|
- A catalog of worked problems, share links that carry the whole state, embeds, and a Quarto extension that renders the views into a page.
|
|
- A static deployment: `pixi run site` and `pixi run deploy`, a Caddy site block, and a CI workflow.
|
|
|
|
### Changed
|
|
|
|
- The engines live in pplus-core, the submodule `core/`; the site keeps its session over core's `Workspace`.
|