How to release Cypht

This page is to document the steps to generate a Cypht release.

Scripts to evaluate:

Steps for 1.4.x:

Release a version of https://github.com/cypht-org/php-sieve-manager and use that in Cypht (done: https://github.com/cypht-org/php-sieve-manager/releases/tag/v1.0.0)
Run all tests and make sure all is well (done)
Create branch 1.4.x and make necessary commits in this new branch (done)
"stability": "dev", in composer.json even though it doesn't exist in https://getcomposer.org/doc/04-schema.md - changed minimum-stability to stable.
Release 1.4.0: https://docs.github.com/en/repositories/releasing-projects-on-github/managing-releases-in-a-repository (done: https://github.com/cypht-org/cypht/releases/tag/v1.4.0)
Update documentation to reflect that we now have 1.4.x and master. Ex.: https://github.com/cypht-org/cypht/blob/master/INSTALL (Note: this is more developer documentation than end-user one. We should have a getting started page for developers where we explain where to commit or base their MRs on.)

Important URLs for Cypht 1.4.0:

Important URLs for Cypht 1.3.0:

Should we continue to use?

Manually releasing a docker image

Until docker tagging is automated, this is now you manually push a new version. In this example I am releasing v2.1.0

Make sure your account has permissions in the dockerhub cypht org.

Pull down the new tag in git

git pull git checkout v2.1.0

Build and push

make docker-push tag=2.1.0

Update the example production compose file:

git checkout master

Update docker/docker-compose.yml to say:

image: cypht/cypht:2.1.0

Create a PR for the change.

Smoke test it:

cd docker docker compose up

###

>