https://github.com/code-423n4/2024-07-reserve/blob/3f133997e186465f4904553b0f8e86ecb7bbacbf/contracts/registry/VersionRegistry.sol#L54
From the version history of the Reserve protocol it appears that the protocol is using semantic versioning or a similar alternative.
This seems a use case that does not fit well with how VersionRegistry.latestVersion is updated: every time a new version is registered on VersionRegistry,  latestVersion will point to that version.
In the event that the protocol releases 4.0.0 and shortly after 3.4.2, then latestVersion will incorrectly point to 3.4.2.
Consider adding a boolean flag to the registerVersion function, allowing the caller to specify whether latestVersion should be updated or not.
