`outdated` property says that versions are out of date even when the semver matches

[Matthew Andrews]

E.g. https://www.versioneye.com/api/v2/projects/5603d4ef4b3478000b011aa4?api_key=xxx

body-parser

version_current: "1.14.1",
version_requested: "1.14.0",
comparator: "^",
unknown: false,
outdated: true

The same is true on the VersionEye UI so perhaps it's just misundestanding of what should be expected.

[Robert Reiz]

I just clicked the "Re Parse Now" button and it's fine now. Look here: https://www.versioneye.com/user/projects/5603d4ef4b3478000b011aa4

VersionEye does not re parse the whole file on each view or each API GET operation, that would be too time consuming. Every time you fetch the Project via the API you get cached values. The project gets "re parsed":

• once a day via a scheduler
• on each git push if you are using the VersionEye GitHub Hook
• if you trigger a "re parse" manually via Web UI or API.

Hope that helps for clarification.