Release Process

Stable

Applies to: WileyLabs repository plugin releases

Introduced: Standardized staged ZIP pipeline

Updated: Documentation v1

The Vexal release process aligns plugin version metadata, changelog surfaces, and canonical WileyLabs ZIP packaging for production installs.

Summary

Use one semantic version across header, constants, readme stable tag, and release artifacts, then build through staged scripts.

Use cases

Ship a SmartBlocks version bump
Produce repository-ready ZIP artifacts
Prevent malformed package structures

How it works

Update version fields and release notes, then run release-smartblocks.ps1 (or registry-based wrappers) to create a clean ZIP with correct top-level slug and entry paths.

Inputs

Updated plugin version and changelog data
Release manifest exclusions
Repository identity metadata

Outputs

Canonical ZIP in WileyLabs package location
Forward-slash entry validation
Hash/checksum-ready release artifact

Admin UI location

Operational process reference; packaging executes from scripts, not WordPress UI.

Post-release telemetry confirms crawler behavior and visibility impacts after deployment.

Release-driven apply actions can still be reviewed through ledger and snapshot history.

Security

Release ZIPs must exclude private docs, tokens, workspace artifacts, and development-only files.