Jenkins plugin "requires a newer version of Jenkins" in CI

A plugin declares a minimum Jenkins core version. When you install or update a plugin whose minimum is higher than the running controller, Jenkins refuses to load it and reports the required versus current core version. The plugin (and anything depending on it) stays disabled.

What this error means

At startup or after an update, the manager shows Failed to load: <plugin>. <plugin> ... requires a newer version of Jenkins (2.W.X) than is running (2.Y.Z).

Jenkins log

Failed to load: Pipeline: Groovy (workflow-cps 3970.vfbef057c6a_d8)
- Jenkins (2.452) or higher required

Common causes

Plugin minimum core exceeds the running version

The plugin was built against a newer Jenkins LTS than the controller runs, so its declared minimum core is not met.

A transitive plugin dependency raised the floor

Updating one plugin pulled a dependency whose newer release requires a core version above the installed one.

How to fix it

Upgrade the controller or downgrade the plugin

Read the required core version in the message.
Upgrade Jenkins to that LTS (or newer), then reinstall the plugin.
If you cannot upgrade now, install the last plugin release that supports your core.

Terminal

# pin plugins to versions compatible with your core
jenkins-plugin-cli --plugins workflow-cps:<compatible-version>

How to prevent it

Keep the controller on a current LTS so plugins load cleanly.
Check a plugin's required core before updating it.
Manage plugin versions in a pinned plugins.txt and test upgrades in staging.