What's broken
The deploy-production.yml workflow's last step, Update Notion status to Published (runs notionStatus:publish-production → scripts/notion-status), fails on every production deploy:
message: "select option \"Staging\" not found for property \"Publish Status\". Available options: \"Not started\", \"Update in progress\", \"Ready for translation\", \"Automated translation in progress\", \"Automated translations generated\", \"Auto translation generated\", \"Reviewing translations\", \"Ready to publish\", \"Adding to staging site\", \"Draft published\", \"Published\", \"Remove\", \"Unplublished\"."
✓ Recorded 0 status changes for rollback
Root cause
scripts/notion-status/index.ts:265-268 defines:
"publish-production": {
from: "Staging",
to: "Published",
setPublishedDate: true,
},"Staging" is not, and per the error message may never have been, a real option on the live Publish Status select property. The vocabulary was consolidated to the 13 options listed above (see digidem/comapeo-content-pipeline's mapStatus, 2026-07-01) — this script wasn't updated alongside that change.
Impact
Low — the script queries for pages matching from: "Staging", finds none, and fails with 0 status changes recorded (confirmed via rollback-session log: Recorded 0 status changes for rollback). It never mutates Notion data. But it fails the job on every deploy (though the actual deploy — build, Cloudflare Pages push, content-lock.sha promotion — completes in the steps before this one, so the site does update correctly; only this trailing step is red).
Suggested fix
Update the from value to a real current option. Best guess, unconfirmed: "Adding to staging site" is the closest semantic match to the old "Staging", but whoever owns the content-status lifecycle should confirm which of the 13 current options this workflow is actually meant to transition from before changing it — a wrong guess here would silently do nothing (matching current behavior) or move the wrong set of pages.
Where this was found
Live-verified during the first production deploy of comapeo-content-pipeline's output, 2026-07-13. Documented as a known non-blocking failure in that repo's DEPLOYMENT.md (pending PR #2 merge — link will 404 until then, see main branch after merge).
What's broken
The
deploy-production.ymlworkflow's last step,Update Notion status to Published(runsnotionStatus:publish-production→scripts/notion-status), fails on every production deploy:Root cause
scripts/notion-status/index.ts:265-268defines:"Staging"is not, and per the error message may never have been, a real option on the livePublish Statusselect property. The vocabulary was consolidated to the 13 options listed above (seedigidem/comapeo-content-pipeline'smapStatus, 2026-07-01) — this script wasn't updated alongside that change.Impact
Low — the script queries for pages matching
from: "Staging", finds none, and fails with 0 status changes recorded (confirmed via rollback-session log:Recorded 0 status changes for rollback). It never mutates Notion data. But it fails the job on every deploy (though the actual deploy — build, Cloudflare Pages push,content-lock.shapromotion — completes in the steps before this one, so the site does update correctly; only this trailing step is red).Suggested fix
Update the
fromvalue to a real current option. Best guess, unconfirmed:"Adding to staging site"is the closest semantic match to the old"Staging", but whoever owns the content-status lifecycle should confirm which of the 13 current options this workflow is actually meant to transition from before changing it — a wrong guess here would silently do nothing (matching current behavior) or move the wrong set of pages.Where this was found
Live-verified during the first production deploy of
comapeo-content-pipeline's output, 2026-07-13. Documented as a known non-blocking failure in that repo'sDEPLOYMENT.md(pending PR #2 merge — link will 404 until then, seemainbranch after merge).