Skip to content
Menu

Changelog#

All notable changes to Squire are recorded here. The format follows Keep a Changelog; the project follows Semantic Versioning once 1.0 is out.

[Unreleased]#

  • Changed: deploy/ requires PROCTOR ^0.16 (was ^0.15, which does not allow 0.16), whose ci-pipelines check no longer asks for a GitHub workflow (D-069).
  • Changed: the dev dependency Pinstripe is ^0.4 (was ^0.3, which does not allow 0.4.0); 0.4.0 adds two opt-in Rector presets and changes no rule this repo uses.
  • Changed: Squire's own deploy/ takes the 0.11.1 templates (squire update): the fallback base names its line (8.4r5), the release script, the parity scripts with their deprecation note, and the compose and env examples (D-113 step 1).
  • Changed: CI pins Preflight 0.9.0 (components and the a11y checker copy).
  • CI: the GitHub workflow calls Preflight 0.9.0's reusable workflow (commit fb73b53), the release the GitLab pipeline pins.

0.11.1 (2026-11-13)#

  • Fixed: the fallback base follows the app's PHP line: an 8.5r3 app's fallback is built on php 8.5.12, an 8.4r5 app's stays on 8.4.27 (D-113).

0.11.0 (2026-11-13)#

  • Changed: the MySQL upgrade guide now says plainly that the supported path ends at MySQL 8.4 LTS; 9.7 LTS is a later hop, revisited once Citadel has reached 8.4 and PHP and Laravel driver support for 9.7 is checked (SQUIRE-14).
  • Added: squire site build runs docs.json block commands from the installed library and copies the pin's files into the build (ADR-0023).
  • Fixed: squire site build keeps a Windows drive letter in the output path.
  • Added: squire site build --check compares a fresh build with the committed output and writes nothing (ADR-0023).
  • Added: squire site build exports a pinned library tag and builds its docs site and agent-ready files with a sha256 manifest (ADR-0023).
  • Added: src/Site generator drivers, the first piece of squire site build (ADR-0023).
  • Added: src/Site pin parsing and tag export for the site build (ADR-0023).
  • Added: squire facts --snapshot rebuilds .squire/facts.json offline from the CREED policy and ADVISOR project data in vendor, with the first three regions (cast-md, php-supported-md, preflight-pin).
  • Fixed: the GitHub contract legs (contract-parity-sh, contract-parity-pwsh, and contract-image on linux/amd64 and linux/arm64) failed since squire init stopped writing the parity group by default (D-095): the fixture had no .squire/Dockerfile or .env.squire.example. The workflow and scripts/contract-image.sh now ask for it with --only=release,parity.
  • Added: squire facts fills marked regions from a committed .squire/facts.json, and squire facts --check fails CI on drift (D-109; the snapshot writer comes next).

0.10.9 (2026-11-11)#

  • Changed: the parity kit's HAProxy pin moves to the current haproxy:3.0-alpine digest (sha256:1c15903c50d5510dcc01de755049e7015a6dd3f35bb2dc4582e888116cb71d8f) in docker-compose.squire.yml, for the common and vue kits and Squire's own deploy layer. Run squire update to take it.
  • Changed: new apps start on the Citadel PHP line 8.5r3 and record it as php in .squire.json; existing apps without the key stay on 8.4r5, and squire update never moves them. squire init --php <line> picks one.
  • Added: the {{PHP_LINE}} token and a manifest php key (D-090, slice A). Templates say {{PHP_LINE}} where they named the Citadel PHP image line, Catalog::content() fills it (default 8.4r5), and .squire.json can record php. Nothing changes for any app yet: every rendered file still says 8.4r5.
  • Changed: squire update --only help calls the parity group opt-in, not deprecated.
  • Changed: a fresh squire init writes only the release group; the parity group is opt-in (--only release,parity), because Parity runs the app locally now (D-095). An app with a .squire.json keeps its recorded groups, and init points at parity init --from-squire when the group is not in play. The drift check in the ADVISOR module follows the recorded groups too.
  • Added: a GitLab Release for every tag. On a tag, the new gitlab-release job posts the tag's CHANGELOG.md section to git.wayne.edu's releases API with the job's own token: 201 is a new release, 409 (one already exists) is left as it is, and anything else fails the job. It never creates, moves or deletes a tag. The notes come from scripts/release-notes.sh TAG [CHANGELOG], which the GitHub release workflow now calls too, so both homes cut the same notes; it drops the section's blank edges and fails loudly when the section is missing or empty (ReleaseNotesScriptTest). OPEN_QUESTIONS no longer lists the GitLab release job as not built.
  • Changed: docs tables fit their column. A table of three or more columns becomes one card per row when the table itself is 560 px wide or less (a phone, or a tablet beside the sidebar; a container query, not a screen width): the first cell names the card and every other value sits under its column's header, so the column that explains everything is no longer off screen behind a sideways scroll. The builder writes each body cell's header text into a data-label attribute, and puts a <wbr> in long code tokens in cells (after slashes, underscores, commas, colons and a dot before a letter, and every 16 characters of a digest) so a path or digest wraps at a seam instead of pushing the table past the page; the first column of a wider table keeps its names whole. Measured on Squire's 34 docs tables: none overflows from 390 px up (15 did at 800 px, and one ran to 1100 px on a desktop). Tables of two columns keep their grid, the header row stays in the page for screen readers, and every site on the kit takes it with its next docs build. Squire's own theme stitches the cards apart with its dashed rule and lets a long header wrap.
  • Added: the release script fetches PROCTOR when --no-dev left it out, so the deploy gate runs on Citadel instead of reporting itself missing on every release. When no PROCTOR is found (SQUIRE_PROCTOR_BIN, vendor/bin/proctor, then PATH), it installs the version the app's composer.lock pins under packages-dev with composer create-project waynestate/proctor <dir> <version> --no-dev --no-scripts --no-plugins into .cache/squire/proctor/<version>, once per version, and gates the release with the same PROCTOR CI ran. A failed fetch leaves nothing behind and is a warning (a stop under SQUIRE_PROCTOR=enforce); SQUIRE_PROCTOR_FETCH=0 turns it off, and SQUIRE_CACHE_DIR=off skips it. Run squire update to take the new scripts/release.sh and .env.squire.example.
  • Docs: OPEN_QUESTIONS, the README and the contributing page no longer say PROCTOR has no published phar (each of its GitLab Releases carries one since 0.6.0), and say the image contract has run by hand on Citadel's own citadel/php-apache:8.5r3.
  • Site: on a phone the packing list's PACKED stamp no longer covers a long file name (deployments/001-first-release.sh, scripts/release.sh), the toast after packing spans the screen instead of folding into a narrow ribbon over the page, and an option such as --force in running text no longer splits at its hyphens at 320 px.
  • CI pins Preflight 0.8.0.
  • Fixed: The parity kit's HAProxy reads the engine's nameserver (parse-resolv-conf) instead of Docker's fixed 127.0.0.11, so Podman no longer drops the app a minute after up (503). Same fix as Parity 64bf3e8.
  • Added: scripts/contract-image.sh --base-image=REF runs the image contract on an image already on your machine instead of the fallback, above all Citadel's own citadel/php-apache:8.5r3 (which parity image get loads). It never pulls, and stops when the image is missing or built for another platform. The three checks that only the base image decides (the Apache server directives and the entrypoint's /run/secrets loading) print GAP: lines there instead of failing; on the fallback they still fail. The first run on Citadel's image (2026-11-10) passed every check the kit owns and showed three gaps, recorded on the Proof and Image hardening pages.
  • Added: the release script installs the frontend from a yarn.lock too, through corepack, as Citadel's images ship Yarn: Yarn 1 with corepack yarn install --frozen-lockfile --non-interactive --ignore-scripts, Yarn 2 and later (a lock with a __metadata: block) with corepack yarn install --immutable --mode=skip-build, then corepack yarn run build. A Yarn 2 lock needs "packageManager": "yarn@..." in package.json; without it the release stops before installing and says so, since corepack would hand the lock to Yarn 1. SQUIRE_NPM_REBUILD works with both (yarn rebuild, or npm rebuild for Yarn 1). Until now a committed yarn.lock stopped the release with "commit a lock file" (two apps in the 82-app proof). Doctor rule S12 accepts either Yarn install as installing from the lock. Run squire update to take the new scripts/release.sh.
  • Fixed: scripts\parity.ps1 on Windows PowerShell 5.1. There a native command's redirected stderr is a terminating error under $ErrorActionPreference = 'Stop', so up with no base image on the machine died on a raw NativeCommandError instead of saying the image is missing, and pin could die the same way. The quiet docker calls now run through Invoke-NativeQuiet, and the script's own errors print one plain parity: ... line and exit 1 instead of a Write-Error record. First run on 5.1 itself: up -Fallback, up on citadel/php-apache:8.5r3, status, pin, down and reset all passed. Run squire update to take the new script.
  • Changed: parity up (both twins) warns while SQUIRE_PROJECT is the default squire-app, and .env.squire.example says why: apps on one name are one compose project, sharing the database and the logs volume that records which deployments/ files already ran, so a second app's first release is skipped and its health check only says vendor/autoload.php is missing. Found on the PowerShell 5.1 run, where a fixture inherited another app's release record. A new Troubleshooting entry names the symptom. Run squire update to take the new scripts.
  • Changed: the image contract runs the app containers with the kit's compose file's least privilege (--cap-drop=ALL, the same seven capabilities back, no-new-privileges, 256 processes, 512 MB), and a test fails when the two disagree. The baked-code container starts through the image's own entrypoint, as Citadel starts it, instead of Apache alone.

