Skip to content

Releases: captainhookphp/captainhook

5.15.2

03 Mar 11:14
5.15.2
728fe38
Compare
Choose a tag to compare

Changes

  • Allow php-path to be an executable with arguments - issue #198

5.15.1

02 Mar 23:06
5.15.1
90b9823
Compare
Choose a tag to compare

Changes

  • Add missing post-commit - issue #200

5.15.0

28 Feb 13:38
5.15.0
bfa05e1
Compare
Choose a tag to compare

Changes

  • Update PHP version to 7.4
  • Add pre-push condition to check for changed files of type
  • Remove php 7.3 build
  • BUGFIX: Make sure you can 'get' the stdIn multiple times

5.14.4

05 Feb 15:16
5.14.4
8309f6e
Compare
Choose a tag to compare

Changes

  • Make sure the php-path is set correctly - issue #198

5.14.3

30 Jan 12:40
5.14.3
6a58975
Compare
Choose a tag to compare

Changes

  • BUGFIX - The block fixup commit action does not fail anymore if remote and local repo are at the same state

5.14.2

30 Jan 12:31
5.14.2
b9dc806
Compare
Choose a tag to compare

Changes

  • Display error messages of allowed errors

5.14.1

30 Jan 10:01
5.14.1
ac8fa96
Compare
Choose a tag to compare

Changes

  • Fix settings - config mixup

5.14.0

29 Jan 17:38
5.14.0
0d44a6f
Compare
Choose a tag to compare

Changes

Add allow-failure setting to config and actions

You can now define the default failure behavior for your Actions in your global settings section. With this you can allow actions to fail and execute the git command anyway.

{
  "config": {
    "allow-failure": true
  }
  "pre-commit": {

You can also overwrite the setting for specific Actions by using the new action settings.

{
  "pre-commit": {
    "is-enabled": true,
    "actions": [
      {
        "action": "ls -lisa",
        "config": {"allow-failure": true}
      }
    ]
  }

In the future we might add new settings like execute-async or something similar.

5.13.0

21 Jan 18:06
5.13.0
85eb7b6
Compare
Choose a tag to compare

Changes

  • Add custom settings feature

You can now set custom settings in your Captain Hook configuration.

{
  "config": {
    "custom": {
      "foo": "bar"
    }
  }
}

You can access the custom settings with Config::getCustomSettings(): array or you can use them to replace values in your configuration file with {$CONFIG|value-of:custom>>foo} that in this example will be replaced with bar.

5.12.0

30 Dec 20:07
5.12.0
cc27956
Compare
Choose a tag to compare

Changes

  • Fix some PHAR issues

⚠️ From now on the PHAR will only support PHP >= 8.0 ⚠️