0.6.3

Fixed

• 🐛 Instantiate named classes without empty parentheses. by @mikebronner in #43

Full Changelog: 0.6.2...0.6.3

0.6.2

Full Changelog: 0.6.1...0.6.2

0.6.1

Full Changelog: 0.6.0...0.6.1

0.6.0

Added

• ✨ Add a shared action that publishes the Pest TIA baseline. by @mikebronner in #42

Full Changelog: 0.5.5...0.6.0

0.5.5

Full Changelog: 0.5.4...0.5.5

0.5.4

Fixed

• ✨ Replace Boost's php/core guideline with one that forbids docblocks. by @mikebronner in #41

Full Changelog: 0.5.3...0.5.4

0.5.3

Removed

• 🔥 Removed PHPMD by @mikebronner in #40

Full Changelog: 0.5.2...0.5.3

0.5.2

Fixed

• 🐛 A failure in the plugin's post-install or post-update step no longer aborts the Composer run. Outside CI, the plugin prints the error and asks you to run the same command again (composer install or composer update), and your project's own scripts still run. With CI set to any non-empty value, the run still fails. One known cause is an update that jumps several versions at once, such as 0.2.0 to 0.5.1. by @mikebronner in #39

Full Changelog: 0.5.1...0.5.2

0.5.1

Added

• ✨ Tell projects to require clean-code, and register it with Boost once they do. Boost composes guidelines only from a project's own dependencies, so clean-code's guidelines never reached consumers. Run composer require --dev mike-bronner/clean-code once. After that, the plugin lists clean-code in boost.json and Boost composes its guidelines. Until then, every run prints that command. by @mikebronner in #37

Full Changelog: 0.5.0...0.5.1

0.5.0

⚠️ Breaking

• ➖ This package no longer requires orchestra/testbench. Apps lose it on their next update, and that fixes pest --parallel: Pest skipped its Laravel handler whenever Testbench was installed, so every worker shared one database. A package repository that uses the artisan shim must run composer require --dev orchestra/testbench.
• ⬆️ mike-bronner/clean-code is now ^0.2.1. A project that requires clean-code at ^0.1 in its own composer.json must raise that requirement first.

Fixed

• 🐛 The test-phase markers no longer clash with the shipped standard. clean-code 0.2.1 exempts // 🧪 Arrange, // 🧪 Act and // 🧪 Assert in test files.
• 📝 The shipped skills teach one marker rule. A phase with content gets its own bare marker, a phase with no content gets none, and phases are never combined to drop a marker.

All in #36

Full Changelog: 0.4.0...0.5.0