Skip to content
Menu

Upgrading#

How to move the Sourdough CLI to a new release, and what each release changes for the apps it bakes. Upgrading the CLI does not rewrite apps you already baked: after the upgrade, run sourdough feed --dry-run, then sourdough feed, in each app to bring the new release's template changes in, merged with your own. The .sourdough/manifest.json in each app is the record it works from. See Keeping apps current.

Upgrade the CLI#

composer global require

composer global require waynestate/sourdough

composer create-project

composer create-project waynestate/sourdough

Verify with:

sourdough --version

Expected for the current release:

Sourdough 0.4.2

Then read the section for the version you are moving to.

0.4.2 (2026-11-09)#

A patch on 0.4.1: new bakes meet Parity, the stack's tool that runs Citadel on your computer. Every shape's README gains "Run it like Citadel" at the end of "Run it locally", and the docs say when to use it.

What sourdough feed brings an app baked with 0.4.1: nothing. The new text lives in README.md, which is a seeded file: Sourdough wrote it once and you own it. Templates, pins and the Squire kit are unchanged.

Breaking: none. Deprecated: none.

Steps: none required. To run an existing app like Citadel, install Parity, copy the "Run it like Citadel" subsection from a fresh bake of the same shape into your README, and follow it. Apps baked with --docker or --sail set DB_CONNECTION=sqlite in .env for Parity runs, because their .env points at the oven's own MySQL.

How to verify: sourdough --version prints Sourdough 0.4.2, and a fresh bake's README has "Run it like Citadel".

0.4.1 (2026-11-09)#

A patch on 0.4.0: the Laravel shapes pick up the Pinstripe extras WELD carries, and Sourdough's own tests pass on a tag build. The raw shapes are unchanged.

What sourdough feed brings a Laravel app baked with 0.4.0 (Blade, Blade + Vue islands, Inertia; it merges each file with your edits):

  • composer.json: a composer lint:gitlab script that writes Pint's findings as a GitLab Code Quality report, pint-codequality.json ([] when clean).
  • .gitignore: /pint-codequality.json, a CI artifact only.
  • .gitlab-ci.yml: the composer-ci job runs composer lint:gitlab in after_script, so it still reports when composer ci fails, and keeps the report as a codequality artifact for seven days. Pint's findings then show in the merge request widget.
  • tests/Unit/PinstripeWiringTest.php: the app's own test that Pinstripe is a dev dependency, that phpstan.neon includes its Laravel preset and leaves the level and the bans to it, and that pint.json is Pinstripe's laravel.json plus the three recorded skips for Squire's files (deploy, health.php, oracle-check.php).

Breaking: none for an app on the template's wiring. An app whose pint.json skips more paths than those three fails the new test until each extra skip is written into the test with its reason. Deprecated: none.

Steps: in each Laravel app, on a clean git tree, sourdough feed --dry-run, then sourdough feed, then composer ci.

How to verify: composer ci passes, and the next merge request's pipeline lists a codequality report from composer-ci.

0.4.0 (2026-11-09)#

Breaking: Pinstripe 0.3 may fail apps that join SQL from strings. Feed moves every shape to Pinstripe ^0.3, and PHPStan now fails code that builds SQL by gluing a variable into the query text. The fix is to bind the value, with the details below. Everything else in this release is pins, pipeline and kit moves.

// Fails on Pinstripe 0.3: the value is joined into the SQL.
$rows = $pdo->query("SELECT name FROM courses WHERE term = '$term'");

// Passes: the SQL is a literal and the value is bound.
$stmt = $pdo->prepare('SELECT name FROM courses WHERE term = :term');
$stmt->execute(['term' => $term]);

This is a minor, not a patch: feeding it moves an app's dev tools across two Pinstripe minors that ban calls, and moves its pipeline pins and deploy kit.

