🚀 Feature: Enforce exact version

[ph55]

Feature Request Checklist

• I have pulled the latest main branch of the repository.
• I have searched for related issues and found none that matched my issue.

Overview

Why

Not all Open Source project follow Semantic Version guidelines properly. And even patch versions might break production code.

How

Add option to valid-version rule to enforce exact version.
Example: 1.2.3 - valid (exact), ^1.2.3 - invalid (not exact).

Additional Info

No response

[michaelfaith]

Thanks for the suggestion. A couple of things worth noting

1. valid-version doesn't govern the conventions of versions in the various dependency groups, it governs the validity of the package's version field. So this feature wouldn't really belong as an enhancement to valid-version
2. We're already working on this capability as part of a new rule restrict-dependency-ranges: feat: new restrict-dependency-ranges rule #998 This will cover the use case you mentioned and several more.

Take a look and feel free to weigh in and let us know what you think. Closing this for now, as duplicated by #959