Update PHP version in unrelated files

[mbrodala]

Given that a PHP project defines its used PHP version at the following 3 locations:

• composer.json via "php": "~X.Y.0" in "require" (~ instead of ^ is intentional here, see Require PHP (minor) version #11954)
• Dockerfile via FROM vendor/base-image:X.Y-fpm
• docker-compose.yml via image: vendor/base-image:X.Y-apache

Is there a way for Renovate to update the PHP version of all locations in a single update?

• composer.json:

      "require": {
  -       "php": "~7.2.0",
  +       "php": "~7.4.0",
          "...": "..."
      }

• Dockerfile:

  -FROM vendor/base-image:7.2-fpm
  +FROM vendor/base-image:7.4-fpm
  
  # ...

• docker-compose.yml

  services:
  # ...
    apache:
  -    image: vendor/base-image:7.2-apache
  +    image: vendor/base-image:7.4-apache
  # ...

So the common change here would be updating the major and minor PHP version. The patch version .0 in composer.json can be left unchanged.

I'm not sure if the regex manager can be set up to handle multiple unrelated files with unrelated data sources here.

[viceice]

Yes, you probably need to group them

[viceice]

So composer.json should better be handled via composer manager

[mbrodala]

@viceice You are absolutely right, the composer.lock also needs to be updated. And by Composer itself if possible.

Otherwise this well-known warning appears:

Warning: The lock file is not up to date with the latest changes in composer.json. You may be getting outdated dependencies. It is recommended that you run `composer update` or `composer update <package name>`.

The warning stays when manually updating platform.php in composer.lock since the content-hash also needs an update. So manually updating the composer.lock using replacements is not an option.

Do you have a suggestion, how I could invoke Composer to update the composer.lock, too?

[viceice]

On self hosted you can use Postupdate command.

For hosted app we need to extend the composer manager.

[mbrodala]

OK, then this is as far as I can get with a public example using the hosted app. I'd need to continue privately using our GitLab setup.

I see that postUpgradeTasks (this is surely what you meant) only has a fileFilters option. This would mean Renovate would pointlessly do another composer update --lock for every PHP package update which updates the composer.json. That'd be a small disadvantage but still.

So given the fact that I've taken over control using a regex manager there is no way to delegate the actual update to the composer manager, right?

Manually I'd do this after all:

1. Update the Docker image tags
2. Rebuild and start all services
3. Do an composer require php:~X.Y.0

[viceice]

yes, you can disable php in composaer manager, so it won't try on your php branch.

But still i think we should extend the composer manager to handle the php updates.

i think you can scope the post upgrade tasks to your php group only