Note: the last stable release does not contain all bug fixes to the stable branch: you can try its last snapshot, but almost surely not all the fixes for the known bugs in the stable release have yet been included in such snapshot.

Download from Git instead

Active MediaWiki developers should instead download from Git to get the latest version of the MediaWiki software.
The git repository has earlier versions of the software, so it is possible to switch to ("check out") a particular release.

Notes

Microsoft SQL Server and Oracle Database, HHVM and PHP 7.0 and 7.1 support has been removed since MediaWiki 1.34.

Alternatives to manual installation

Some users may prefer to skip manual installation by using a pre-integrated MediaWiki software appliance or hosting services; repositories of some distros also increasingly offer packages for MediaWiki, with different degrees of frequency and extensions coverage (e.g. Debian, Ubuntu, Fedora, Gentoo).

What next?

Legacy releases

If your MediaWiki installation is heavily modified, it may be difficult to incorporate the latest official changes/updates to MediaWiki. To support such users, we maintain old branches of our code for up to a year for the legacy release and up to three years for the legacy long term support release.

Installation assistance

mediawiki-l (Mailing List) is the high-traffic mailing list to ask for support.

References

↑This could cause reference problems when you later use "git pull" to upgrade your shallow clone and the newer revision refers to older revisions which are not yet downloaded to your system. In such a case you can simply download more - increase the depth value - or all revisions later, or make a fresh shallow clone.