Closes #3509

It seems that there is a bug in PHP that when a PHAR is include()d or require()d
and the PHAR's bootstrap script has a shebang such as "#!/usr/bin/env php" on its
first line followed by "<?php declare(strict_types=1);" on its second line then
PHP wrongly triggers a "strict_types declaration must be the very first statement
in the script" compiler error.

ChangeLog-8.0.md

@@ -2,6 +2,12 @@
 
 All notable changes of the PHPUnit 8.0 release series are documented in this file using the [Keep a CHANGELOG](http://keepachangelog.com/) principles.
 
+## [8.0.1] - 2019-MM-DD
+
+### Fixed
+
+* Fixed [#3509](https://github.com/sebastianbergmann/phpunit/issues/3509): Process Isolation does not work with `phpunit.phar`
+
 ## [8.0.0] - 2019-02-01
 
 ### Changed
@@ -31,5 +37,6 @@ All notable changes of the PHPUnit 8.0 release series are documented in this fil
 * Implemented [#2762](https://github.com/sebastianbergmann/phpunit/issues/2762): Drop support for PHP 7.1
 * Implemented [#3123](https://github.com/sebastianbergmann/phpunit/issues/3123): Remove `PHPUnit_Framework_MockObject_MockObject`
 
+[8.0.1]: https://github.com/sebastianbergmann/phpunit/compare/8.0.0...8.0.1
 [8.0.0]: https://github.com/sebastianbergmann/phpunit/compare/7.5...8.0.0
 

build/binary-phar-autoload.php.in

@@ -1,5 +1,5 @@
 #!/usr/bin/env php
-<?php declare(strict_types=1);
+<?php
 if (version_compare('7.2.0', PHP_VERSION, '>')) {
     fwrite(
         STDERR,