Knowing the maintenance status of a release
Knowing whether a release a solution runs on is still maintained, and until when: which versions get fixes, which get critical fixes only, and when maintenance ends. Upgrading to a newer release once that is known is a different job.
Overview
SAP's Product Availability Matrix on the SAP Support Portal lists, for each SAP software release, its release type, its maintenance durations, its planned availability and its upgrade paths, with the database platforms and operating systems it runs on.
Not covered: At one release at a time, read in the portal or exported as a file. The matrix does not hold which releases a given organisation runs, so checking a landscape against it is a person's own list held next to the matrix.
SAP's answer is a page of the SAP Support Portal rather than something one develops with, so it is not an artifact. The entries that answer this across stacks are listed on the Operations & Runtime domain page and count into no door's coverage.
Tools that read a person's own export of the Product Availability Matrix: a browser app, SAP Support RadarSAP Support RadarA browser app that checks the support and maintenance status of the SAP product versions a person runs against their own export of the SAP Product Availability Matrix.independent, umbrella, that checks the releases a person marks as their landscape, and a local MCP server, pam-mcp-serverpam-mcp-serverA local MCP server that answers an agent's questions about the support status of SAP product versions from the reader's own export of the SAP Product Availability Matrix.independent, umbrella, that answers an agent's questions about version status. Both are by Tobias HofmannTobias Hofmannmaintains 4 entries, contributed to 12 entries.
capire's release schedule says that when a new major CAP version is released, the former one enters maintenance status, receives critical bug fixes only for at most twelve more months, and then reaches end of life; CAP Node.js majors follow the end of life of Node.jsNode.jsA cross-platform JavaScript runtime that servers, command line tools and scripts written in JavaScript are run with. For the things here, the prerequisite a repository names when its build is a set of npm scripts. LTS releases.
Not covered: At CAP's own runtimes. The schedule says nothing about the releases of the SAP systems a CAP application connects to, which are in the Product Availability Matrix.
No community artifact is documented here.
The SAPUI5 version overview lists the SAPUI5 versions available on SAP BTP and their maintenance status, and points to SAP's maintenance strategy document for versions from 1.120 and to the previous one for older versions.
Not covered: At SAPUI5 on SAP BTP. Which SAP_UI version and front-end server an on-premise system carries is no longer on the page and sits in an SAP Note.
A UI5 build task, ui5-task-check-eocpui5-task-check-eocpA UI5 builder task that matches the UI5 version in ui5.yaml against the versions retrieved from ui5.sap.com and warns during the build once that version's End of Cloud Provisioning quarter has been reached.independent, ui5, that matches the UI5 version in a project's ui5.yaml against the versions retrieved from ui5.sap.com and warns once that version's End of Cloud Provisioning quarter is reached.
Artifacts
Details
Coverage
For your agent
- Ref
capability:product-maintenance-status- JSON
- /capabilities/product-maintenance-status.json
- MCP
- Connecting an agent