Upgrade to PHP 8.2 #969
Upgrade to PHP 8.2 #969
Conversation
Bumps [smarty/smarty](https://github.com/smarty-php/smarty) from 4.5.3 to 5.3.1. - [Release notes](https://github.com/smarty-php/smarty/releases) - [Changelog](https://github.com/smarty-php/smarty/blob/master/CHANGELOG.md) - [Commits](smarty-php/smarty@v4.5.3...v5.3.1) --- updated-dependencies: - dependency-name: smarty/smarty dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps [spomky-labs/otphp](https://github.com/Spomky-Labs/otphp) from 10.0.3 to 11.3.0. - [Release notes](https://github.com/Spomky-Labs/otphp/releases) - [Changelog](https://github.com/Spomky-Labs/otphp/blob/11.4.x/doc/Release.md) - [Commits](Spomky-Labs/otphp@v10.0.3...11.3.0) --- updated-dependencies: - dependency-name: spomky-labs/otphp dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
Merge master into php8
…omky-labs/otphp-11.3.0 Bump spomky-labs/otphp from 10.0.3 to 11.3.0
Bumps [bacon/bacon-qr-code](https://github.com/Bacon/BaconQrCode) from 2.0.8 to 3.0.0. - [Release notes](https://github.com/Bacon/BaconQrCode/releases) - [Changelog](https://github.com/Bacon/BaconQrCode/blob/main/CHANGELOG.md) - [Commits](Bacon/BaconQrCode@2.0.8...v3.0.0) --- updated-dependencies: - dependency-name: bacon/bacon-qr-code dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
…con/bacon-qr-code-3.0.0 Bump bacon/bacon-qr-code from 2.0.8 to 3.0.0
Merge master to php8
… because I don't need its modifications.
|
Just as a heads-up, we're still running the production application on bullseye, which is still PHP 7.4. This can't be merged until we've got the new infrastructure in-place. We will indeed be targeting PHP 8.2 (with bookworm) post-upgrade, and then whatever PHP version trixie gives us when that is eventually released (I'm assuming it'll probably be at least 8.4). At the moment, I'm not hugely sure how to run the upgrade as this will be the first major version bump of PHP in quite a long time. My usual preference with larger/riskier upgrades is to break them down into smaller bits that can be applied a little bit at a time (where possible) to reduce the risk. Smarty 5.x should run on 7.4, so I'd definitely prefer if we split that out into a separate change to go live first. The rest I think is probably all interdependent and has to go at once? |
revert dependency upgrades; purely php8
Done; see #973.
Yes. |
# Conflicts: # composer.json # composer.lock
2 participants
It looks like some dependencies are removing support for PHP 7.4 (which has been EOL for almost two years). Although none of those dependencies' new releases seem to contain security fixes, being on a supported PHP version would likely make applying future security fixes easier.
Notes:
SmartytoSmarty\Smartyand similar is due to the upgrade to Smarty v5 (https://smarty-php.github.io/smarty/stable/upgrading/).