Repository navigation
[RFC]: Replace .laminas-ci/pre-run.sh script with .laminas-ci.json config file #332
Description
Activity
We can try to remove it and if it's correctly installing the dependencies we can remove
.laminas-ci/pre-run.sh.- linked a pull request that will close this issueIssue #332: Replaced `.laminas-ci/pre-run.sh` script with `.laminas-ci.json` config file #378
on Sep 4, 2025 - changed the title
[-][RFC]: Remove `.laminas-ci/pre-run.sh`[/-][+][RFC]: Replace `.laminas-ci/pre-run.sh` script with `.laminas-ci.json` config file[/+]on Sep 4, 2025 The original idea did not work out as expected, but there's a different solution that works:
we can require additional PHP extensions via the.laminas-ci.jsonfileTo reflect this new idea, I repurposed this issue.
- added a commit that references this issue
on Sep 4, 2025
Metadata
Metadata
Assignees
Labels
No labels
Based on this PR, before runtime, Laminas' CI action should now be able to correctly determine and install the required PHP extensions (assuming they are present in
composer.json). For this, we probably need to addext-sqliteunderrequire-dev.With this, we should remove
.laminas-ci/pre-run.shfrom our projects and the CI actions should still be able to run successfully.@MarioRadu Thoughts?