Create a Customer Release
Prepare, validate, package, inspect, and checksum a clean versioned customer ZIP.
On this page 5
What you will learn
- Prepare release metadata.
- Create the supported artifact.
- Verify excluded and included files.
Prerequisites
- Authorization to create a customer package
- A clean validated canonical source
Prepare the version
Increment the template version in package.json and describe customer-visible changes in CHANGELOG.md. Do not create a release from an unclear or partially tested state.
- Version chosen
- Changelog updated
- License files current
- Environment example safe
- No credentials in source
Build the release
The supported command runs the full check before creating a versioned directory and ZIP inside dist.
bash
pnpm release:templateArtifact contract
The package includes editable source, lockfile, documentation, licenses, scripts, tests, and bundled UI CSS. It excludes local dependencies, build cache, demo production environment values, test output, and CDN publishing credentials.
- No node_modules
- No .next
- No .env.production
- No test-results
- No CDN credential
- Bundled Nexus UI CSS present
Verify delivery
Extract the ZIP into a temporary directory, run the documented install flow, and record a SHA-256 checksum for delivery integrity.
bash
sha256sum dist/azora-nexus-template-<version>.zip