PHPackages sunnysideup/release - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. [DevOps & Deployment](/categories/devops) 4. / 5. sunnysideup/release ActiveSilverstripe-vendormodule[DevOps & Deployment](/categories/devops) sunnysideup/release =================== Auto-release latest version of a branch. 2.5.3(2mo ago)21.6k↓50%12BSD-3-ClauseShell Since Oct 19Pushed 1mo ago1 watchersCompare [ Source](https://github.com/sunnysideup/silverstripe-release)[ Packagist](https://packagist.org/packages/sunnysideup/release)[ RSS](/packages/sunnysideup-release/feed)WikiDiscussions master Synced 1mo ago READMEChangelog (1)Dependencies (4)Versions (48)Used By (2) Silverstripe Release Module =========================== [](#silverstripe-release-module) This module helps you release your silverstripe (or other) projects. install ------- [](#install) `composer require sunnysideup/release` release script usage -------------------- [](#release-script-usage) This module comes with an opiniated release script that can be used as follows: ### try it [](#try-it) ``` vendor/bin/sake-release -h ``` #### skip front-end flushing [](#skip-front-end-flushing) The script flushes the cli and apache cache by default. To skip flushing the front-end, set the following variable in your `.env` file: ``` SS_RELEASE_FRONT_END=false ``` #### to release a specific branch [](#to-release-a-specific-branch) In general, the script will release the branch 1. set in your command - e.g. `vendor/bin/sake-release develop` will release the `develop` branch. 2. if not set, the script will release the branch set in the `.env` file - e.g. `SS_RELEASE_BRANCH=develop`. 3. if not set, the script will release the branch that fits your `SS_ENVIRONMENT_TYPE` - e.g. `SS_ENVIRONMENT_TYPE=live` will release the `production` branch. Mapping is as follows: `live` => `production`, `staging` => `staging`, `test` => `test`, `dev` => `develop`. To release a specific branch, set the following variable in your `.env` file: ``` SS_RELEASE_BRANCH=feature/my-branch ``` #### speed up DEV/BUILD [](#speed-up-devbuild) To speed up the `dev/build`, you can add the following to your `.env` file: ``` SS_FAST_DEV_BUILD=true ``` other notes about releasing --------------------------- [](#other-notes-about-releasing) Here are some general notes about releases. Use as you see fit. ### requirements [](#requirements) release should be easy .... - Whenever you push to a designated branch, it releases on a server (test / production). - We are able to roll back (db + code) - Releases should be fast ### option 1 - use bitbucket *hook* with this module [](#option-1---use-bitbucket-hook-with-this-module) Here is how: ##### set up .env variables [](#set-up-env-variables) set: - `SS_RELEASE_TOKEN="FOO_BARFOO_BARFOO_BAR"` # set to a random string - `SS_RELEASE_SCRIPT="vendor/bin/sake-release"` in your `.env` file. then add a hook to bitbucket: `https://mysite.co.nz/_resources/vendor/sunnysideup/release/client/ReleaseProjectFromBitbucketHook.php?ts=FOO_BARFOO_BARFOO_BAR` See ### option 2 - use BEAM [](#option-2---use-beam) See ### option 3 - use bitbucket pipepline with this module [](#option-3---use-bitbucket-pipepline-with-this-module) 1. enable pipelines: (see settings / pipelines / settings) 2. create ssh key on bitbucket.com (settings > pipelines > ssh keys) 3. add public ssh key to server in ~/.ssh/authorized\_keys (or through a control panel) 4. write file below as `bitbucket-pipelines.yml` in the root of your project ``` pipelines: branches: development: - step: script: - ssh -o StrictHostKeyChecking=no bitbucket@111.222.333.444 'cd ./var/www/mysite; bash vendor/bin/sake-release develop' master: - step: script: - ssh -o StrictHostKeyChecking=no bitbucket@111.222.333.444 'cd ./var/www/mysite; bash vendor/bin/sake-release production' ``` ##### example pipelines with extra stuff [](#example-pipelines-with-extra-stuff) ### Option 4: use [](#option-4-use-httpsdeployerorg) TBC ### Option 5: use github actions [](#option-5-use-github-actions) TBC ### Health Score 50 — FairBetter than 96% of packages Maintenance87 Actively maintained with recent releases Popularity23 Limited adoption so far Community14 Small or concentrated contributor base Maturity63 Established project with proven stability Bus Factor1 Top contributor holds 96.6% of commits — single point of failure How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Release Activity Cadence Every ~35 days Recently: every ~12 days Total 47 Last Release 56d ago Major Versions 0.1.0 → 1.0.12023-07-31 1.5.5 → 2.0.02024-11-05 2.5.3 → 5.x-dev2026-03-24 ### Community Maintainers ![](https://avatars.githubusercontent.com/u/167154?v=4)[Sunny Side Up](/maintainers/sunnysideup)[@sunnysideup](https://github.com/sunnysideup) --- Top Contributors [![sunnysideup](https://avatars.githubusercontent.com/u/167154?v=4)](https://github.com/sunnysideup "sunnysideup (168 commits)")[![S-GrabhamMadden](https://avatars.githubusercontent.com/u/27248899?v=4)](https://github.com/S-GrabhamMadden "S-GrabhamMadden (6 commits)") --- Tags releasesilverstripebitbucketpipelinescmsgitciSilverstripe-CMS ### Embed Badge ![Health badge](/badges/sunnysideup-release/health.svg) ``` [![Health](https://phpackages.com/badges/sunnysideup-release/health.svg)](https://phpackages.com/packages/sunnysideup-release) ``` PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)