fix: Restrict downgrade checks only to Docker versioning scheme

[zharinov]

Changes

Context

Documentation (please check one with an [x])

• I have updated the documentation, or
• No documentation update is required

How I've tested my work (please select one)

I have verified these changes via:

• Code inspection only, or
• Newly added/modified unit tests, or
• No unit tests but ran on a real repository, or
• Both unit tests + ran on a real repository

[renovate-release]

🎉 This issue has been resolved in version 37.426.3 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)
• 37.426.3

Your semantic-release bot 📦🚀

[viceice]

do we now know it's only happening on docker versioning?

[zharinov]

do we now know it's only happening on docker versioning?

It's not proven, but so far, only Docker-based versions were affected. And we have bunch of weird versioning schemes, which may be affected by our patch, so for now it's reasonable to restrict it only for Docker ones.

[viceice]

do we now know it's only happening on docker versioning?

It's not proven, but so far, only Docker-based versions were affected. And we have bunch of weird versioning schemes, which may be affected by our patch, so for now it's reasonable to restrict it only for Docker ones.

ok, next time please add this information to the PR description or link to relevant issue or discussion 🙃