portal · Current reference
Release changes and availability
Every accounted Core and Control source release since the last portal update, with honest activation boundaries.
Applies to evergreen
This history closes the documentation gap after portal v1.3.10. It accounts for tagged Core and Control source individually; a source tag does not activate a managed feature or upgrade a customer site. Current portable documentation follows Distribution’s v1.1.29 stable bundle.
Core remains a portable Hugo framework. Control adds private permissions, review, AI configuration and operations. AI, billing, managed publication and other optional capabilities retain their explicit site and provider configuration. Local tests are separate from production availability, representative accessibility review and measured customer task performance.
Foundry Core source changes
| Version | Change and scope |
|---|---|
| v1.1.17 | Typed editor item schemas expose declared fields without moving source meaning into Control. |
| v1.1.18 | Preview evidence recognizes an exact Go-only restriction without granting process execution. |
| v1.1.19 | Responsive image metadata survives normalization; empty override CSS no longer adds a request. |
| v1.1.20 | Self-hosted attribution font subsets reduce default payload while retaining licensed originals and multilingual detail shaping. |
| v1.1.21 | Ordered native CSS and shared original-font resources support optional bundles without Node. |
| v1.1.22 | Source mapping preserves explicit empty editable values across YAML, TOML and JSON. |
| v1.1.23 | Native page recipes support the content root; cross-platform source preservation and browser diagnostics improve. |
| v1.1.24 | Publication starters and source-bound episode proposals support read, listen and watch journeys without managed write authority. |
| v1.1.26 | Optional site-wide foundation CSS retains complete component states; canonical blueprint authoring and tracking coverage are included. |
| v1.1.28 | Adds portable no-write customer-journey reports and complete mapping for simple wrapped prose. Optional native search shares ordinary Pagefind state and remains off by default; readiness checks do not establish task speed. |
| v1.1.29 | Retires repository Actions definitions and makes the required local verification lane explicit. Bounded native browser identity and focus diagnostics preserve strict keyboard checks; foreign compile/link evidence is separate from native execution. Customer journeys, runtime assets and default-off search retain v1.1.28 behavior. |
Foundry Control source changes
| Version | Change and scope |
|---|---|
| v0.6.1 | Search and reputation follow-through retains source-bound observations and owner reviews without claiming causation. |
| v0.6.2 | Default-off read-only Search Console OAuth adds property selection, refresh and connection recovery. |
| v0.6.3 | New persistent identifiers use UUIDv7; transient security and idempotency values retain UUIDv4. |
| v0.6.4 | A narrowly scoped intake policy separates clear service pitches from customer inquiries; authorized restoration remains available. |
| v0.6.5 | OAuth callback feedback survives session rotation and credential-bearing query strings are excluded from routine logs. |
| v0.6.6 | Bounded callback diagnostics record normalized stages without credentials or request values. |
| v0.6.7 | Credential-free callback checkpoints reach the managed error stream. |
| v0.6.8 | Callback diagnostics identify pre-authorization and redaction boundaries without recording request values. |
| v0.6.9 | The OAuth proxy boundary is corrected and temporary diagnostics are removed. |
| v0.6.10 | Versioned form schemas preserve historical accepted submissions; form-only manifest application rejects unrelated site mutations. |
| v0.6.11 | Forms queues and downloads respect selected-site authority and omit internal classification details. |
| v0.6.12 | Intake screening becomes a validated site policy with conservative treatment of ambiguous content and audited recovery. |
| v0.6.13 | Reversible form-content classification adds operator corrections, bounded local budgets and provider-failure recovery. |
| v0.6.14 | PostgreSQL row-lock targets are explicit while permission, revision and recovery guards remain intact. |
| v0.6.15 | Private Journal writing, groups, Library and placement drafts join the guarded owner editor; publication remains independently gated. |
| v0.6.16 | The schema installer uses the restricted migration principal and preserves runtime-role separation. |
| v0.6.17 | Saved Journal publication binds exact reviewed source, durable steps and independently observed live status; feature activation stays separate. |
| v0.6.18 | Static extraction normalizes public directory modes even under a private operator umask. |
| v0.6.20 | Recognizable page targets, content search, saved-preview sizes and interrupted-save recovery improve owner editing; campaign inquiry capture is included. |
| v0.6.21 | The hardened preview worker uses a fixed bounded socket transport without weakening process protections. |
| v0.6.22 | Typed list-item controls preserve bounds, choices and image authority alongside configurable staff capabilities. |
| v0.6.23 | Preview profiles bind the authorized site to its own exact dependencies and origin. |
| v0.6.24 | Scoped site media sources and reusable hosted references extend existing owner workflows. |
| v0.6.25 | Current tenant/site membership checks, private-response protection and bounded login attempts strengthen account isolation. |
| v0.6.26 | Exact saved-page review prepares only its acknowledged source and explicitly bound images; preparation is separate from approval. |
| v0.6.27 | Reopening an eligible edited page resumes the existing private draft and preserves acknowledgements and sibling work. |
| v0.6.28 | Default-off source-context checks retain earlier private drafts and close ambient Git environment inheritance. |
| v0.6.29 | A disabled saved-work transfer candidate adds protected lineage and qualified preview-input metadata; activation is separate. |
| v0.6.30 | The successor transfer release retains private work and source-pair restrictions; no public publisher is implied. |
| v0.6.31 | Save authority, source anchor and lease generation are rechecked after document-lock waits. |
| v0.6.32 | Saved-work recovery uses a signed scoped intent and reopens its recorded target without copying twice. |
| v0.6.33 | Bounded preview-status retries preserve typing and offer explicit recovery after transient read failures. |
| v0.6.34 | An isolated security runtime candidate updates Python and Django without changing editor permissions or publishing flags. |
| v0.6.35 | Reviewed saved-page publication binds images and hosted references to one frozen source version with durable recovery for ambiguous effects. |
| v0.6.36 | Owner guidance clarifies page selection, private saving and saved-change review on narrow screens. |
| v0.6.37 | A site-scoped content-owner role separates website work from Forms, Contacts and Communications authority. |
| v0.6.38 | The isolated application runtime moves to Python 3.15.2 and Django 6.1.3 while retaining existing owner state and configuration. |
| v0.6.39 | Each site may select its own pinned Core editor runtime; malformed profiles fail closed. |
| v0.6.40 | One document-scoped image inventory replaces repeated field payloads while retaining signed access and current image selections. |
| v0.6.41 | Disabled billing foundations add recurring Checkout and signed event reconciliation; no live payment or Connect flow is implied. |
| v0.6.42 | Content-only accounts receive scoped navigation and authenticated password change without private-intake access. |
| v0.6.44 | Form notification email includes the complete accepted form content and frontend CSRF handling matches the served assets. |
| v0.6.45 | Private media and podcast preparation coordinate page, catalog and feed publication; provider and delivery activation remain separate. |
| v0.6.46 | Approved owned-media addresses require explicit site admission while recognized prior copies retain recovery paths. |
| v0.6.47 | A held Forms/reporting candidate prepares durable intake, schema recovery and traffic coverage with additive migrations. |
| v0.6.48 | The successor Forms/reporting release preserves durable intake and adds exact schema/default compatibility and frozen-data rehearsal. |
| v0.6.50 | A default-off private offer workspace adds review, history, archive/restore and authenticated copy handoff; commerce and publication remain separate. |
| v0.6.51 | Adds optional customer-question declarations, private facts, AI or manual wording, immutable proposal review and conditional draft saves. Feature and inference default off; source publication does not establish production activation. |
| v0.6.52 | Adds explicit Site public-media permission, per-file declarations and show confirmations while preserving private history and public identities. Tagged source is a disabled deployment candidate; installed workflow and provider acceptance remain separate. |
Retained baseline provenance
The initial local baseline retains the following exact snapshots. They are not evidence of upstream publication or current availability. Every actual upstream release is checked separately before deployment; a retained snapshot appearing upstream requires a new accounting review.
- core
v0.1.35at860b8558754387674edddf7fecf9cb9632669e0c: Retained from the initial local baseline; upstream publication has not been established. - control
v0.1.0at5bf65ddd9fbecf3378427939853f27fe2120fda9: Retained from the initial local baseline; upstream publication has not been established.
Before enabling a feature
Confirm its site permission, source/runtime identity, required provider and preview configuration, review and recovery path, and actual deployed status. A successful local rehearsal or a tagged disabled foundation is not a live customer workflow. Existing sites keep their own release and adoption decision.