You have a package, "Foo", at version 1.0.1. This version is added to the Editor manifest and therefore appears in Package Manager UI with the Verified tag. If you then push a new package of Foo that bumps the patch version to 1.0.2, this version will get tagged as Verified in Package Manager UI, even though version 1.0.1 is still the version specified in the editor manifest.

This only happens when bumping the patch version number, not the major or minor version numbers.

1. Install Unity 2019.1.0b8
2. Open Unity
3. Create a new project with any settings
4. Once the project has been created, open the Package Manger UI
5. Find In App Purchasing in the package list
6. Compare the detail view of versions 2.0.1 and the latest 2.0.x

Expected Result:
Version 2.0.1, which is included in the editor manifest, is marked as Verified.

Actual Result:
The latest 2.0.x version is marked as Verified, even though it is not specified in the Editor Manifest.

Tested on Windows.

This is not a regression, and has been an issue for as long as the Package Manager has been around.