0.10.8 (2026-11-10)#

  • Docs: the Local parity guide points at Preflight 0.6.0's mysql56-migrate component and PROCTOR's mysql56-ci check, the CI side of the same MySQL 5.6.51 pin (D-078).
  • Changed: the Oracle image tag jobs build linux/amd64 again, natively on a runner tagged amd64, while linux/arm64 stays on the default runner; the new oracle-images-manifest job stitches both halves into one manifest list per image. SQUIRE_BUILD_AMD64 now defaults to "1"; "0" publishes linux/arm64 only. Only the two amd64 jobs carry the amd64 tag.
  • Changed: the deploy layer requires PROCTOR ^0.15 (locked 0.15.0, was ^0.12): 0.13 checks the release cooldown against the CREED policy, 0.14 adds script-pair and 0.15 adds mysql56-ci; all only warn, nothing breaks.
  • Changed: the deploy layer requires PROCTOR ^0.12 (locked 0.12.0, was ^0.11): two new warning-only checks, nothing breaks.
  • Changed: Renovate proposes only patch and digest updates for the two PHP 8.4 base images (the Oracle parity image and the fallback base), so it stops opening 8.5 bumps the image tests reject.
  • Docs: the ADVISOR guide and README say to list SquireModule in a manifest of your own and point ADVISOR_MODULES_FILE at it; ADVISOR never reads an app's modules.json.
  • Site: the front page's stale facts are current (Squire 0.10.7 on Packagist, the bag holds 25 files, the full squire init output for laravel, the whole S8 message, S78 on the rule list; the README's packing-list image says 25 files too).
  • Fixed: squire update reports a file current, and records it, when an app's edit already matches the new template byte for byte (an edit taken upstream), instead of reporting drift.

0.10.7 (2026-11-10)#

  • Added: the kit ships a .gitattributes that pins line endings (LF for shell scripts, .conf files and Dockerfiles, CRLF for PowerShell and batch files), so a deploy layer in its own folder clears PROCTOR's gitattributes-eol and crlf-deploy-script warnings. An app that has its own .gitattributes keeps it: Squire never writes over it.
  • Changed: doctor rule S8 names every .gitattributes line to add (shell scripts, .conf files, Dockerfiles and PowerShell), the same pins PROCTOR's gitattributes-eol check wants, so following the doctor clears PROCTOR too.
  • Changed: the GitHub workflow calls Preflight 0.5.0 (was 0.1.4), now that GitHub's copy of Preflight has the tag. MAINTAINING.md says the arm64 contract leg blocks, as it has since it passed on 2026-11-08.

0.10.6 (2026-11-10)#

  • Fixed: the docs builder, agent-ready generator, template export and doctor scans walk folders with scandir, because PHP's recursive directory iterator lists only some files on Docker Desktop mounts (22 of Preflight's 28 guide pages went missing).
  • Site: assets/stack-env.js knows Parity, so a pre-production page links Parity's pre-production site and a dev page links its local site/ folder. Until now Parity, of all parts, was the one link that ignored its environment.
  • Site: Parity is out; the party list links its site.
  • Changed: requires waynestate/pinstripe ^0.3 and waynestate/advisor ^0.3.
  • Docs: the 0.10.5 tag published the Oracle images, the first tag to do so: both flavors for PHP 8.3, 8.4 and 8.5, linux/arm64 only. The Oracle guide and MAINTAINING.md (What each tag published) list each image's list digest, for example squire-oracle-sail:8.4-0.10.5@sha256:3d942883ea31c802e2a958542697941c6bff4b36989931e12e2c24289b690a87 and squire-oracle-parity:8.4-0.10.5@sha256:531b22047eedfd4e8bceee4583cbce2d0aac3129d27afdae97aec8b22bb54367. amd64 hosts still build locally until SQUIRE_BUILD_AMD64=1.
  • Docs: US spelling in the README and OPEN_QUESTIONS.md (flavors).

