Prepare v5 for 2026.x

[bluvulture]

v5 ready for 2026.x

[bluvulture]

cc @berfinyuksel

[Copilot]

Pull request overview

Prepares the Docker image v5 line for Pimcore 2026.x by updating documented compatibility guidance and enabling release builds for v5 tags in CI.

Changes:

• Extend the README compatibility matrix to include Pimcore v2026.x and add the new v5 image line.
• Enable v5.0 and v5-dev build entries in the GitHub Actions release workflow.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
README.md	Updates Pimcore compatibility matrix to include v2026.x and v5.
.github/workflows/release.yml	Turns on release workflow matrix entries for v5.0 and v5-dev.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The table header formatting is inconsistent: there’s no space before the v2025.x and v2026.x columns (|v2025.x|v2026.x|). This renders fine, but makes the markdown harder to scan and inconsistent with the other columns. Consider adding spaces around those pipes for consistency.

Suggested change

	| Image / Pimcore | v10 | v11 | v2023.3 | v2024.4 |v2025.x|v2026.x|
	| Image / Pimcore | v10 | v11 | v2023.3 | v2024.4 | v2025.x | v2026.x |

[Copilot]

These new matrix entries have trailing whitespace at the end of the lines. Please trim the trailing spaces to keep the workflow file clean and avoid failing any whitespace/lint checks.

Suggested change

	- { tag: 'v5.0', php: '8.5', distro: trixie, version-override: "", latest-tag: false }
	- { tag: '5.x', php: '8.5', distro: trixie, version-override: "v5-dev", latest-tag: false }
	- { tag: 'v5.0', php: '8.5', distro: trixie, version-override: "", latest-tag: false }
	- { tag: '5.x', php: '8.5', distro: trixie, version-override: "v5-dev", latest-tag: false }