LTS Version received forced update post 1/24 release

https://www.jenkins.io/changelog-stable/ - version 2.426.3

We have had this version of Jenkins since Release in January.  I added a completely unrelated plugin to our Jenkins and it was failing to startup due to the below:

2024-03-14 20:26:59.231+0000 [id=37] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin Credentials Plugin v1337.v60b_d7b_c7b_c9f (credentials)
java.io.IOException: Failed to load: Credentials Plugin (credentials 1337.v60b_d7b_c7b_c9f)
 - Update required: Configuration as Code Plugin (configuration-as-code 1746.vf1673cfe690a) to be updated to 1775.v810dc950b_514 or higher
 
The credentials plugin version in the error looks to have been released 2 weeks ago.
 
I am hoping to get confirmation that this is an expected behavior for an LTS version to have updates pushed post release?
 
While updating the CASC version did address the error, there is no documentation (unless I missed it) that an update was pushed to the version released in January.
In our case we have a 'base' version of Jenkins we maintain with a set of standard plugins we install/upkeep (like casc) then then other teams use this base image for their own Jenkins instances and can add plugins on top as needed/maintain themselves.  So an update to an exiting LTS version would then break all other teams for an error that has nothing to do with their changes.