0.10.5 (2026-11-09)#

  • Deprecated: the parity group (docker-compose.squire.yml, .squire/, .env.squire.example, scripts/parity.sh and scripts/parity.ps1). Parity, the stack's own tool, runs Citadel on your computer now: one program for Windows, macOS and Linux, for any app, with or without Squire, on Docker or Podman, with Citadel's PHP image, Citadel's proxy and MySQL 5.6. parity init --from-squire carries the kit's settings over and deletes nothing. The kit still works and nothing is removed in this release. It goes no sooner than two minor releases and 60 days from now (the stack's ADR-0022): Squire 0.12.0, and not before 2027-01-08. The portable image files stay with Squire and move to a group of their own. The local parity guide, the README, the commands, files, quick start, doctor and troubleshooting pages and the front page say so and recommend Parity. Squire still carries the bag to Citadel; it just stops pretending to be Citadel at home.
  • Added: squire init (not --check) and squire update end with one line that points at Parity whenever the parity group is in play, and their --only help marks the group deprecated. squire doctor adds an S35 info finding that says the same when the kit is there; without it, the S35 info line now says how to start with Parity instead of suggesting init --only=parity. No exit code changes. Tests pin the line, where it prints, and where it does not.
  • Changed: the oracle-images tag jobs publish linux/arm64 only, both flavors, PHP 8.3, 8.4 and 8.5: Apple silicon and arm64 Linux hosts can pull them, and amd64 users, Citadel-shaped hosts included, build locally with scripts/oracle-image-build.sh. The CI runner is arm64 and cannot run amd64 binaries, so the amd64 legs used to fail every tag pipeline. One switch turns amd64 back on: the CI variable SQUIRE_BUILD_AMD64=1 (default 0, in the .oracle-platforms block both Oracle jobs extend), once the runner host has qemu-user-static. scripts/oracle-image-publish.sh takes --platforms (amd64, arm64 or both; both is still the default by hand), puts only what it built into the manifest list, and refuses an unknown platform with exit 2. MAINTAINING.md records what each tag published.
  • Docs: Parity joins the party. The README cast, the front page's party roster and the docs overview list Parity right after Squire, with its spirit-level mark, linking its repository until its site is live. The front page's parity section gets a handoff card, and Parity's level tilts in and finds level when it scrolls into view (rotation only, and only without a reduced-motion request).
  • Fixed: every PHP 8.5 Oracle image build (both flavors, every architecture, in CI and with scripts/oracle-image-build.sh --php 8.5) failed in images/oracle/install-oracle.sh. PHP 8.5's php --ini prints the ini scan directory in double quotes (8.4 and older print it bare), and the script wrote zz-oci8.ini into a path with the quotes in it, a folder that does not exist. It strips the quotes now, fails by name if the folder is missing, and a test pins both.

0.10.4 (2026-11-09)#

  • Fixed: the Sail flavor of the oracle-images CI jobs failed before it built anything, on every tag since 0.6.0: scripts/oracle-image-publish.sh ran buildah from docker://composer:2.11.1@sha256:..., and buildah's docker:// transport refuses a tag and a digest together (invalid reference format). The script now names the image in full without the prefix (docker.io/library/composer:2.11.1@sha256:..., same digest), and a test fails on a tag and a digest after docker:// in either Oracle script.
  • Fixed: every linux/arm64 Oracle image build (both flavors, in CI and with scripts/oracle-image-build.sh on an arm64 machine) failed in images/oracle/install-oracle.sh. The arm64 Instant Client 19.32 Basic Light and SDK zips share their META-INF/ signing files, so the second unzip stopped to ask whether to replace them, read end of input and failed. The SDK now unpacks with unzip -n (Basic Light's files always win), the unused META-INF/ is removed, and a test pins it. The amd64 21.7 zips share no files, so amd64 builds were never affected.
  • Fixed: when a build dies because the runner cannot run the other architecture, the publish script now says so plainly; it looked for Exec format error, but buildah prints it in lower case, so the job showed only a raw log tail. It also builds the runner's own architecture first, so a dry run proves that half before it stops.
  • Docs: MAINTAINING.md, OPEN_QUESTIONS.md, the README and the Oracle guide say what is true today: no tag has published the Oracle images yet, because the only CI runner is linux/arm64, cannot run linux/amd64 binaries, and its jobs are not privileged to register qemu emulation themselves. Build the images locally with scripts/oracle-image-build.sh until the runner host gets emulation or an amd64 runner joins.

0.10.3 (2026-11-09)#

  • Changed: the wayneui-copies and composer-ci CI jobs pin composer:2.11.1 by its multi-arch list digest (sha256:8de2184c...), as the kit already does, instead of the bare tag.
  • Changed: the deploy layer requires CREED ^0.1.8, HELMET ^1.3 and PROCTOR ^0.11 (locked 0.1.8, 1.3.0 and 0.11.1; were ^0.1, ^1.0 and ^0.8), and the Pinstripe dev dependency is ^0.1.4 (locked 0.1.4, was 0.1.0). proctor check on deploy/ still passes.
  • Changed: CI pins the Preflight components to 0.5.0 (was 0.4.0). The composer-audit job drops its own image input, since 0.5.0's default is composer:2.11.1 by digest, and the PROCTOR job now keeps proctor.json for Rollcall. The a11y checker is the same at 0.5.0, so tools/a11y/ does not change.
  • Changed: the kit's templates say in plain words what each comment used to point at with an internal item ID (the opcache switch, the web's disable_functions list, secrets as files, the digest pins, the npm install-script escape hatch, the Oracle check), so an app's copied files no longer cite numbers it cannot look up. Comments only: no setting, default or behavior changes. Run squire update to take them; until then init --check reports those files as outdated, as it does for any kit change. Squire's own deploy/ takes them in this release, and the docs, tests, scripts and CI comments drop the same IDs.
  • Docs: MAINTAINING.md names the maintainer as a role (the stack maintainer), reached through an issue on git.wayne.edu.

0.10.2 (2026-11-09)#

  • Fixed: the kit's Dockerfiles name every image in full (docker.io/library/php:..., docker.io/library/node:..., docker.io/library/composer:..., tags and digests unchanged), so Buildah and Podman build them with short-name mode enforcing; Buildah refused the fallback base's COPY --from=composer:2.11.1@sha256:... outright. The fallback base's Composer now comes from a FROM ${COMPOSER_IMAGE} AS composer stage, so all three images (PHP_IMAGE, NODE_IMAGE, COMPOSER_IMAGE) are build arguments a proxy or mirror can swap; Image hardening in the docs has the Dependency Proxy recipe. The Oracle parity image's bases in images/oracle/php-images.txt are named in full too. A test fails on a short name in any of the kit's Dockerfiles.
  • Changed: the portable image drops node_modules/ after the frontend build, in the same step, so no layer keeps it; the image ships the built assets and no role runs Node. --build-arg SQUIRE_KEEP_NODE_MODULES=1 keeps it for an app that reads it at run time.
  • Changed: raw PHP apps get SameSite=Lax session cookies. The kit's php.ini sets session.cookie_samesite = Lax (it was empty), next to the session.cookie_httponly = 1 and session.cookie_secure = 1 it already set, so an app that never calls helmet_boot() sends a session cookie SESAME 0.7.0 does not warn about. Lax still sends the cookie on a top-level GET from another site (a CAS ticket, an OIDC code), not on a cross-site POST. Applies wherever the kit's php.ini is used (local parity, the portable image); on Citadel the platform's php.ini decides. A test pins the three settings and reads them back through PHP.
  • Changed: Squire's own deploy/ is on the 0.10.2 kit (the new php.ini, fallback base and portable image).

0.10.1 (2026-11-09)#

  • Changed: the kit's Composer moves from 2.10.3 to 2.11.1 (composer:2.11.1@sha256:8de2184c6de224f4689e8f80ed5f5edaf0030b6b8b7839a22a2bcb6722ac87d0, the multi-arch list) in the fallback base, the Oracle parity image, the contract and Oracle build scripts, CI and the Docker-only commands in the docs. 2.10 is no longer maintained, and 2.11.0 fixed GHSA-c968-33g3-wh7p (package names in installed.json could escape the vendor directory) and GHSA-fm2w-xgf2-f9fh (inline repository HTTP headers could be written into composer.lock). 2.11 drops the source-fallback setting, which Squire never used, and the new policy.cooldown stays off by default. Run squire update to take the new fallback base.
  • Changed: the deploy kit is Squire 0.10.0 (was 0.8.0): release.sh gains the release env guard (a Laravel release stops when APP_KEY is unset or APP_DEBUG is on in production).
  • Fixed: scripts/a11y.ps1 works on a Windows checkout with CRLF line endings; it strips the carriage returns from the shell command it hands to Docker, which sh rejected with a syntax error.

0.10.0 (2026-11-09)#

  • Added: the MySQL upgrade path guide (docs/guides/mysql-upgrade-path.md): 5.6.51 to 5.7 to 8.0 to 8.4 LTS one series at a time, with the checker to run, the backup (a dump made with the source's own client) and the driver and Laravel floor for each hop, and a rollback for each hop, since MySQL cannot downgrade in place across series. With it, scripts/mysql-preupgrade-checks.sql, a read-only script for a copy of the data that lists old temporal columns, names of 64 characters or more, tables not on utf8mb4_unicode_ci, and what 8.4 rejects (foreign keys on a non-unique or partial key, AUTO_INCREMENT on FLOAT or DOUBLE); a test refuses any statement that is not a SELECT or SET SESSION.
  • Docs: MAINTAINING.md records the Code Quality check (SQUIRE-33): the pipeline uploads PROCTOR's findings as a codequality report artifact and never uses GitLab's deprecated CodeClimate template, so its planned removal changes nothing; OPEN_QUESTIONS.md names the 0.4.0 Preflight pin and the queue worker that is still missing on Citadel.
  • Changed: the GitHub workflows pin every action by its commit SHA with the version in a comment (actions/checkout v4.4.0, shivammathur/setup-php 2.40.0, docker/setup-qemu-action v3.7.0, docker/setup-buildx-action v3.12.0, the same code their moving tags ran), so a moved tag cannot change what CI runs; a test fails on any tag pin.
  • Fixed: the generated changelog page links relative paths with GitHub's blob path when the source is GitHub, and leaves links inside code spans and fenced code alone.
  • Fixed: the docs kit keeps a heading's "#" permalink on the line of its last word (the builder wraps the pair in .docs-heading-tail), so it never wraps onto a line of its own. On phones, narrow windows and touch screens, and for the page title at every width, the "#" takes no room and no tap area and shows on keyboard focus. A heading word too long for its line breaks or hyphenates instead of widening the page.
  • Added: the docs kit's "On this page" list marks the section in view with aria-current="true" and is-current (an accent bar on the list's rule, light and dark); a clicked entry stays marked through a smooth jump instead of flashing every section it passes. It is a docs.js enhancement that never scrolls, so without JavaScript the page reads as before. Resync the kit and builder with --sync-to to take both.
  • Fixed: agent-ready reads the project name from a README title inside a centered block or an <h1>, then the Composer package name, so a site built in place is no longer titled "# ." (Sourdough's was).

0.9.0 (2026-11-08)#

  • Changed: the release script refuses a Laravel release when APP_KEY is unset or APP_DEBUG is true in production, and warns when APP_ENV is not production (Sourdough practice 4.14).
  • Changed: CI pins the Preflight components to 0.4.0 (the proctor job clones the full history, so the override-approver check can read git blame).
  • Changed: the release gate passes --php-runtime (SQUIRE_PHP_RUNTIME, default auto: the php that runs release.sh, which is the one serving the app), so the deploy path grades the runtime for PROCTOR's unpatched check.
  • Changed: the GitHub workflow's arm64 image leg and pwsh parity leg block the run (no continue-on-error): both passed in five pushes in a row on 2026-11-08.

0.8.0 (2026-11-08)#

  • Added: the portable image (.squire/portable.Dockerfile, ADR-0010), for OpenShift, Coolify and raw Docker. One image with the code baked in runs as web, worker (queue:work --tries=3 --max-time=3600 --sleep=3), scheduler (schedule:work) or migrate, picked by argument or SQUIRE_ROLE, as USER 10001:0 with group-0 writable folders (any arbitrary UID in group 0 runs it), Apache on 8080 (SQUIRE_PORT, else PORT), logs to stdout and stderr, and a graceful stop on SIGTERM (WELD W8, W13). The compose file's new portable profile runs the four roles; a plain up is unchanged. The Citadel mirror (.squire/Dockerfile, port 80) does not change. Run squire update to take the five new files.
  • Added: health.php reads SQUIRE_APP_DIR for the app root, so a kit kept in a subfolder (WELD's deploy/) checks the app it serves.
  • Fixed: the front page and the README's packing list count the parity kit as it ships (19 files; they still said 12).
  • Added: release.sh keeps Composer's and npm's download caches in .cache/squire inside the app folder (SQUIRE_CACHE_DIR, off to disable), so a Citadel Update no longer downloads every package again, and npm ci prefers the cache.

0.7.1 (2026-11-08)#

  • Fixed: Squire's own deploy/.squire.json records the release.sh it ships (it kept the 0.6.0 hash after the W22 restart step), so squire update no longer refuses it; a test now checks every recorded hash.
  • Docs: the queue-workers guide names the QUEUE_WORKER_MODE switch (scheduler or none) that Sourdough's Laravel shapes ship, with --tries=3 and the test that covers both modes.
  • Fixed: the kit's php.ini no longer sets session.sid_length or session.sid_bits_per_character, so PHP 8.4 and later raise no deprecation notices and session IDs use PHP's default (32 hex characters, 128 bits), as HELMET and SESAME S45 say. Run squire update to take it.
  • Changed: the local a11y scripts run Preflight's own checker (vendored from 0.3.1 and pinned by a test), so they check what CI checks: axe-core 4.14.0, 320 and 1280 px, and the reflow check.

0.7.0 (2026-11-08)#

  • Added: the release script restarts Laravel's long-lived processes after optimize (reload, or queue:restart and schedule:interrupt), report only; SQUIRE_ARTISAN_RESTART=0 turns it off (WELD W22).
  • Added: CI runs Preflight's a11y component (0.3.1) on site/, every page in light and dark at 320 and 1280 px with the WCAG 1.4.10 reflow check, blocking.
  • Changed: CI pins the Preflight components to 0.3.1 (fixed cache keys, and caches saved even when a job fails; D-072).
  • Changed: CI saves its Composer and npm caches even when a job fails, so a retry after a dropped download fetches only what is missing (D-072).
  • Changed: CI caches Composer and npm downloads under a fixed key, so a lock change downloads only what changed (D-072).
  • Changed: HELMET moves to ^1.0, its first stable release, wherever this repo requires it.
  • Fixed: OPEN_QUESTIONS.md no longer says there is no GitHub release job; only the GitLab one is missing.
  • Docs: OPEN_QUESTIONS 13 records the Node every current Citadel image ships (Node 22 from NodeSource, npm bundled, pnpm and yarn through corepack).
  • Added: the docs builder stamps the front page too. An element in a top-level site/*.html page that carries data-docs-version holds the docs stamp (the first released CHANGELOG heading, the same value as the docs header's {{version}}); a plain run writes it, --check reports the page stale after a release, and an element with markup inside is a finding. Squire's own chip now carries it. Other sites get it on their next kit sync.
  • Fixed: the docs kit's copy button no longer covers the first line of code when it says Copied or Copy failed. It grows only where it stays clear of the code; over the code it keeps its resting width and shows a check or a cross when the word does not fit (the live region still says it in words). The failure word is now Failed.
  • Fixed: the front page's quick start command folds at its spaces on a phone (560 px and narrower), with the --dev flag kept whole, instead of hiding its tail behind a sideways scrollbar.
  • Changed: the deploy layer requires PROCTOR ^0.8 (locked 0.8.0).
  • Fixed: the front page's Get started prompt wears the site's look (paper card, stitched seam, Arvo title, green buttons) inside the page width; it came out plain white and full-bleed because squire.css mapped none of the kit's --ar-* tokens.
  • Fixed: the docs kit's mobile menu closes with Escape and puts focus back on its summary (kit/docs/docs.js; Enter and Space already toggled it). Other sites get it on their next kit sync.
  • Changed: the pipeline pins every Preflight CI component to 0.3.0 (preflight@0.3.0); component image inputs are plain image names, since Preflight adds the Dependency Proxy prefix itself.
  • Docs: the README's Commands section gains the stack's "Which command when" table, copied word for word from WELD's docs: squire doctor, squire init --check, weld:doctor, proctor check and the other look-alikes, with what each checks, when to run it and where it runs (D-064).
  • Docs: the build.sh template and MAINTAINING.md say what a Citadel test showed (SQUIRE-16): an edited build.sh rebuilds its image step on a full Update, and a Quick Update never runs it; the revision marker stays.
  • Docs: a queue workers guide (the scheduler-driven short worker that works today, the timeout rule, and the supervised-worker request for Citadel).
  • Changed: the GitHub a11y job is blocking now that it has been seen green on GitHub (SQUIRE-35).
  • Fixed: the front page accessibility gate installs again on GitHub: tools/a11y/package-lock.json now matches the @axe-core/playwright 4.14.0 pin (the dependency update had changed only package.json).
  • Docs: source comments, messages and art titles write Squire as a word, not in capitals; wordmarks keep their display type.
  • Fixed: the front page's deploy layer (deploy/) really runs kit 0.6.0 now: the earlier update kept the old record and missed release.sh, the Dockerfiles, php.ini, the compose file and the two hardening files (.squire/apache-hardening.conf, .squire/php-web.ini); squire init --check passes on all 23 files.
  • Fixed: squire update records the current release in .squire.json even when every file already matches it; it kept the old version, so Squire's own deploy layer said 0.5.0 on 0.6.0 files.
  • Fixed: the pipeline's PROCTOR jobs no longer pass --policy, which PROCTOR 0.7 refuses in CI; PROCTOR checks against the CREED policy it bundles.
  • Changed: the front page's deploy layer (deploy/) pins HELMET ^0.4 (locked 0.4.0) and PROCTOR ^0.7 (locked 0.7.0).
  • Added: the image contract suite checks the hardening inside the running image (SQUIRE-40): after the release, scripts/contract-image.sh pipes the new scripts/contract-image-checks.php to php in the container, which asks Apache for a probe page (scripts/contract-image-probe.php, the fixture's app.php) and checks the Server header, X-Powered-By, TRACE, the web's opcache and disable_functions, the CLI's full function set, a Composer post-install-cmd that shells out, and a throwaway secret mounted at /run/secrets (seen by the web, named by the release, absent from every log, layer and image config). Green on linux/amd64 locally (23 assertions); GitHub's contract-image job runs it on both platforms. The driver's Composer image is pinned by digest.
  • Changed: every image the kit pulls is pinned by its multi-arch list digest (SQUIRE-30): the fallback base's php:8.4.27-apache, node:22.23.4-trixie-slim and composer:2.10.3, the Vue layer's Node service (node:22.23.4-bookworm-slim, was the moving node:22-bookworm-slim), the Oracle parity image's PHP base and Composer, and the Composer image the Oracle build scripts run. The parity bases move to images/oracle/php-images.txt, one pinned row per PHP line (8.3, 8.4, 8.5), which both Oracle build scripts read and pass as PHP_IMAGE; a line without a row is refused. A test fails on any unpinned reference. Bump procedure: Image hardening in the docs and MAINTAINING.md.
  • Added: an escape hatch for npm install scripts and a written release-age policy (SQUIRE-26): SQUIRE_NPM_REBUILD names the packages (space-separated, each checked against the shape of a package name) that run their own install scripts after npm ci --ignore-scripts (npm rebuild --ignore-scripts=false, or pnpm rebuild), so one native addon no longer means turning scripts back on for every package. The release logs the npm version and notes when that npm (older than 11.10) ignores min-release-age. The Vue layer's .npmrc keeps min-release-age=1 and explains it, with the deliberate --min-release-age=0 install for an urgent fix. Docs: Image hardening, The release script, Configuration reference.
  • Added: secrets as files at run time (SQUIRE-18): scripts/release.sh and the fallback entrypoint share one loader that turns each file in SQUIRE_SECRETS_DIR (default /run/secrets, where Docker, Compose and Kubernetes mount secrets) named like a variable into that variable, unless the environment already sets it; names that change how the shell runs are skipped, and only names are printed. The entrypoint loads them before Apache starts; the release loads them again after su -l. SQUIRE_SECRETS_DIR joins the settings-file allow list. Tests run the loader in bash, keep the two copies identical, and keep secrets out of the Dockerfiles, the build context and build.sh. Docs: Image hardening (Citadel, Compose, docker run, OpenShift), Citadel setup, The release script, Configuration reference.
  • Added: the web loses the shell (SQUIRE-29): the new parity file .squire/php-web.ini sets disable_functions to exec, passthru, shell_exec, system, pcntl_exec, phpinfo, show_source and highlight_file, and the app image appends it to php.ini as php-apache2handler.ini, the file mod_php reads, so the CLI (Composer scripts, artisan, the health check, the release script) keeps every function. proc_open and popen stay for Symfony Mailer, Laravel's Process and PHPMailer. SQUIRE_PHP_DISABLE_FUNCTIONS replaces the list and none disables nothing; PHP's ${NAME:-default} falls back only when the variable is unset, so the parity compose files pass it by name only and an unset one never reaches the container as an empty value. php.ini no longer sets disable_classes, which PHP 8.5 removed. Tests run PHP on both files.
  • Added: production opcache in the kit's php.ini (SQUIRE-10), set by how code arrives: opcache on for the web and off for the CLI, 128 MB, 20000 files and a 16 MB interned strings buffer. One switch, SQUIRE_OPCACHE_VALIDATE: 1, the default, wherever code is pulled into a running container (a Citadel Quick Update, a bind mount, or anywhere Squire cannot tell), checks files every 2 seconds (revalidate_freq 2), so a release is never served stale; 0, for an image that bakes its code in and never changes (OpenShift, Coolify, raw Docker), never checks. It is a build argument of .squire/Dockerfile (default 1, never empty) and a run-time variable (the run-time value wins), and the parity compose files pass it from .env.squire by name only. SQUIRE_OPCACHE_MEMORY and SQUIRE_OPCACHE_MAX_FILES set the sizes. The fallback base loads opcache when its image does not. The release script gains a "check opcache" step that never fails: a note when files are checked, a warning when a release in place meets 0. The image contract checks both cases. Docs: Image hardening, The release script, Configuration reference.
  • Added: the fallback base says less about itself (SQUIRE-9): the new parity file .squire/apache-hardening.conf sets ServerTokens Prod, ServerSignature Off and TraceEnable Off, and the base enables it as zz-squire-hardening.conf, after Debian's security.conf (which ships ServerTokens OS and ServerSignature On), so the Server header reads Apache and Apache's own error pages carry no version footer. The app image is unchanged, so a run on the real Citadel image still shows what that image says. New docs page: Guides, Image hardening.
  • Changed: CI caches Composer and npm downloads per lock file (.composer-cache, keyed on composer.lock and deploy/composer.lock, and .npm-cache), so a pipeline stops fetching every package from Packagist and npm on every run. Images already come through the Dependency Proxy.

0.6.0 (2026-11-07)#

  • Changed: the release script asks PROCTOR's deploy gate, proctor gate, for a go or no-go instead of running proctor check, and runs it right after composer audit, before the frontend build and the migrations, so an enforced no-go stops the release before it touches the database. The verdict is written to storage/squire/proctor-gate.json (new setting SQUIRE_PROCTOR_RECORD_DIR, in the settings-file allow list and the .env.squire.example files); when the release goes on, the verdict becomes the baseline the next release is ratcheted against, so a failure that is already live is held and only a new one blocks. SQUIRE_PROCTOR=auto still only reports a no-go, and enforce stops on it. With a PROCTOR that has no gate command the step warns, names the PROCTOR version, and runs proctor check as before. Needs a PROCTOR release with proctor gate to take effect.

  • Changed: doctor S14 passes when the release runs proctor gate as well as proctor check, and the S50 hand-off names proctor gate.

  • Changed: Squire's own deploy layer (deploy/) is updated to the current templates with squire update.

  • Changed: The canonical repository is git.wayne.edu (ADR-0021); docs, links and package metadata no longer point at the archived nougat copy.

  • Changed: the Oracle images publish to the group's images project (images/squire-oracle-sail, images/squire-oracle-parity) because git.wayne.edu has no registry.

  • Fixed: squire update writes the template files a newer release added to a group the kit records: a file the target release has that .squire.json does not list is written from the template, recorded, and printed as added, so one update converges the kit (a kit made before 0.4.0 gains oracle-check.php when it moves past it) instead of leaving the new files to squire init; a file the app already has is still left alone, and an edited file is still refused and shown as a diff.

  • Fixed: squire init without --only defaults to the groups the .squire.json records instead of release,parity, so a bare init completes an existing kit without dropping its groups; with no manifest it still writes release,parity, and --only still wins.

  • Added: the Proof page records its last run: a dated table of the checks run against Squire itself (composer ci and the local parity rig) with their results and durations, so a reader can see when the page was last verified and how to refresh it.

  • Fixed: the docs builder turns an article image whose src leaves the site (an http:, https: or // address) into a text link, because the stack's CSPs block external images: inside an anchor the tag becomes its alt text (the last path segment of the src when the alt is empty) and the link stays, so a README badge reads as a link to its page, and a bare tag becomes a link to the image itself with rel="noopener"; relative, /-absolute and data: srcs are the site's own and stay put, for Markdown images and raw HTML <img> alike.

  • Fixed: images in a docs page sit in rows again instead of stacking one per line (WayneUI's reset makes every image a block): the kit's docs.css puts article images back in the line, centered on the text, while an image alone in its paragraph (or followed only by a <sub> credit) stays a block; a paragraph or block of only images or linked images (badge rows, a README cast row) wraps in balanced lines with even spacing and keeps align="center"; a list whose every item is one image or linked image becomes a wrapping row of 4rem tiles with no bullets; and linked tiles show an accent hairline on hover, the kit's focus ring on keyboard focus, and a 2px lift only without a reduced-motion request.

  • Fixed: the kit's docs.css and docs-site.php answer three findings the new axe-core gates raised on SESAME, HELMET and Booster: inline code in a table header cell now inherits the cell's own colors (color: inherit, background: none) so it keeps the header text's contrast in light and dark themes; every code block gets tabindex="0" from the builder, like the table wrappers, so a block that scrolls sideways on a narrow screen is keyboard reachable; and the level-3 "On this page" entries carry the docs-toc__item base class as well as docs-toc__item--sub so the kit's target-size rules reach them.

  • Security: the front-page deploy layer moves to Symfony 7.4.23 (symfony/http-foundation and symfony/yaml advisories, including CVE-2026-118514).

  • Fixed: GitHub CI's js-tests job installs git first, so checkout keeps package-lock.json.

  • Added: a Proof page in the docs (Reference, Proof): Squire run against 82 Wayne State applications and 13 more repositories on 2026-11-05 (doctor, init, init --check, a second init, doctor again, update --dry-run, and a lint of every file init wrote), plus four of them booted on local parity; what it caught in Squire itself, what it does not prove, and how to run the same on your own app.

  • Changed: squire init says so when the release it just wrote cannot pass its own first step: an app with no composer.json or no composer.lock gets a "Heads up" line naming the missing file and how to make it, instead of finding out from a failed first deploy. Found by the proof run (31 of the 82 apps have no lock file). New tests in ConsoleTest.

  • Changed: Squire's docs theme tidies two rough edges the front page never shows: the phone Menu button keeps a clear line of canvas between itself and the page title, and the sidebar and terminal scrollbars are thin stitches in the theme's colors instead of the browser's grey rail.

  • Fixed: a docs code block that overflows only once the web fonts load joins the tab order: the kit's docs.js re-measures every code block once document.fonts.ready settles (when the browser exposes the Font Loading API), so a block whose width grows with the final font gets tabindex="0" like one measured after a resize; browsers and pages without the API behave exactly as before.

  • Fixed: the docs builder's changelog page writes its own # Changelog heading after the marker comment, so the built page has an h1 like every other docs page; the source's first heading is still dropped, whatever it said.

  • Fixed: the agent-ready Markdown twin keeps the text of a label, which the docs builder wraps around every task-list checkbox and its item text: a list item that opens with a checkbox input (directly in the li, or in a label or paragraph that starts the item) renders as - [ ] Item text, or - [x] Item text when the input carries a checked attribute, ordered lists keep their number, and a label outside a list keeps its text inline.

  • Changed: Squire's own docs pages wear the front page's look through the theme key: docs/_header.html is the front page masthead (satchel, SQUIRE, the same links, the version tag, Documentation marked current) and docs/theme/squire.css maps the front page's canvas, leather, gold and Arvo onto the kit's --dk-* tokens, with luggage tags for labels, the current page and the pager, stitched seams above sections, the hero's strap and buckle under each title, terminals with the gold Copy in the corner, code tabs styled like the front page's OS switcher, a derived dark set (prefers-color-scheme and data-theme), and motion only without a reduced-motion request. The kit's docs.css and docs.js are unchanged.

  • Fixed: the front page footer's Documentation link was green on the deep green footer (contrast 1.43, axe color-contrast); it is gold now, like the footer's line.

  • Added: dark mode in the docs kit: docs.css redefines its twelve --dk-* color aliases with dark fallbacks in :root[data-theme="dark"] and in a prefers-color-scheme: dark query scoped to :root:not([data-theme="light"]), in WayneUI's own resolution order (an explicit choice first, then the reader's system setting, else light), declares color-scheme in each theme so form controls and scrollbars follow, and keeps every text pair at WCAG AA contrast in both themes; the hex fallbacks only apply when WayneUI is absent.

  • Fixed: code tab labels may contain spaces: the docs builder now finds the first tab="..." token anywhere in a fence's info string (the quoted label may hold spaces but no double quote, 1 to 40 characters after trimming) instead of only when it is its own whitespace-separated word, so a fence such as bash tab="Linux / macOS" joins its tab set with the full label; the token is still dropped from the kept info (the language is the first remaining word), an empty or over-long label still leaves the fence as a plain block, and the ids the builder derives from spaced labels stay valid (no spaces).

  • Added: code tabs in the docs builder: consecutive fenced code blocks whose info string carries tab="LABEL" (double quotes, label up to 40 characters) render as one labeled tab set (a docs-tabs element keyed by the lowercased labels joined by |, each panel a docs-tabs__panel with a visible label and the code escaped exactly like a plain fenced block), so every example reads without JavaScript; a lone tab="..." fence stays a plain code block with the tab="..." word dropped from its language class, a run broken by anything else becomes separate sets, and the kit's docs.js turns each set into an accessible tablist (click, arrow keys, Home and End), remembers the chosen label per key in localStorage, and keeps every set sharing a key in step, while docs.css styles the tabs from WayneUI tokens and print shows every panel.

  • Added: Squire's own docs site (docs/ built to site/docs/ by its docs builder) and the composer scripts site:agent-ready, site:agent-ready-check; ci now runs both checks.

  • Added: GitHub alert callouts in the docs builder: a blockquote whose first line is a marker alone ([!NOTE], [!TIP], [!WARNING] or [!DANGER], case-insensitive) renders as an aside with the classes docs-callout and docs-callout--note (one per kind), role="note", a visible label, and the body below it, and the marker line leaves the body; a blockquote without a marker, or with a marker that is not one of the four, stays a plain blockquote, and the kit's docs.css styles all four kinds from WayneUI tokens in light and dark themes.

  • Fixed: the kit's agent-ready.js drops two unused variables in enhancePrompt, so eslint no-unused-vars passes.

  • Fixed: the kit's agent-ready.js and stack-env.js use bindingless catch blocks, so a linter with no-unused-vars passes on them.

  • Fixed: a docs code block that scrolls sideways is keyboard reachable: the kit's docs.js gives a block wider than its box tabindex="0" and takes it away again when a resize makes it fit, so axe's scrollable-region-focusable rule passes on pages with long commands.

  • Fixed: a scrolling code block inside a code tab stays keyboard reachable: docs.js measures a block again when its tab shows, and a resize leaves a block in a hidden panel as it was (it has no box to measure), so axe's scrollable-region-focusable rule passes on whichever tab is open.

  • Fixed: a GitHub task list checkbox in the docs has an accessible name: the builder wraps the checkbox and its item's own inline text in a label (class docs-task), stopping before a nested list or a second paragraph, so axe's label rule passes on pages with task lists.

  • Fixed: sub-items in the docs "On this page" list carry docs-toc__item as well as docs-toc__item--sub, so the kit's item rules (muted color, padding, hover) and a theme's reach them; docs.css also matches a bare --sub item, so pages built before a resync still look right.

  • Fixed: the docs builder ignores generated: markers inside fenced code blocks, so a page can show the marker syntax in an example without the builder filling or checking it.

  • Fixed: the docs kit's copy button says Copied after a successful copy; clipboard.writeText resolves with undefined, which docs.js read as a failure, so every working copy said Copy failed, and a refused write now says Copy failed instead of staying silent.

  • Added: the docs builder's theme hook: an optional theme key in docs/docs.json with css and header members (both optional and independent, both plain relative paths against docs/); css names a stylesheet copied byte for byte to site/docs/theme/ and linked after docs.css on every page, builder-owned like a copied image (--check compares it, reports it stale when it differs, and flags a copy under site/docs/theme/ as a leftover once the key goes away), and header names an HTML fragment whose single

    element replaces the generic docs header in place, its relative href, src and srcset URLs prefixed with the page depth (#, /, // and scheme URLs stay put), its first link to docs/index.html or docs/ marked aria-current="page" unless it already carries one, and its {{project}} and {{version}} placeholders filled (any other {{...}} fails the build, naming it); a non-object theme, a non-string member, an unknown key, an empty string or a path that does not exist is a tool error naming the key, and with no theme key, or an empty one, every generated byte matches the unthemed build.

  • Changed: the docs builder's table cells strip Symfony console style tags (, , , , <fg=...> and </>) before escaping, so a symfony-commands help cell shows list instead of list; other angle text stays.

  • Added: the docs builder's changelog page: when docs/nav.json lists a page whose path is changelog, a plain run writes docs/changelog.md from CHANGELOG.md before building (the usual front matter, a marker comment naming its source, the body without its top-level heading, every version heading kept as written), a relative link becomes a blob link under the nav.json source or loses its link keeping its label when there is none, --check reports docs/changelog.md (missing) or (out of date) instead of writing, and a nav entry without a CHANGELOG.md is a finding.

  • Added: the docs builder's --examples mode runs the tagged command examples in the docs and fails when reality drifts from what they promise: a fenced block tagged run (bash, sh, shell or console, optionally exit=N) runs its lines in order in a fresh temp copy of the examples.cwd folder and compares the output with the following output block, every shell block must be tagged run or carry a docs-test: skip REASON line directly before it, skips are counted and grouped by reason in the summary and capped by examples.maxSkips, and a plain build or --check never runs examples.

  • Added: the docs builder's two-way command and option coverage gate for a symfony-commands block: a code span or fenced line that starts with the CLI name must name a real command (help and list always pass) and may only use options of that command or the application options, every kept command and option must appear in the docs at least once (the generated block counts), and a fenced block whose info string contains docs-test: skip is not scanned.

  • Changed: the front-page deploy layer pins HELMET ^0.3, PROCTOR ^0.4 and CREED ^0.1 (lock: HELMET 0.3.0, PROCTOR 0.4.0, CREED 0.1.6).

  • Changed: CI pins Preflight 0.1.4 (GitLab component includes and the GitHub reusable workflow at its tag commit); the deploy layer sets minimum-stability to stable.

  • Added: the docs builder's link gate for the built pages: every content link must reach a built page, a file under site/, or an external address, a fragment must name a real heading on the page it points at, and a relative link to a file the site does not serve (for example ../README.md) is a finding.

  • Added: a GitHub release workflow (.github/workflows/release.yml) creates the release when a version tag arrives through the push mirror, using the CHANGELOG section for the notes and only the built-in GITHUB_TOKEN.

  • Added: the docs builder's image gate for the built pages: every image a page references (a Markdown image or an HTML img) must name a file under docs/, resolved against the source page's folder, and is copied byte for byte to the same relative path under site/docs/ so the built page's relative src still resolves; a missing image is a finding, unreferenced files are never copied, and --check fails when a copy is missing or out of date.

  • Added: the docs builder compares composer.json's version field with the docs stamp; a different version is a finding.

  • Added: the docs builder's --require-release flag fails when CHANGELOG.md has no released heading yet, so the stamp cannot be unreleased in a checked repo.

  • Added: the docs builder's --require-tag flag fails when the repo's latest version tag does not match the docs stamp (a tag such as v1.6.0 counts as 1.6.0); the flag is off by default.

  • Added: a JavaScript test harness for the docs kit (tests/js, node:test with jsdom pinned exactly in package.json and package-lock.json) and a js-tests CI job on GitLab and GitHub that runs npm ci and npm test in a pinned multi-arch Node 22 image; composer js runs the same two commands locally and stays out of composer ci because the PHP image has no Node.

  • Fixed: the oracle image jobs pin the Buildah image to the v1.43.5-immutable tag and its manifest list digest, because the previous digest was removed upstream.

  • Fixed: a directory asked for without its trailing slash (for example /docs) now redirects to /docs/, so the page's relative images and links resolve.

0.5.0 (2026-11-03)#

  • GitHub CI now pins the PREFLIGHT reusable workflow to the 0.1.3 tag instead of a commit SHA.
  • Added: an ADVISOR module (waynestate/advisor) with squire_doctor and squire_drift.
  • Added: squire doctor oracle runs the Oracle connection check on demand, reading ORACLE_* settings from the environment and .env.
  • Changed: the deploy layer's Squire kit is refreshed to 0.4.0 (the Oracle check script and the updated build and release scripts).
  • Added: CI publishes the multi-arch Oracle images to the project's container registry when a version is tagged.
  • Changed: the docs name the real image path instead of placeholders.
  • Changed: Oracle image recipes use fully qualified COPY --from names so buildah can resolve them; the CI dry run shows amd64 builds need qemu binfmt on the runner (see OPEN_QUESTIONS).
  • Docs: WSL 2 file-location advice and an engines and licenses note for local parity.
  • Added: scripts/contract-image.sh runs release.sh inside the fallback image and asserts the smoke URL, health.php and the first-release log.
  • Added: a contract-image CI job (GitHub) that runs scripts/contract-image.sh on amd64 and arm64.
  • Changed: CI pulls its Docker Hub images through the GitLab Dependency Proxy (the group's CI_DEPENDENCY_PROXY_GROUP_IMAGE_PREFIX), so pipelines no longer hit Docker Hub's anonymous pull limit.
  • Added: contract-parity-sh and contract-parity-pwsh CI jobs (GitHub) that bring the local parity stack up on the fallback image and check the proxy answers.
  • Docs: the contract suite gap on GitLab and the real image is recorded as an open question.
  • Fixed: the fallback base image builds when the host's uid or gid already exists in the image (GitHub runners use 1001).
  • Fixed: the front page shows the current version.
  • Fixed: the contract-image CI job installs PHP and the Composer dependencies before running scripts/contract-image.sh, so it no longer stops on the missing vendor/autoload.php.
  • Fixed: the PowerShell parity script passes the host's uid and gid to the fallback base image build (1000 on Windows, the current user's ids on Linux and macOS) instead of hard-coded 1000, so the app container starts when the bind-mounted source is owned by another user.
  • Added: a front page accessibility gate (tools/a11y: axe-core in Playwright, WCAG 2.2 AA) with scripts/a11y.sh and scripts/a11y.ps1 that run it in Docker; GitHub gets an a11y job, continue-on-error until it has been seen green once.
  • Fixed: scripts/a11y.sh and scripts/a11y.ps1 create tools/a11y/node_modules on the host before docker run, so the named volume's mount point exists when the repo is mounted read-only.
  • Changed: the PROCTOR deploy job is blocking now.
  • Fixed: the contract-image job builds with the docker buildx driver so the app image finds the freshly built fallback base.
  • Added: bin/docs-site.php, the shared docs builder, with the kit's docs.css and docs.js; it turns docs/ into a committed, WayneUI-styled site/docs/ and fails CI when the pages are stale or a finding is present.
  • Changed: docs and package metadata name nougat as the canonical repository, with git.wayne.edu and GitHub as read-only mirrors, until git.wayne.edu has CI runners.
  • Added: the docs builder renders a Source link in the header and footer, with a Mirrors list beside it, from the optional source and mirrors keys in docs/nav.json; a source or mirror URL that is not https is a finding.
  • Added: the docs builder's generated blocks: docs/docs.json defines blocks that own marked regions in docs/**/*.md, the json-table type renders a Markdown table from a command's JSON output, and --check reports a stale block instead of writing.
  • Added: the docs builder's symfony-commands block type runs list --format=json and renders the command reference (overview table, per-command headings with usage, argument and option tables, application options listed once), and its env block type scans the scan folders for prefixed environment variable names and renders them with describe meanings and defaults; a read variable without a describe entry, or a described variable no scanned file reads, is a finding.

0.4.0 (2026-11-01)#

  • Added: oracle-check.php, a plain-language Oracle connection check (settings, host, port, driver, login) shipped in the kit's deploy scripts. release.sh runs it after PROCTOR and before the smoke test; it is a report, never a gate, and stays silent when the app has no ORACLE_* settings.
  • Added: opt-in Oracle-ready Docker images, a Laravel Sail flavour (squire/oracle-sail) and a parity flavour (squire/oracle-parity), with scripts/oracle-image-build.sh and scripts/oracle-image-test.sh. Oracle Instant Client 21.7 on amd64 and 19.32 on arm64 is downloaded at build time and checksum-pinned; nothing from Oracle is committed.
  • Changed: the site's agent-ready files cover the Oracle check.
  • Changed: the readme art check allows the word Citadel.
  • Changed: the deploy layer's Squire kit is refreshed to 0.3.4 (the local .env.squire file is now git-ignored).

0.3.4 (2026-10-29)#

  • Changed: the deploy layer's Squire kit is refreshed to 0.3.3 (release options can now live in ./.env.squire).
  • Fixed: squire init now adds .env and .env.squire to the target .gitignore, so the local deploy secrets file is never committed.

0.3.3 (2026-10-29)#

  • Fixed: docs say app settings go in a ./.env configuration file; Citadel has no dashboard environment field.
  • Fixed: the .env.squire template says to add it as a Citadel configuration file; Citadel has no dashboard environment field.
  • Added: release.sh reads release options from ./.env.squire (parsed, never sourced; allow-listed keys; the environment wins), so they can be set on Citadel.

0.3.2 (2026-10-29)#

  • Added: collapsed prompt blocks show a "Show the whole prompt" button; the fade stays inside the panel.
  • Changed: a long command in the "Run it in" panel folds the same way, behind a "Show the whole command" button, instead of a scroll box with no cue.

0.3.1 (2026-10-29)#

  • Changed: README, site and open questions match 0.3.0 (Sourdough requires Squire, the policy default, the Preflight pin, the static target).
  • Fixed: the agent-ready tool's messages write Squire as a word; the static template's SQUIRE_STATIC_ROOT comment matches the code.
  • Changed: bin/agent-ready.php is clean under Pint's laravel preset (CI checks it); the README says how consumers keep the kit out of Composer downloads.

0.3.0 (2026-10-29)#

  • Added: the raw target ships a front controller.

0.2.2 (2026-10-29)#

  • Fixed: stale capability claims in the site and README.

  • Changed: project names written as words except acronyms.

  • Changed: templates and the agent-ready label write Squire as a word; older labels are still recognised.

  • Changed: CI uses Preflight 0.1.1.

0.2.1 (2026-10-29)#

Fixed#

  • Fixed: SQUIRE reported 0.1.0 after the 0.2.0 release.

0.2.0 (2026-10-29)#

Added#

  • --target=static: writes everything the raw target writes plus a front controller (public/index.php) and an .htaccess that serve a committed static site behind HELMET. The site folder is ../../site by default; point SQUIRE_STATIC_ROOT at another. squire init --check and squire update cover the new files, and the template export carries them under static/.
  • SQUIRE_PROCTOR=enforce: a failed PROCTOR check now stops the release. The default stays report-only, so existing apps are unaffected.
  • SQUIRE_PROCTOR_POLICY defaults to vendor/waynestate/creed/policy/policy.json when unset and present, so a static site needs no environment variables in the deploy wizard. When CREED is not installed, PROCTOR runs on its own default policy with a notice instead of the release failing. An explicit value always wins.

Changed#

  • PHPStan now includes Pinstripe's raw PHP preset (waynestate/pinstripe 0.1) instead of carrying a hand copy of the settings; phpstan.neon keeps only SQUIRE's own paths and PHP version range, and the preset's deprecation checks come along with it.
  • symfony/console floor raised to ^7.4: Application::add() is deprecated since 7.4, and the CLI now calls addCommand().

0.1.0 (2026-10-29)#

Added#

  • squire init with --target, --only, --check and --force; a .squire.json manifest of SHA-256 hashes.
  • squire doctor with text and JSON output, checking 26 rules (see BEST_PRACTICES.md).
  • Templates for raw PHP and Laravel: build.sh, deployments/001-first-release.sh, scripts/release.sh, health.php, public/up.php.
  • Vue/Inertia layer: squire init detects vue in package.json and writes .npmrc with min-release-age=1 and a Vue docker-compose.squire.yml with a Node 22 service (the frontend install and build stay in the one common scripts/release.sh); squire doctor reports the layer and warns when node_modules/ is tracked in git (S78); the template export includes the layer under vue/.
  • Local parity kit: compose file with digest-pinned HA-Proxy and MySQL 5.6.51 images, .squire/ build context, a fallback base image, scripts/parity.sh and scripts/parity.ps1.
  • CI for GitLab and GitHub: composer ci, shellcheck and PSScriptAnalyzer, run in Docker.
  • bin/export-templates.php: export a generated copy of SQUIRE's templates (for Sourdough and other projects that cannot composer require SQUIRE), with a catalog.json and a manifest.json; --check verifies the copy and exits 1 on drift.

Changed#