Setting Up a Release Source

Setting Up a Release Source

A Release Source links one product variant to a repository and branch, so the platform knows what to build and where to publish it. Create one under Admin → Licensing → Release Sources.

Creating a Release Source

1. Choose the Product Variant this source builds releases for
2. Choose the Provider and the Connection (from your connected Git Connector accounts)
3. Pick the Repository — for GitHub, GitLab, and Bitbucket this is searched live from the provider, never typed by hand; Custom Git instead asks for the remote URL directly
4. Enter the Branch to monitor for new tags (e.g. main)
5. Choose a Build Profile

Build Profiles

• Default — runs composer install --no-dev --optimize-autoloader. Suitable for most PHP/Laravel packages with no build step.
• Custom — runs your own build script, one shell command per line (e.g. asset compilation, additional Composer flags, packaging steps).

The Build Script Contract

Custom build scripts execute inside an isolated sandbox container under a fixed contract:

• The repository source is unzipped to /work/src before any command runs
• Commands run sequentially and fail-fast — the build stops at the first non-zero exit code
• The environment variables RELEASE_VERSION and RELEASE_TAG are available to every command
• The resulting directory is re-zipped into the release artifact automatically — do not zip it yourself
• Network access is available during the build, so composer install and npm install work as expected
• Builds are capped at roughly 30 minutes; a build that exceeds this is killed and reported as failed