<runtime> is past its end of life
A mevcore app hosting error at the “settings” stage.
What it means
Support for <runtime> ended on <date>, so it gets no security fixes.
This is a warning about the app settings: mevcore shows it in the Problems card even before a deployment.
Typical causes
- Required environment variables are missing
- A service (database, Redis) is not connected or the limit is reached
- Too little memory for the app's stack
How to fix it on mevcore
The application keeps running. Pick a newer runtime in the settings, raise the version the project asks for if it pins one (engines, target framework, .python-version) and deploy.
- 1 Open the app in the mevcore panel: the Problems card on the overview shows this error and the log line it was found in.
- 2 After the fix, deploy again. If it fails again, the log ends with [mevcore] lines naming the new error code.
- 3 The "Ask AI" button next to the error prepares a request for ChatGPT or Claude: the error code, the end of the log without secrets and the app settings.
For an AI assistant
The same in English: paste it together with the log into the AI chat.
mevcore error code: config.runtime_end_of_life phase: settings diagnosis: <runtime> is past its end of life platform hint: Support for <runtime> ended on <date>, so it gets no security fixes. The application keeps running. Pick a newer runtime in the settings, raise the version the project asks for if it pins one (engines, target framework, .python-version) and deploy. platform docs: https://mevcore.com/llms-full.txt
All error codes · How to prepare your project for mevcore · llms-full.txt
Can't fix it?
Message support with the error code: we will tell you what to change in the project or settings.