Version 1.0.4

What's Changed

• Install python3 as default python executable by @tdgroot in #72

Full Changelog: 1.0.3...1.0.4

Version 1.0.3

What's Changed

• Backport #24: ci: Fix non-templated tag spec in release_semantic_versions.sh by @tdgroot in #71

Full Changelog: 1.0.2...1.0.3

Version 1.0.2

What's Changed

• Application: Fix unsupported heredoc indentation level by @tdgroot in #70

Full Changelog: 1.0.1...1.0.2

Version 3.3.1

Fixed a bug where the .hypernode directory didn't exist on deploy.

What's Changed

• Ensure .hypernode exists by @AlexanderGrooff in #67

Full Changelog: 3.3.0...3.3.1

Version 3.3.0

This release contains a new feature for Hypernode Brancher deployments.

It was already possible to clean up Brancher instances by running hypernode-deploy cleanup. This looked at the deployment-report.json file to see which instances were created an cancelled them. While this is a nice and fundamental feature to have, we found that we still missed something.

What we felt that was missing was a way to cancel Brancher instances not for just the current run, but for all Brancher instances created for a given pull request. For this to happen, you need to label the Brancher instances in the deploy.php file:

$configuration = new ApplicationTemplate\Magento2(['en_US', 'nl_NL']);

$productionStage = $configuration->addStage('test', 'myshop');
$productionStage->addBrancherServer('example')
    ->setLabels(['gitref=' . (\getenv('GITHUB_HEAD_REF') ?: 'unknown')]);

return $configuration;

With this configuration, the test stage will create a Brancher instance with the label gitref=my_feature_branch.

When you want to clean up instances based on that gitref, you can simply run the cleanup command like this:

hypernode-deploy cleanup test

This will look up the Brancher instances using the Hypernode API and match the brancher instances by the labels configured for the test stage.

What's Changed

• remove old 'build image locally' from readme by @vdloo in #62
• add instructions to build and run local image by @vdloo in #63
• Create Brancher node with provided labels and settings by @tdgroot in #65
• Cleanup Brancher nodes by labels by @tdgroot in #66

Full Changelog: 3.2.0...3.3.0

Version 3.0.3

This release features a bugfix introduced in 3.0.2 where new deployment environments were not bootstrapped anymore.

What's Changed

• Fix missing deploy:prepare step by @tdgroot in #57

Full Changelog: 3.0.2...3.0.3

Version 3.0.2

Bugfix release.

What's Changed

• stage/deploy: Fix running deploy:release twice by @tdgroot in #54

Full Changelog: 3.0.1...3.0.2

Version 3.0.1

What's Changed

• console: Add customized ConsoleLogger with different verbosity map by @tdgroot in #52
• feat: Allow run-task command to configure server / build stage by @Fgruntjes in #53

New Contributors

• @Fgruntjes made their first contribution in #53

Full Changelog: 3.0.0...3.0.1

Version 3.0.0!

With this release we're announcing a new feature: Brancher Servers! To see how this can be configured, please check out:
Brancher servers for acceptance/integration testing.

Full Changelog: 2.0.2...3.0.0

Version 2.0.2

Changed

• Platform config directories are now placed in the {{ release_dir }}/.hypernode directory.
• Hypernode setting configurations are now applied with the --block flag to make sure the change is applied before continuing.

Fixed

• Problem where Hypernode Deploy did not exit with a non-zero exit code when a Deployer task failed.