* 6.3:
Prepare release
Ignore error
Use SplObjectStorage::offsetSet() instead of deprecated SplObjectStorage::attach()
Suppress warning
Update tools
Prepare release
Use SplObjectStorage::offsetSet() instead of deprecated SplObjectStorage::attach()
Suppress warning
Prepare release
Test with more versions
Do not cache Composer dependencies
Suppress warning
Do not use implicitly nullable parameters and prepare release
Do not use implicitly nullable parameters and prepare release
* 5.1:
Use SplObjectStorage::offsetSet() instead of deprecated SplObjectStorage::attach()
Suppress warning
Update tools
Prepare release
Use SplObjectStorage::offsetSet() instead of deprecated SplObjectStorage::attach()
Suppress warning
Prepare release
Test with more versions
Do not cache Composer dependencies
Suppress warning
Do not use implicitly nullable parameters and prepare release
Do not use implicitly nullable parameters and prepare release
* 4.0:
Prepare release
Use SplObjectStorage::offsetSet() instead of deprecated SplObjectStorage::attach()
Suppress warning
Prepare release
Test with more versions
Do not cache Composer dependencies
Suppress warning
Do not use implicitly nullable parameters and prepare release
Do not use implicitly nullable parameters and prepare release
* 3.1:
Prepare release
Test with more versions
Do not cache Composer dependencies
Suppress warning
Do not use implicitly nullable parameters and prepare release
* When I created the 6.0.2 tag, I only ran the tests locally without code coverage
* When I pushed the 6.0.2 tag, the CI pipeline failed
* Upon seeing the CI pipeline, I deleted the 6.0.2 tag (within seconds after pushing it). I also deleted the 6.0.2 release on packagist.org
* As it turned out, the CI pipeline only failed because of bad code coverage metadata (after d0d99db563)
* In hindsight, pulling the release was an overreaction that should have been avoided