What sourdough feed brings an app baked with 0.3.0 (it merges each file with your edits):

  • .gitlab-ci.yml: the Preflight 0.5.0 pins (60314791565a264e97cb210813ef4f3e76512402 # 0.5.0, was 0.4.0). Inputs and job names are unchanged, so an include you edited keeps your inputs. Every component's Composer default is now 2.11.1 by digest, and the raw shapes' proctor job keeps proctor.json for Rollcall.
  • composer.json: Pinstripe ^0.3 (was ^0.1) and ADVISOR ^0.2 (was ^0.1) in require-dev; an app baked with --no-advisor gets no ADVISOR line.
  • Raw shapes: src/Oracle.php types query()'s SQL as literal-string (PHPDoc only; the code does the same thing).
  • The Squire 0.10.3 deploy kit (was 0.10.2): comments only. The kit's comments say in plain words what they used to cite by internal item ID; nothing the kit does changes.

Breaking, in full: for apps whose code uses what Pinstripe 0.2 and 0.3 ban, PHPStan (vendor/bin/phpstan analyse, inside composer ci) now fails. The bans are eval(), extract(), var_dump(), dd() and dump() (Laravel's methods of those names too), Http::withoutVerifying() and other ways to turn TLS checks off, and SQL joined from strings: a variable concatenated, interpolated or sprintf()'d into the SQL given to oci_parse(), PDO, mysqli or Laravel's DB::select() and friends. Bind values instead. A helper of your own that takes the whole SQL as a parameter passes once that parameter is typed literal-string in its PHPDoc, the way src/Oracle.php does now; PHPStan then checks the helper's callers. Each finding has a pinstripe.banned.* identifier for a reasoned ignore, and Pinstripe's Banned calls page lists them all.

Steps: in each app, on a clean git tree, sourdough feed --dry-run, then sourdough feed, then composer update waynestate/pinstripe waynestate/advisor --with-all-dependencies (feed never touches your lock files), then composer ci. Fix each pinstripe.banned.* finding PHPStan reports before you push. Deprecated: none.

How to verify: the next pipeline's include list names @60314791565a264e97cb210813ef4f3e76512402 # 0.5.0 on every Preflight component, composer show waynestate/pinstripe waynestate/advisor names 0.3 and 0.2, and composer ci passes.

0.3.0 (2026-11-09)#

New: sourdough adopt for apps Sourdough did not make. An existing app in git gets a manifest with sourdough adopt --shape <shape>, and from then on sourdough feed looks after it like any loaf it baked. See Adopt an existing app and the section on it below.

Breaking: for apps you feed, in five cases. First, the fed composer.json moves PROCTOR to ^0.11 (0.2.0 baked ^0.7). PROCTOR 0.8's crlf-deploy-script fails an app whose build.sh, release.sh or a .sh under deployments/, deploy/ or scripts/ has Windows line endings (CRLF); such a script was already broken on the Linux host, so convert it to LF and add *.sh text eol=lf to .gitattributes. PROCTOR 0.9's case-clash fails two paths that differ only by letter case, and its dev-only-packages fails Laravel Boost or Debugbar in require (they belong in require-dev, where the shapes put Boost). The other checks PROCTOR added from 0.8 to 0.11 (0.8's mysql-eol among them) only warn. Second, a front-end app's frontend job now fails on a lock file that does not match package.json and on a high or critical npm audit finding (below). Third, the test suite fails on a deprecation the app's own code raises or causes (below). Fourth, feed brings Squire's 0.10.2 kit, whose scripts/release.sh stops a Laravel release before anything installs when APP_KEY is unset or APP_DEBUG is true in production (it warns when APP_ENV is not production): set the key in .env or as a masked variable in the Citadel dashboard, and APP_DEBUG=false. Fifth, HELMET moves from ^0.4 to ^1.3, and since 1.0 an unknown quoted source in the CSP (the csp option, or HELMET_CSP in Laravel) throws at boot instead of shipping a token the browser ignores: read every quoted source you set. Deprecated: none.

This is a minor, not a patch: it adds a command, and feeding it moves an app's stack pins, deploy kit and pipeline images.

What sourdough feed brings an app baked with 0.2.0 (it merges each file with your edits):

  • composer.json: HELMET ^1.3 (was ^0.4), SESAME ^0.7 (was ^0.5) and PROCTOR ^0.11 (was ^0.7); the Laravel shapes' CREED floor moves to ^0.1.8 (was ^0.1).
  • .gitlab-ci.yml: Composer 2.11.1, pinned by its multi-arch digest, in composer-ci, sourdough-feed and a11y-pages (was 2.10.3, which is no longer maintained; 2.11.1 fixes two Composer advisories); the Preflight 0.4.0 pins (was 0.3.0); and the sourdough-feed job and the a11y, SBOM and secret-detection gates, which the changelog lists under 0.3.0.
  • The Squire 0.10.2 deploy kit (was 0.6.0; the changelog lists each kit move): .squire/php.ini sets session.cookie_samesite = Lax, the kit's Dockerfiles name every image in full (docker.io/library/...) so Buildah and Podman build them, the fallback base copies Composer 2.11.1, and the portable image ships without node_modules/.
  • Apps baked with --docker: the composer-bin stage of the Dockerfile copies Composer 2.11.1.

SESAME 0.7 and the session cookie. Laravel apps are not affected. A raw app's NativeSession now raises one warning per request when the session cookie lacks HttpOnly, Secure (on https) or a Lax or Strict SameSite. The raw shapes call helmet_boot() before session_start(), which sets all three, and the 0.10.2 kit's php.ini sets Lax, so a fed app that kept that order sees nothing. If you moved session_start() above helmet_boot(), put it back below, or follow SESAME's upgrading notes.

Steps: in each app, on a clean git tree, sourdough feed --dry-run, then sourdough feed, then composer update waynestate/helmet waynestate/sesame waynestate/proctor waynestate/creed --with-all-dependencies (feed never touches your lock files), then composer test and vendor/bin/proctor check. See HELMET's, SESAME's, PROCTOR's and Squire's upgrading notes.

How to verify: sourdough manifest --check is clean after you commit the feed, composer show waynestate/helmet waynestate/sesame waynestate/proctor names 1.3, 0.7 and 0.11, vendor/bin/proctor check ends with RESULT: pass, and the next pipeline's composer-ci job log names composer:2.11.1.

Front-end shapes: the pipeline installs from the lock file. Feed moves the frontend job to npm ci --ignore-scripts and npm audit --audit-level=high --omit=dev (runtime dependencies only; a second run lists dev-only findings without failing). npm ci needs a package-lock.json that matches package.json: an app that has none gets the template's (a seeded file, written only where you have none), and an app that already commits one keeps it. If you added or changed a dependency, run npm install once and commit both files before you push. A high or critical advisory in a runtime dependency now fails the job: update the package (npm audit fix, or npm install <package>@<fixed version>), then commit the lock.

Every shape: deprecations fail the tests. Feed adds failOnDeprecation, failOnPhpunitDeprecation and the two displayDetailsOn... flags to phpunit.xml (Laravel) or phpunit.xml.dist (raw), and ignoreIndirectDeprecations to its <source>, so only a deprecation your code raises or causes counts. The Laravel shapes also take a new tests/Support/ReportsDeprecationsToPhpUnit.php and a tests/TestCase.php that uses it: Laravel's own error handler drops deprecations while testing, so without it PHPUnit never sees one. If the suite now fails, its report names the test and the line: fix the code (on PHP 8.4 and 8.5 that is usually an implicitly nullable parameter, string $x = null, which becomes ?string $x = null). A deprecation you cannot fix yet can go in a PHPUnit baseline (write it with the --generate-baseline <file> option, then name the file in <source baseline="...">), which keeps the gate on for everything else.

Laravel shapes: config/helmet.php shrinks to the app's own override. Feed brings a short config/helmet.php that sets only policy_path; every other HELMET setting comes from the package's own config. If you never changed the file, feed replaces it and nothing else changes, except that the app now gets HELMET's current defaults: HELMET_PRESET can come from Playbook, a set-but-empty HELMET_PROXIES trusts no proxy (as HELMET documents), and the newer settings (HELMET_SESSION_SECURE, HELMET_WARN_DEBUG, the metrics storage) work. If you changed it, feed marks a conflict: keep only the keys you changed, each with the package's whole value for that key, and drop the rest. The full list is in vendor/waynestate/helmet/config/helmet.php.

New: sourdough adopt for apps Sourdough did not make. Nothing changes for an app Sourdough baked. An existing app in git can now get a manifest with sourdough adopt --shape <shape>: files that match the template become managed, files that differ are recorded as yours (a new manifest class feed never writes, merges or reports, until your copy equals the template's), and the first feed adds the files the app lacks. The manifest's schema stays 1. An adopted app records the Sourdough that adopted it, so an older Sourdough refuses to feed it, as for any newer manifest; keep the sourdough-feed job on the newest release. See Adopt an existing app.

New bakes take their PHP floor from CREED. Nothing changes for an app today: the floor is still ^8.3, tested on 8.3, 8.4 and 8.5. When CREED's policy moves the floor, the next Sourdough release bakes the new one and feed brings it in. sourdough new prints the floor, where it came from and the shape's support line; see Support and sunset. Deprecated: none.

0.2.0 (2026-11-08)#

Breaking: for apps you feed, in two cases only. The fed pipeline pins Preflight 0.3.0, which needs GitLab 18.7 or later (git.wayne.edu is newer), and the fed composer.json moves PROCTOR to ^0.7, whose node-eol check fails an app that pins Node 20 or older. Deprecated: none.

This is a minor, not a patch: it adds the saved plan and YAML plans, and feeding it changes an app's pipeline, deploy kit and stack pins.

What sourdough feed brings an app baked with 0.1.7 or earlier (it merges each file with your edits; see the steps below):

  • .gitlab-ci.yml: the Preflight components pinned to the 0.3.0 SHA with image_prefix: "${IMAGE_PREFIX}", the IMAGE_PREFIX workflow rule, and the .composer-cache and .npm-cache download caches.
  • The Squire 0.6.0 deploy kit (scripts/release.sh asks proctor gate, .env.squire.example lists SQUIRE_PROCTOR_RECORD_DIR), plus the scripts/parity.ps1 and fallback image fixes for host uids and gids.
  • composer.json: HELMET ^0.4, SESAME ^0.5, PROCTOR ^0.7 and Squire ^0.6; the raw shapes add guzzlehttp/guzzle and nyholm/psr7.
  • Raw shapes (--raw, --raw --vue): public/index.php hands the cas driver an HTTP client, a request factory and the session, so CAS sign-in works in production.
  • Laravel shapes: config/sesame.php names SESAME 0.5's cas.require_pending_login (leave it on).
  • Apps baked with --docker: the compose files publish the dev server and Vite on 127.0.0.1 only.

Feed does not bring the saved plan (.sourdough/plan.yaml is written by new bakes only) and does not touch your lock files, so the composer update in the steps is yours to run.

New bakes save their plan in the app as .sourdough/plan.yaml, next to the manifest, and --plan reads YAML plans as well as JSON, so the saved plan bakes the same loaf again. Commit it with the manifest. Apps you already baked have no saved plan, and feed does not write one: it is not in the manifest, so feed and manifest --check never touch it. See The saved plan.

Every shape's .gitlab-ci.yml gains a sourdough-feed job that runs sourdough manifest --check and sourdough feed --dry-run on the newest Sourdough release. An app you already baked gets it with its next feed: sourdough feed adds the job to your .gitlab-ci.yml, merged with your own jobs. From then on a release the app has not fed shows as a warning in its pipeline (never a blocked deploy), hand edits to managed files are listed without failing, and a broken record (no manifest, conflict markers left from a feed) fails the job. sourdough manifest --check also forgives line endings now, as feed does, so a raw app's clone no longer reports scripts/parity.ps1 (checked out with CRLF by the shape's .gitattributes) as changed. See Feed in CI.

Every shape's .gitlab-ci.yml now caches its downloads: Docker Hub images through ${IMAGE_PREFIX} (the group's Dependency Proxy when the GitLab has one, Docker Hub otherwise) and Composer and npm installs per lock file. See Dependency caching.

Every shape pins the Preflight components to the 0.3.0 release SHA (23038dfe767f6ef60e3b2efca1128f53d9acdff7, was 0.1.4; Preflight 0.3.0 needs GitLab 18.7 or later). From 0.3.0 each Docker Hub component adds the registry prefix in front of its own image (a new image_prefix input), so the includes pass image_prefix: "${IMAGE_PREFIX}" and no image input: the components and the app's own jobs follow one proxy rule, and IMAGE_PREFIX=docker.io still sends both to Docker Hub. See Preflight's upgrading notes.

New bakes start on the Squire 0.6.0 deploy kit (was 0.4.0): scripts/release.sh asks PROCTOR's deploy gate (proctor gate) for a go or no-go before the frontend build and the migrations and keeps the verdict in storage/squire/ as the next release's baseline. Every shape requires HELMET ^0.4, SESAME ^0.5 and PROCTOR ^0.7. The raw shapes' public/index.php now hands the cas driver a Guzzle client, a request factory and the session, so they sign in with CAS in production (before, the cas driver refused to boot there).

Steps: in each app, on a clean git tree, sourdough feed --dry-run, then sourdough feed, then composer update waynestate/helmet waynestate/sesame waynestate/proctor --with-all-dependencies (the raw shapes add guzzlehttp/guzzle nyholm/psr7 to that line). The feed also brings the Squire 0.6.0 kit files (they are in the manifest). Feed merges the new .gitlab-ci.yml with your own jobs; a job you added that pulls a Docker Hub image or installs packages takes the same pattern by hand (image: ${IMAGE_PREFIX}/<image> and extends: .composer-cache or .npm-cache). A Preflight include you added yourself takes the 0.3.0 SHA too, plus image_prefix: "${IMAGE_PREFIX}"; if it passes an image input, keep the plain name (php:8.4-cli-trixie@sha256:<digest>) and drop any ${IMAGE_PREFIX}/ or ${CI_DEPENDENCY_PROXY_GROUP_IMAGE_PREFIX}/ in front of it, or the component adds the prefix a second time and the pull fails. If you changed the include lines feed manages and it stops on a conflict, take the template's side for the pin and the image_prefix line.

How to verify: the next pipeline's job logs show Pulling docker image with your GitLab's host in front, once, in the Preflight jobs as well as your own; each Preflight job's first line reads Preflight component <name> 0.3.0; and a second run logs Successfully extracted cache.

0.1.7 (2026-11-07)#

Breaking: for new bakes, and for apps you feed. The Inertia shape moves to Inertia 3 (inertiajs/inertia-laravel ^3.0, @inertiajs/vue3 ^3.0: PHP 8.2+, Laravel 11+, ES modules only, Axios no longer bundled). Every shape requires PROCTOR ^0.6, and the Laravel shapes' composer proctor script drops --policy, because PROCTOR 0.6 refuses that option in CI.

Deprecated: none.

Steps: upgrade the CLI, then in each app, on a clean git tree:

sourdough feed --dry-run
sourdough feed

Feed merges the new pins into composer.json (and, in an Inertia app, package.json, resources/views/app.blade.php and resources/js/app.ts, which now hands HELMET's nonce to Inertia so the progress bar's styles pass the CSP) with your own edits. The lock files are yours, so move them next:

every shape

composer update waynestate/proctor --with-all-dependencies

inertia

composer update inertiajs/inertia-laravel waynestate/proctor --with-all-dependencies
npm install
php artisan view:clear

What to check by hand in an Inertia app, because feed only knows the template's code, not yours:

  • Your own code imports axios (or qs, or lodash-es)? Inertia 3 no longer brings them along: npm install axios (or the one you use), or move the call to Inertia's useHttp.
  • Inertia::lazy() becomes Inertia::optional(); router.cancel() becomes router.cancelAll(); the invalid and exception router events are now httpException and networkError.
  • You published config/inertia.php? Its testing.page_paths and testing.page_extensions moved to pages.paths and pages.extensions. Republish with php artisan vendor:publish --provider="Inertia\ServiceProvider" --force and reapply your changes.
  • Another head tag in your root view carries a bare inertia attribute? Rename it to data-inertia, as the template's <title> now is.

The full list is Inertia's own upgrade guide.

A pipeline that passes --policy or --today to PROCTOR fails with exit 2 on 0.6. Drop the option (PROCTOR finds CREED's policy in vendor/waynestate/creed by itself, or name it with the PROCTOR_POLICY variable), or set PROCTOR_ALLOW_OVERRIDES: "1" in a protected or group-level CI variable, never in the app's own .gitlab-ci.yml. PROCTOR 0.6 also fails composer-audit when there is no composer.lock or Composer is not on PATH, and when an audit ignore entry in composer.json has no matching override in policy-overrides.json.

How to verify: composer proctor passes. In an Inertia app, npm ls @inertiajs/vue3 and composer show inertiajs/inertia-laravel both print a 3.x version, npm run typecheck and npm run build pass, and the page source of / carries <script data-page="app" type="application/json"> instead of a data-page attribute on the root div.

0.1.6 (2026-11-06)#

Breaking: for new bakes only; apps you already baked are not rewritten. sourdough new now requires Playbook (waynestate/playbook) in every app and checks that you can read it before writing anything, so a developer without Playbook access gets exit 1 until they have it (--no-playbook is for CI and automated tests only; --playbook is now a no-op kept for old scripts). The Inertia shape draws with WayneUI instead of the Tailwind starter kit, so a new Inertia app has no tailwind.config.js, cn() or kit components. The Laravel shapes generate apps on Pest 4.

Deprecated: none.

Steps: upgrade the CLI with composer global require waynestate/sourdough. The fifth loaf is out of the oven: sourdough new --raw --vue bakes a raw PHP + Vue SPA over JSON (Next steps: composer install, npm install, npm run build, composer serve), so all five shapes generate. Raw apps start with composer serve now; an app baked earlier can copy the raw template's serve script. Laravel apps baked earlier can pick up the fixes by hand: the .gitlab-ci.yml php-test matrix runs vendor/bin/pest, --docker apps run the vite service with LARAVEL_SAIL=1 and install node_modules when Vite is missing, and --sail apps take the new compose entrypoint. See Keeping apps current.

How to verify: sourdough --version prints Sourdough 0.1.6. Bake sourdough new --raw --vue, run its Next steps, and /, /api/me and /up answer.

0.1.5 (2026-11-03)#

Breaking: none. Three more loaves join the bench: sourdough new --laravel (Laravel + Blade), sourdough new --inertia (Laravel + Inertia/Vue) and sourdough new --laravel --vue (Laravel + Blade + Vue islands) now bake, so four of the five shapes generate. New bakes also carry ADVISOR by default (waynestate/advisor in require-dev, .mcp.json git-ignored, a README "ADVISOR" section); pass --no-advisor to skip it. The raw template pins WayneUI 2.0.8 instead of fetching the floating main branch copy, and the Squire copy comes from Squire 0.4.0 (dev dependency ^0.4).

Deprecated: none.

Steps: upgrade the CLI with composer global require waynestate/sourdough. For maintainers of this repository, run composer install to pick up Squire 0.4.0, then composer squire-copy:check. --name on the Laravel bakes now reaches every place WELD applies it by hand: composer.json's name becomes app/<slug> (an application is not a published package), .env.example's APP_NAME carries the app name (quoted when it holds a space), and the config/app.php default follows it.

How to verify: sourdough --version prints Sourdough 0.1.5. Bake a shape and run its Next steps, for example composer install, cp .env.example .env, php artisan key:generate, php artisan migrate, php artisan serve for the Laravel shapes.

0.1.4 (2026-10-29)#

Breaking: for maintainers of this repository, the Squire template copy in templates/squire/ now comes from the waynestate/squire Composer package (new dev dependency, ^0.2) instead of a Squire checkout: composer squire-copy:sync rewrites the copy from vendor/waynestate/squire, and composer squire-copy:check (now part of composer ci) exits 1 when the committed copy has drifted. Generated apps require SESAME ^0.2 (Entra sign-in).

Deprecated: none.

Steps: run composer install to pick up the new dev dependency, then composer squire-copy:check.

How to verify: sourdough --version prints Sourdough 0.1.4; composer ci is green; and sourdough new my-app --laravel --inertia --dry-run is accepted (the flag pair was fixed in this release).

0.1.3 (2026-10-29)#

Breaking: none.

Deprecated: none.

Steps: upgrade the CLI. sourdough new now wires Playbook into generated apps: by default the app's composer.json gets a suggest for waynestate/playbook, .env.example lists the seven WSU shared setting names, the README gains a "WSU values (PLAYBOOK)" section, and the command prints a hint line pointing at it. --playbook adds the VCS repository and requires waynestate/playbook ^0.1; --no-playbook skips all of it; the two flags together are refused with exit 1.

How to verify: sourdough --version prints Sourdough 0.1.3; bake with sourdough new my-app --raw --dry-run and inspect the plan for the Playbook entries.

0.1.2 (2026-10-29)#

Breaking: none declared. Two behaviors tighten for new bakes: the raw template now requires HELMET ^0.2 and PROCTOR ^0.2 (SESAME stays at ^0.1 until it cuts 0.2), and app names that fail validation are refused with exit 1 and write nothing.

Deprecated: none.

Steps: upgrade the CLI. If a script passed an unusual name before, rename it: the name must start with a letter or number and use only letters, numbers, spaces, dots, dashes and underscores, at most 63 characters.

How to verify: sourdough --version prints Sourdough 0.1.2; sourdough new my-app --raw --dry-run prints the plan, and a hostile name (for example one with a slash or over 63 characters) is refused with exit 1 and writes nothing.

0.1.1 (2026-10-29)#

Breaking: none.

Deprecated: none.

Steps: run composer install to pick up the new dev dependency waynestate/pinstripe ^0.1. PHPStan and Pint now take their settings from Pinstripe instead of a hand copy: phpstan.neon includes the raw preset, and pint.json extends the per preset. Same cut, off the rack.

How to verify: composer lint (Pint) and composer analyse (PHPStan) pass, and composer ci is green.

0.1.0 (2026-10-29)#

Breaking: the raw template's own deployments/release.sh and deployments/release.ps1 were removed; the release steps now come from Squire. The raw app installs Squire's deploy files from a checked copy at templates/squire/: build.sh, deployments/001-first-release.sh, scripts/release.sh, scripts/parity.sh, scripts/parity.ps1, health.php, public/up.php, docker-compose.squire.yml, .env.squire.example, and the .squire/ build context. Squire owns them; Sourdough copies them as-is and records them in the manifest.

Deprecated: none.

Steps: run composer install. For maintainers of this repository, mount a Squire checkout (or set SQUIRE_PATH, default /squire) so the copy check can compare against it; the check skips with exit 0 when no checkout is mounted. The Squire template copy was refreshed from e66f07b to 2a893c0 (the Vue layer's .npmrc and docker-compose.squire.yml joined the batch).

How to verify: composer squire-copy:check exits 0 when the copy matches a fresh export from the Squire checkout.