|Resolved||Reedy||T180272 Release MediaWiki 1.27.4/1.28.3/1.29.2|
|Resolved||demon||T169127 Release MediaWiki 1.30|
|Resolved||Reedy||T168823 Tracking bug for 1.27.4/1.28.3/1.29.2 security releases|
|Resolved||Reedy||T180231 MW 1.27 and 1.28 require-dev versions of phpunit with known security issues|
|Resolved||Legoktm||T180237 Have composer create a .htaccess file in vendor director|
- Mentioned In
- T191597: MediaWiki 1.30.0 tarball is missing vendor/.htaccess
T181451: RFC: WebAssembly and compiled JS code best practices
T180394: MediaWiki entry points should not be in the base repo directory
T168823: Tracking bug for 1.27.4/1.28.3/1.29.2 security releases
- Mentioned Here
- T180394: MediaWiki entry points should not be in the base repo directory
T167038: Separate "application" and "project" concerns
T180231: MW 1.27 and 1.28 require-dev versions of phpunit with known security issues
Yes, we can technically do this. Composer has post-install hooks like the one that composer-merge-plugin uses. We'd just need to write a simple PHP class that writes out the .htaccess file.
This is a nice idea from a belt and suspenders point of view.
A much better long term fix would be to refactor MediaWiki core so that there is a distinct webroot directory that does not contain all of the PHP code and instead only exposes the entry point scripts. This was discussed at least tangentially in T167038: Separate "application" and "project" concerns.