Bump SemanticVersioning from 2.0.2 to 3.0.0

[dependabot]

⚠️ Dependabot is rebasing this PR ⚠️

Rebasing might not happen immediately, so don't worry if this takes some time.

Note: if you make any changes to this PR yourself, they will take precedence over the rebase.

---

Bumps SemanticVersioning from 2.0.2 to 3.0.0.

Release notes

Sourced from SemanticVersioning's releases.

3.0.0

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 (a121c7ef9b51e89157c3da6b995efbdc61eb44d0)
• 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

3.0.0-beta2

What's Changed

• Add README to Nuget package by @​adamreeve in adamreeve/semver.net#59
• do not trim version name with strict mode by @​anatawa12 in adamreeve/semver.net#61

Full Changelog: adamreeve/semver.net@3.0.0-beta1...3.0.0-beta2

3.0.0-beta1

This is a beta version of the 3.0.0 version, which is a major version change due to introducing some breaking changes.

Breaking changes

• 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.
• 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.
• 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.
• Targets other than netstandard2.0 have been removed

Merged pull requests

• fix: 3.2.x should satisfied by 3.2.0-beta.1 by @​anatawa12 in adamreeve/semver.net#55
• Add tests from node-semver by @​anatawa12 in adamreeve/semver.net#56
• fix: versions prefixed with 'v' are parsed in strict mode by @​anatawa12 in adamreeve/semver.net#58

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

Commits

• cbd7461 Promote 3.0.0-beta1 to a stable 3.0.0 release (#67)
• d054250 Update upload-artifact and download-artifact actions (#66)
• 8d1b68c Update version to 3.0.0-beta2 (#62)
• 949d401 Do not allow leading and trailing whitespace in strict mode (#61)
• 620dc55 Add README to Nuget package (#59)
• ec3ad36 Update version to 3.0.0-beta1
• 94a76b0 Update build badge
• 48d840d Fix use of deprecated license url property
• 6191bd1 Add CI workflow for GitHub actions
• a121c7e Build and project tidy up
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[opensearch-trigger-bot]

The backport to 1.x failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-1.x 1.x
# Navigate to the new working tree
cd .worktrees/backport-1.x
# Create a new branch
git switch --create backport/backport-887-to-1.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 70b51413e7abe56d469a39b5e141a6438db0a988
# Push it to GitHub
git push --set-upstream origin backport/backport-887-to-1.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-1.x

Then, create a pull request where the base branch is 1.x and the compare/head branch is backport/backport-887-to-1.x.