test: add release upgrade compatibility matrix

[RentnerKev]

Summary

Add automated release-to-release upgrade coverage.

RentnerProxy now has public releases and must test supported upgrade
paths as a compatibility contract.

Initial Matrix

Evaluate at minimum:

alpha.1 → alpha.2
alpha.2 → alpha.3
alpha.3 → beta.1

If direct older upgrades are officially supported, include them as well.

Verify

For each supported upgrade:

• application starts
• database migrates
• authentication works
• users/roles remain
• Proxy Hosts remain
• Redirect Hosts remain
• certificates remain
• Trusted CAs remain
• Access Policies remain
• runtime reconciles
• HTTP traffic works
• HTTPS traffic works

CI

Do not make every PR unnecessarily download/build every historical
version if this would be excessive.

Choose an efficient strategy:

• dedicated compatibility workflow
• scheduled/nightly
• release-gate
• selected PR trigger when migration/runtime changes

Acceptance Criteria

• automated compatibility matrix exists
• failures identify exact source/target version
• uses real released artifacts/images where appropriate
• current Beta release gate includes required supported path

Priority

P0

Dependencies and sequencing

Validates upgrade hardening #67 and coordinates restore coverage with #71. Reuse the existing production smoke foundation #13 and historical Alpha upgrade fixtures from #34. Provides version-specific compatibility evidence required by #75.

Alpha 4 prerequisite

Include alpha.3 -> alpha.4 (reuse #85 evidence) and alpha.4 -> beta.1 in the supported matrix. Retain direct alpha.3 -> beta.1 evaluation where supported; do not assume skipping Alpha 4 bypasses its migration contracts.

[github-actions]

🔍 Similar issues found

This issue may overlap with existing reports. Please take a look at these related items.

Match	Issue	Status
Medium	#6 – [Bug]: test	CLOSED · COMPLETED

This is an automated suggestion. This issue has not been closed automatically.