Evolution CMS Installer 1.3.2

Evolution CMS Installer 1.3.2

Evolution CMS Installer 1.3.2 introduces optional project-local EVO Skills installation for automated CLI workflows and improves installation reliability across Windows, custom manager directories, and non-interactive environments.

EVO Skills Installation

The installer can now install project-local EVO Skills as an optional final stage of a non-interactive installation.

New CLI options:

• --skills — comma-separated skill names, default, or none;
• --skills-source — local path or Git source containing the skills manifest;
• --skills-ref — optional Git branch, tag, or commit;
• --skills-link — link skills instead of copying them;
• --skills-dry-run — validate and display the installation plan without writing files.

Example:

evo install my-project \
  --cli \
  --skills=default \
  --skills-source=/path/to/evo-skills

Install selected skills:

evo install my-project \
  --cli \
  --skills=evo-skill-creator,evo-git-workflow \
  --skills-source=/path/to/evo-skills

Preview the operation without changing the project:

evo install my-project \
  --cli \
  --skills=evo-skill-creator \
  --skills-source=/path/to/evo-skills \
  --skills-dry-run

The installer creates a project-local lockfile describing the selected source, installation mode, installed skills, resolved files, hashes, and executed operations.

Integrity and Workflow Metadata

• Verify hashes of skill payload files declared by the EVO Skills manifest.
• Reject missing files and content-hash mismatches before installation.
• Record verified file hashes in .evo-skills.lock.json.
• Load and validate optional workflow metadata declared by a skill.
• Resolve and display the planned workflow stage order.
• Record workflow identity, version, hash, dependencies, and resolved stages in the lockfile.
• Reject workflow definitions that request automatic execution or write actions.

Workflow autoload only makes validated workflow metadata available. It does not automatically execute workflow stages or scripts.

Windows Installation Fixes

• Normalize Evolution bootstrap paths during bundled Extras installation.
• Preserve native filesystem paths for file operations while using the path format expected by Evolution CMS core.
• Fix bundled Extras installation failures caused by Windows directory separators.

Custom Manager Directories

Installations using a renamed manager directory now receive correct rewrite configuration.

The installer updates:

• the manager .htaccess RewriteBase;
• the root .htaccess manager-directory exclusion;
• generated paths for manager-owned endpoints.

This prevents friendly URL rules from intercepting manager package routes such as EvoUI and Livewire endpoints.

Cleaner CLI Progress

Non-interactive installation progress is now redrawn in place instead of printing every update on a separate line.

This applies to:

• file downloads;
• archive extraction;
• parsed PHP installer progress;
• other inline progress events.

Regular messages, warnings, errors, and completed steps remain on separate lines, making CI and terminal output significantly easier to read.

Current Boundaries

EVO Skills installation in this release is intentionally CLI-only:

• --skills requires --cli;
• there is no TUI skills selector yet;
• there is no standalone evo install skills command yet;
• installed workflows are validated but never executed automatically;
• skill scripts are not executed during installation.

Existing installations that do not use --skills keep their current behavior.

Updating

Recommended:

evo self-update

Alternatively, update the Composer bootstrap package:

composer global update evolution-cms/installer

Verify the installed version:

evo version

Installation

For a new global installation:

composer global require evolution-cms/installer

Then create a new Evolution CMS project:

evo install

Release Assets

Prebuilt binaries are provided for:

• Linux AMD64;
• Linux ARM64;
• macOS Intel;
• macOS Apple Silicon;
• Windows AMD64.

The release also includes checksums.txt for SHA-256 verification. The Composer bootstrapper downloads the matching binary and verifies its checksum automatically.