Repository navigation
PHPAML CLI 1.7.0-beta.46
Pre-release-
Custom Element subclasses overriding style/State helper methods must adopt
the widened signatures; ordinary Page/Component classes and existing calls
remain supported. See the View migration guide. -
Deliver the coordinated View/Engine release: functional pages and components,
local State, constructor-derived factories, reactive IList and optional Icon,
finalized Style/CSS, precise nesting diagnostics and faster compilation.
Preserve class components and both browser runtimes. -
Add aml install lucide and aml uninstall lucide, pinned to the official
lucide-static 1.61.0 archive with SHA-512 verification and upstream licenses.
Restore the optional dependency during aml install; preserve modified assets
and diagnose remaining Icon references before removal. Ship the installer
helper in macOS, Linux and Windows distributions. -
Keep generated files inside their project paths. Refuse traversal and
symbolic links during generation and project creation; use exclusive file
creation for generators and add cross-platform regression checks. -
Remove duplicate factory functions from the View starter and
make:view-component: View now derives each function's signature directly
from the component constructor when loading the application. -
Refresh the View starter with native semantic components, colocated CSS modules,
responsive container queries, shared light/dark tokens and accessible controls.
Demonstrate automatic State bindings through TextField, Picker, Toggle and
composedStyle::create()/Style::make()styles in a reusable component.
Keep--emptyminimal and existing applications unchanged. -
Pin bundled PHP to
8.4.27on macOS, Linux and Windows for the security
fixes for CVE-2026-109618 and CVE-2026-109619. Refuse a different PHP version
during packaging, installed/portable checks and the macOS publication verifier. -
Select View
^0.1.0-beta.14and Engine^0.1.0-beta.10for new View
applications, including Picker, Toggle and Calendar. Preserve beta/stable
publication channels and the signed macOS release workflow. -
Verify the installed View Style API and colocated CSS module through the
distributed example, including the production archive and both runtimes. -
Finalize the Style/CSS candidate with installed regressions for reactive
values, CSS-wide keywords, clearing,!important, composition, conditions and keyframes in
development and production. Verify TestView from the archive, and test stable
versus explicit beta update selection with mocked release metadata. -
Generate production CSS through the application's installed View runtime,
matching development import selection, errors and ordering. Preserve empty
bundles to replace stale public CSS. Declare starter state stylesheet imports
and verify that removing an import removes CSS from the production archive.