fix: release v1.11.0-rc.12 for deployments' own site.yml

CHANGELOG.md

@@ -8,6 +8,22 @@ major version, and each entry says so when it happens.
 
 ## [Unreleased]
 
+## [1.11.0-rc.12] — 2026-10-16
+
+Twelfth candidate. rc.11 failed closed in a deployment's update (nothing was
+published) on a test that read the deployment's own `site.yml`; rc.12 fixes that
+test and otherwise carries rc.11 unchanged.
+
+### Fixed
+
+- A test added in rc.11 failed inside a real deployment's PHCT update, which
+  runs the template's suite on the deployment's own files.
+  `submit_uploads.test.mjs` required `_data/site.yml` to carry a blank
+  `submit.uploads_url`, which a deployment's own `site.yml` need not have. That
+  file belongs to the deployment, so the check is gone; off-by-default is still
+  checked on the submit page's own snapshot and at runtime. The submit page and
+  the upload code were not at fault.
+
 ## [1.11.0-rc.11] — 2026-10-16
 
 Eleventh candidate. It adds optional file uploads on the submit page (off by
@@ -1780,7 +1796,8 @@ fixed in this release, and the remaining P3s are listed in `docs/roadmap.md`.
   in-browser and CLI configurators, GitHub-issue submission flow, events /
   cohorts / resources modules, Lunr search, thumbnails workflow.
 
-[Unreleased]: https://github.com/crypticpy/phct/compare/v1.11.0-rc.11...HEAD
+[Unreleased]: https://github.com/crypticpy/phct/compare/v1.11.0-rc.12...HEAD
+[1.11.0-rc.12]: https://github.com/crypticpy/phct/compare/v1.11.0-rc.11...v1.11.0-rc.12
 [1.11.0-rc.11]: https://github.com/crypticpy/phct/compare/v1.11.0-rc.10...v1.11.0-rc.11
 [1.11.0-rc.10]: https://github.com/crypticpy/phct/compare/v1.11.0-rc.9...v1.11.0-rc.10
 [1.11.0-rc.9]: https://github.com/crypticpy/phct/compare/v1.11.0-rc.8...v1.11.0-rc.9

README.md

@@ -104,7 +104,7 @@ A fork is a copy, not a subscription: template releases do not reach you on thei
 ```bash
 git remote add template https://github.com/crypticpy/phct.git
 git fetch template --tags
-npm run upgrade:check -- --to v1.11.0-rc.11 # read-only: what this exact release changes, in two lists
+npm run upgrade:check -- --to v1.11.0-rc.12 # read-only: what this exact release changes, in two lists
 ```
 
 The whole protected-update and manual-recovery recipe: [`docs/upgrading.md`](docs/upgrading.md).

docs/release-readiness-plan.md

@@ -3,7 +3,7 @@
 - Status: in execution; automated baseline implemented 2026-08-22
 - Created: 2026-08-21
 - Target: a release candidate suitable for the wider BCHC demo audience next week
-- Candidate: `v1.11.0-rc.11` (last stable release: `v1.10.0`)
+- Candidate: `v1.11.0-rc.12` (last stable release: `v1.10.0`)
 - Parent repository: [`crypticpy/phct`](https://github.com/crypticpy/phct)
 - Downstream demo: [`Big-Cities-Health-Coalition/use-case-catalog`](https://github.com/Big-Cities-Health-Coalition/use-case-catalog)
 

package.json

@@ -1,6 +1,6 @@
 {
   "name": "phct",
-  "version": "1.11.0-rc.11",
+  "version": "1.11.0-rc.12",
   "private": true,
   "packageManager": "npm@10.9.4",
   "engines": {

test/scripts/submit_uploads.test.mjs

@@ -296,7 +296,8 @@ test('feature off: no pickers, no script, no data attribute — in the markup an
     !SCRIPTS.some((src) => /uploads/.test(src)),
     'the uploads scripts must not be in the always-on list'
   );
-  assert.match(read('_data/site.yml'), /^ {2}uploads_url: ""/m, 'uploads must be off by default');
+  // _data/site.yml belongs to the deployment (merge=ours), which may have
+  // turned uploads on, so off-by-default is checked on the snapshot below.
   assert.doesNotMatch(FIXTURE, /uploads/i, 'the off-by-default snapshot mentions uploads');
 
   // At runtime: signed in, but no uploads script and no attribute.