Add Wiki.js compatibility data

[gi8lino]

What changed

• add Wiki.js compatibility metadata for the bounded release range 2.5.302 through 2.5.314
• model Node.js 22.x and 24.x runtime support
• model every fully supported database engine: PostgreSQL, MySQL, MariaDB, Microsoft SQL Server, and SQLite
• cite the official requirements and the lower and upper version-pinned sample configurations

Why

Wiki.js publishes its runtime and database requirements across the installation documentation and tagged sample configuration. Adding these relationships makes it possible to evaluate Wiki.js upgrades against the deployed Node.js runtime and database version.

The bounded project-version range preserves the documented Node.js support boundary at 2.5.302 while avoiding duplicated compatibility rows. The tagged config.sample.yml file has the same Git blob at both endpoints.

Scope decisions

• MySQL 5.7.8 is documented as partially supported and is not represented as a compatible range because the current schema cannot express partial compatibility without overstating support.
• Wiki.js 3.x is not included because it is not a released production target.
• Browser compatibility is omitted because the documentation uses moving version labels.
• PostgreSQL is included with the project-recommended status in notes; SQLite's production warning is also preserved in notes.

Validation

• npm run validate:data -- data/*.yaml
• npm run lint
• git diff --check

[rxbn]

Thanks for the thorough source-backed contribution. The dependency choices and the decision not to treat partially supported MySQL 5.7.8 as compatible make sense.

Please collapse the three duplicated patch rows into one bounded project-version range:

versions:
  '2.5.302 - 2.5.314':
    dependencies:
      # one copy of the Node.js and database entries

The compatibility engine accepts semver ranges as project-version keys. I verified that this range matches 2.5.302 through 2.5.314, while 2.5.301 and 2.5.315 remain unknown. This keeps future updates small: after verifying a new release, only the upper bound and evidence need updating instead of adding another duplicated block.

Please do not replace the rows with a broad 2.5 key. The official requirements say Node.js 22 and 24 support starts with Wiki.js 2.5.302; a 2.5 key would also match older patches and incorrectly report them as compatible. The tagged config.sample.yml file has the same Git blob across every release from 2.5.302 through 2.5.314, so the bounded range is both less noisy and supported by the upstream evidence.

Please also consolidate the patch-specific source anchors accordingly. Referencing the lower and upper tagged configurations plus the official requirements page should preserve the important evidence without repeating identical entries.

[rxbn]

Thanks for the update. The bounded project-version range, consolidated sources, and patch boundary now match the requested model. I verified the full local validation suite and confirmed the API returns compatible only for 2.5.302 through 2.5.314.