[Release Process] Branching: Composer installer

New branch preparation

Update Composer Install

This process describes required steps in the Bolt release process, specifically the bolt/composer-install repository.

Assuming the following in examples below:

• Local origin is git@github.com:bolt/composer-install.git
• Release branch for bolt/bolt stable is master, until the next beta, then branched from master if not previously
• "3.0" is stable and "3.1" is new beta

Branch present Bolt-stable

Release branch for bolt/bolt stable is master, until the next beta, then branched from master if not previously

To update bolt/composer/install:

git pull --rebase
git checkout -b release/3.0 master
git push --set-upstream origin release/3.0
git checkout master

Update composer.json

Start in the master branch.

git checkout master

Require

The constraint for bolt/bolt needs to be updated. On stable releases it will be lacking the @beta suffix.

    "require": {
        "php": "^5.5.9 || ^7.0",
        "bolt/bolt": "^3.1@beta",
        "PasswordLib/PasswordLib": "^1.0@beta"
    },

Update branch alias

Update the branch alias for dev-master to match the constraint in core, i.e. bolt/bolt

    "extra": {
        "branch-alias": {
            "dev-master": "3.1-dev"
        }
    }