Hypernode Deploy v4.2.0 is here with several improvements and refinements to enhance your deployment experience, most feedback coming straight from our users!
Improved Docker Image Support
- NPM Preinstalled in Docker Builds: When building a Docker image, NPM is now automatically installed, ensuring a smoother experience when working with Node.js dependencies. This was a known bug in older (below 20) NodeJS versions.
- New Docker Image Variants: Added support for
:latest-phpX.X-nodeXtagged Docker images, which allows you to always stay up-to-date with our newest versions without having to update your own deployments. - Wildcard Support for Safe Directories: The Dockerfiles now include wildcard support for git’s safe directories, making repository handling more seamless, this was a bug when sometimes making use of Hypernode Deploy with Bitbucket Pipelines and Github Actions.
Deployment Enhancements
- Refined Autoloading Behavior: The application vendor autoloader is no longer automatically included. This gives developers better control over how dependencies are managed in their projects, and fixing an issue when using Shopware 6. You can make use of the old functionality by running the below command in your deployments:
DEPLOY_AUTOLOAD_PATH=./vendor/autoload.php hypernode-deploy build
- Accurate Branch Naming in CI for Slack notifications: The correct branch name is now displayed based on the CI runner, ensuring clarity when working with slack notifications.
- Support for http:cache:warm:up was dropped in Shopware 6.6+ . We have updated our Shopware recipe to reflect these changes for Shopware 6.6 and above.
To change the new version, please include the latest version of our docker image:
image: quay.io/hypernode/deploy:latest-php8.3-node20
or pin your version by specifying a specific version:
image: quay.io/hypernode/deploy:4.2-php8.3-node20