Releases: captainhook-git/captainhook
5.21.2
Changes
- Fix double '..' revision range for
{$BRANCH_FILES}placeholder
5.21.1
Changes
- Allow skipping options for
Branch\FilesCondition
5.21.0
Changes
- Revert reflog fallback for {$CHANGED_FILES} introduced in
5.20.0 - Add new
Branch\Filescondition - Add new
{$BRANCH_FILES}placeholder
5.20.2
5.20.1
Changes
- Add IntegrateBeforePush action
- Add proper filter settings to not list deleted files
- Properly check the detected ranges
- Split debug action into
SuccessandFailure
5.20.0
5.19.2
Changes
- Allow Symfony 7 - thanks to @alessandro-podo
5.19.1
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"
}
}
}