I do not believe this currently exists anywhere, but given how Proxmox updates work in typical Linux fashion — especially with the Enterprise Repo, which most of us are using in production environments — apt-get applies the latest available updates without an easy way to choose a specific version.

Because of that, we need a dedicated page on the wiki, as well as a clear note in every release note entry — both on the wiki page and in the .md file shown inside MP — stating which Proxmox version that MP release was tested with and approved for.

In addition, I believe it is important to establish a clear contract/promise between MP and its customers where:

• At the time of release, every version of MP supports the latest Proxmox Enterprise-repo version.
  For example, MP 1.1.3 should have been tested against the current Proxmox 9.2.x release available at that time.

To be clear, this does not mean all new Proxmox features must immediately be supported. However, it does mean that all existing functionality that MP uses or relies on must continue to work.

This should also be relatively straightforward to test and re-test. I would expect that by now there is, or should be, an automated test harness that validates MP functionality after every MP patch or codebase update against the supported Proxmox version.

It is critical for us to be able to keep Proxmox fully up to date at all times without risking broken MP functionality. Proxmox and its API are mature and generally follow good practices, so in theory most updates should not break existing MP integrations. The recent HA mechanism change is a good example of the kind of exception where MP needed to adapt — but that should be rare.

That is why the first request above is so important: we need a solid, authoritative page that clearly states which MP versions support which Proxmox versions, so there is no ambiguity for production customers.