The jenkins update center is serving the wrong update-center.json file for pinned versions. As a result automation that depends on this file to determine the latest compatible version of a plugin for a particular jenkins version (such as the plugin manager CLI) may pull in a plugin version that is too high and requires a newer Jenkins core version.

As far as I can tell there is no place to obtain the actual update-center.json file for 2.277.3 once a newer LTS is released.

Expected:

1. Hit https://updates.jenkins.io/update-center.json?version=2.277.3
2. Get redirected to https://updates.jenkins.io/dynamic-stable-2.277.3/update-center.json
3. Json should only contain plugins compatible with 2.277.3 (example: configuration-as-code:1.50)

Actual:

1. Hit https://updates.jenkins.io/update-center.json?version=2.277.3
2. Get redirected to https://updates.jenkins.io/dynamic-stable-2.277.3/update-center.json
3. Json may contain plugins that are not compatible with 2.277.3 (example: configuration-as-code:1.51)