Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(e2e): Setting e2e tests to be a specific version #2207

Merged
merged 1 commit into from
Oct 14, 2021

Conversation

jamdavi
Copy link
Member

@jamdavi jamdavi commented Oct 14, 2021

Since the versions of the packages are based off of existing versions present in the Nuget repository, Nuget will honor the non suffixed versions first.

See semantic versioning.

Taken from the page above

Whatever suffixes you use, however, NuGet will give them precedence in reverse alphabetical order:

1.0.1
1.0.1-zzz
1.0.1-rc
1.0.1-open
1.0.1-beta.12
1.0.1-beta.5
1.0.1-beta
1.0.1-alpha.2
1.0.1-alpha

As shown, the version without any suffix will always take precedence over pre-release versions.

Leading 0s are not needed with semver2, but they are with the old version schema. If you use numerical suffixes with pre-release tags that might use double-digit numbers (or more), use leading zeroes as in beta.01 and beta.05 to ensure that they sort correctly when the numbers get larger. This recommendation only applies to the old version schema.

@jamdavi jamdavi changed the title Setting e2e tests to be a specific version fix(e2e): Setting e2e tests to be a specific version Oct 14, 2021
@jamdavi jamdavi merged commit 449074d into preview Oct 14, 2021
@jamdavi jamdavi deleted the jamdavi/updatee2e branch October 14, 2021 23:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants