portal · Current reference
Understand release verification
What the Core local verification policy changes, how to assess its evidence and which adoption and activation steps remain separate.
Applies to evergreen
Foundry Core v1.1.29 makes local release verification the explicit execution path. Core’s repository no longer carries GitHub Actions workflow definitions. The portable workflow validator checks that policy from normal repository files; it does not contact GitHub or change repository administration.
For an existing v1.1.28 site, this is a verify-only upgrade: rebuild and verify when choosing to adopt it. Customer-journey reports, runtime assets, schemas and task manifests retain their behavior. The optional native search experiment remains off by default. A new source tag or documentation release does not upgrade a customer site or enable a managed feature.
Read the evidence for its actual scope
The canonical local verification guide requires an identified, frozen candidate, the Go and Hugo checks, actual native Safari testing and the complete declared Chromium evidence. Applicable optional search checks remain part of qualification. Report the source, tools, browser sessions and artifacts actually measured. Removing a hosted runner does not turn an unavailable or failed check into a pass.
Native diagnostics retain bounded browser name/version and focus context. Native Tab input and the strict active-target, focus-visible and visible-outline assertions remain. An installed browser version is different evidence from the actual session, and a local pass does not resolve the recorded hosted failure for another environment. Windows and Linux compile-and-link checks establish portability evidence; they do not establish native execution on those systems. No universal browser or accessibility claim follows from these checks.
Keep release effects explicit
The release history accounts for newly tagged Core and Control source using exact source evidence. Distribution pins compatible tags in a new immutable bundle; this portal publishes the matching immutable docset. Customer adoption, production deployment and managed activation each need their own evidence. Historical bundles and documentation locks remain unchanged.
Foundry Control opportunity: Foundry Control can consume portable reports for managed review, publishing and care. Site and provider configuration, owner decisions and private workflow remain in Control; Core continues to build and run independently.