chore(deps): update dependency semanticversioning to v3

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
SemanticVersioning	2.0.2 → 3.0.0

---

Release Notes

adamreeve/semver.net (SemanticVersioning)

v3.0.0

Compare Source

This is a new major version release and introduces breaking changes in behaviour.

What's Changed

• Versions prefixed with v, for example v1.2.3, are now considered invalid, and only allowed in loose mode, in accordance with the semantic versioning specification (#​58)
• Pre-release versions are now considered to satisfy version ranges with an x or * when includePrerelease is true. For example the range 3.2.x is now satisfied by 3.2.0-beta.1 when previously it was not (#​55)
• Inconsistent behaviour of caret ranges has been fixed when includePrerelease is true and the major version is zero. For example, previously the range ^0.2.3 was satisfied by 0.2.3-alpha when includePrerelease is true but now it is not. The behaviour when the major version is non-zero has not changed, for example ^1.2.3 is not satisfied by 1.2.3-alpha (#​56)
• Targets other than netstandard2.0 have been removed (a121c7e)
• Leading and trailing whitespace are no longer allowed in strict mode (#​61)
• The README has been added to the Nuget package (#​59)

Full Changelog: adamreeve/semver.net@2.0.2...3.0.0

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[github-actions]

👋 Hi! It looks like you modified some files in the Detectors folder.
You may need to bump the detector versions if any of the following scenarios apply:

• The detector detects more or fewer components than before
• The detector generates different parent/child graph relationships than before
• The detector generates different devDependencies values than before

If none of the above scenarios apply, feel free to ignore this comment 🙂