Jenkins Plugin "requires a newer version of Jenkins" - Fix Incompat

A plugin could not load because it needs a different Jenkins core version, or a dependency plugin at a version that is not installed. Jenkins disables the plugin (or refuses to start cleanly), and any steps it provides disappear.

What this error means

On startup or the Plugin Manager you see Failed to load: <plugin>, requires a newer version of Jenkins (X) than the current (Y), or <plugin> requires <dependency> version >= Z. Pipelines then fail with missing steps the plugin would have provided.

SEVERE: Failed to load: Pipeline: Groovy (workflow-cps 3960.v...)
 - Jenkins (2.479.1) or higher required
 - Update required: Pipeline: API (workflow-api) v1450 (currently v1300)

Common causes

Plugin newer than the Jenkins core

A plugin update requires a core version higher than the one installed, so it refuses to load until core is upgraded.

Missing or too-old dependency plugin

Plugins depend on other plugins. If a required dependency is absent or below the minimum version, the dependent plugin fails to load.

How to fix it

Upgrade core and dependencies together

1. Read the failure to see whether core or a dependency plugin is too old.
2. Upgrade Jenkins core to the required LTS, then update plugins so versions are mutually compatible.
3. Use the Plugin Manager’s compatibility/"updates" view to resolve dependency minimums in one pass.

Pin a compatible plugin set as code

Manage the full plugin set (with versions) as code so every controller runs a tested, compatible combination.

# plugins.txt consumed by jenkins-plugin-cli / JCasC
workflow-cps:3960.vXXXX
workflow-api:1450.vXXXX
git:5.4.0

How to prevent it

• Upgrade core and plugins together, not piecemeal.
• Pin plugins with versions in plugins.txt/JCasC and test upgrades in staging.
• Read the Plugin Manager compatibility warnings before applying updates.

Related guides