Skip to content

Releases: captainhook-git/captainhook

5.21.2

23 Jan 13:11
5.21.2
f0911f6

Choose a tag to compare

Changes

  • Fix double '..' revision range for {$BRANCH_FILES} placeholder

5.21.1

23 Jan 12:35
5.21.1
b50216b

Choose a tag to compare

Changes

  • Allow skipping options for Branch\Files Condition

5.21.0

23 Jan 11:05
5.21.0
5d1926b

Choose a tag to compare

Changes

  • Revert reflog fallback for {$CHANGED_FILES} introduced in 5.20.0
  • Add new Branch\Files condition
  • Add new {$BRANCH_FILES} placeholder

5.20.2

22 Jan 15:39
5.20.2
e485ec7

Choose a tag to compare

Changes

  • Add conditions to check current branch by regex inspired by @Eydamos ;)
  • Add On and NotOn branch conditions

The Condition\OnBranch condition is now deprecated and should be replaced with Condition\Branch\On.
Full list of Conditions can be found here

5.20.1

22 Jan 12:13
5.20.1
be5608c

Choose a tag to compare

Changes

  • Add IntegrateBeforePush action
  • Add proper filter settings to not list deleted files
  • Properly check the detected ranges
  • Split debug action into Success and Failure

5.20.0

19 Jan 19:50
5.20.0
cebfe57

Choose a tag to compare

Changes

  • Refactor and optimize changeset discovery huge thanks to @Eydamos
  • Output executed cli command anyway in verbose mode
  • Fix branch extraction
  • Catch condition exceptions

🐛 Bugfixes

#233 #234

5.19.2

18 Dec 14:07
5.19.2
604bfc5

Choose a tag to compare

Changes

5.19.1

15 Dec 09:22
5.19.1
93ef43a

Choose a tag to compare

Changes

This release focuses on cleaning up the installation and plugin confusion.
From this point forward the captainhook/composer-plugin is deprecated and "replaced" by captainhook/hook-installer.

The decision was made because the composer-plugin package was doing too much. And by requiring captainhook directly it did not give you the opportunity to choose the CaptainHook installation method yourself.

The new hook-installer package is only focusing on the functionality of activating the hooks for all your team members.
Especially because of an issue @Eydamos pointed out. The Composer "script" solution has some serious drawbacks when installing dependencies with --no-dev. You can follow the discussion over here.

From now on, to automate the hook activation, you should combine your preferred way of installing the Cap'n with requiring the hook-installer package.

Examples

Installing the Cap'n as PHAR via Composer

{
  "require-dev": {
    "captainhook/captainhook-phar": "^5.19",
    "captainhook/hook-installer": "^1.0"
  }  
}

Installing the Captain's source code and its dependencies with composer.

{
  "require-dev": {
    "captainhook/captainhook": "^5.19",
    "captainhook/hook-installer": "^1.0"
  }  
}

Installing the Cap'n via PHIVE and the hook-installer via composer.

{
  "require-dev": {
    "captainhook/hook-installer": "^1.0"
  },
  "extra": {
    "captainhook": {
      "exec": "tools/captainhook.phar"
    }
  }
}

5.19.0

01 Dec 14:36
5.19.0
6109b0f

Choose a tag to compare

Changes

  • Increased PHP requirement to >= 8.0
  • Overhauled the complete action output handling
  • Add BlockSecrets action
  • Improve export ignore
  • Move some HookRunner logic to Config
  • Remove php 7.4 build
  • Remove unused import
  • Cleanup hook argument handling

Issues Fixed

#28, #230

5.18.3

05 Nov 13:59
5.18.3
b7bc503

Choose a tag to compare

Changes

  • Fix inject issue key action #230