Switch 8.4 to 8.5 using isolated staging, composer check-platform-reqs and smoke tests.
What It Does and When to Use It
Read the return value of a NoDiscard-annotated function to avoid warnings. A minimum platform requirement controls what syntax can be parsed; target-version tests find runtime and extension incompatibilities.
Requirements, Inputs and Expected Behavior
The code using the pipe operator, NoDiscard, or void cast requires PHP 8.5 or later; code with older syntax can still run on earlier supported PHP releases. Roll back both runtime and release artifact if a critical extension fails.
Example 1: Basic Operation
Read the return value of a NoDiscard-annotated function to avoid warnings.
<?php
#[\NoDiscard] function getResult(): bool { return true; } $result=getResult(); if (!$result) throw new RuntimeException('Failed');
Example 2: Behavior and Validation
Verify runtime and platform requirements before touching production.
php -v
php -l public/index.php
composer check-platform-reqs
Practical Example: Application Use
Validate dependency constraints, audit vulnerabilities and run regression tests.
composer validate --strict
composer audit --locked
vendor/bin/phpunit --testsuite unit
Important Behavior and Edge Cases
The second example highlights: Verify runtime and platform requirements before touching production. The practical example adds: Validate dependency constraints, audit vulnerabilities and run regression tests.
Comparison with Related Approaches
| Approach | What changes |
|---|---|
| Minimum PHP version and target PHP version | A minimum platform requirement controls what syntax can be parsed; target-version tests find runtime and extension incompatibilities. |
| Choosing safely | Do not introduce syntax from a newer minor version before every production host supports it. |
Common Beginner Mistakes
| Mistake | Correct approach |
|---|---|
| Assuming newer syntax parses on older PHP | Lint with the oldest supported runtime; gate or delay newer syntax. |
| Upgrading CLI PHP but not the web worker | Check the FPM binary, all extensions and the Composer platform in staging. |
| Skipping operational constraints | Roll back both runtime and release artifact if a critical extension fails. |
Key Takeaways
- Switch 8.4 to 8.5 using isolated staging, composer check-platform-reqs and smoke tests.
- Validate dependency constraints, audit vulnerabilities and run regression tests.
- Do not introduce syntax from a newer minor version before every production host supports it.