Release 1.1.2 With the release of cf-puppeteer 1.1.2 we worked on backporting some v3 features to the legacy-push option. We also implemented the possibility to use all features with docker images. All new features and bugfixes are listed below. New Legacy-push options: --route-only --no-route New v3 options: --docker-image --docker-username Feedback Please give some feedback and open a issues if you find one. github-issue tracker Changelog Changed 🛠 refactor environment parsing cleanup code update documentation back port “–no-route” and “–route-only” option to “–legacy-push” (v2).

Release 1.1.1 With the release of cf-puppeteer 1.1.1 we worked on some feedback of the community and make the usability easier and more user friendly All new features and bugfixes are listed below. --no-route --venerable-action Examples No-routes Deploy the application without route switching - old application should still run and new one should be stoped after deployment. (Venerable-action will be set to none automatically ) cf zero-downtime-push -f ./manifest.yml --no-routes now you can add new services or what ever you want.

Release 1.1.0 With the release of cf-puppeteer version 1.1.0 we bring some new features and bugfixes. The new features and bugfixes are listed below. --no-route --route-only Examples No-routes Deploy the application without route switching - old application should still run and new one should be stoped after deployment cf zero-downtime-push -f ./manifest.yml --no-route --vendor-option none right now you can add new services or what ever you want. To start the new application with routes and cleanup the old one you can do the following things: