Automate the bumping of PHP extension/module versions

[martyspiewak]

Background

Right now PHP modules need to be bumped manually by updating the php-<version>-extensions.yml files in the build-binary-new task in buldpacks-ci.

Proposal

We should automate this process so that new extension versions are automatically pulled in when they are released.

Known issue: There will still need to be some human intervention if building or testing the extension with PHP fails, in order to determine if this is an incompatible version or we need to change the way we are consuming/compiling it.

Breakdown

Step 1

Add php-extensions to dep-server

• Pecl-hosted extensions
• Add support for general Github-hosted dependencies #34 Github-hosted extensions
• Support for PHP dependencies not hosted on GitHub or PECL #35 Other PHP extensions

Step 2

• Github workflow to update php-base-extensions config files #33 Write GH workflows which check for updates to these extension versions and update the relevant config files

[thitch97]

Alternate option 1:
It may be beneficial to add a url field to the pointing to the release page of the extension.
OR
Modify the klass field in files from above

• This would require changes to the build tooling

Caveats:

• This is only worthwhile if the logic contained within the <internal folder in dep-server pkg/dep> is made public

Questions:

• Will modifying the structure of the files mentioned above break our other build tooling?

[thitch97]

Additional context

[menehune23]

We now have some helper scripts to aid in these tasks. Because some human intervention is required with the module updates, I don't see a world where this is done in CI. I think local scripts to remove the tedium, allowing for intermediate human analysis, is the way to go.