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

Use version: ~> 1.0, remove conditions: v1 #4162

Merged
merged 1 commit into from
Oct 9, 2019
Merged

Use version: ~> 1.0, remove conditions: v1 #4162

merged 1 commit into from
Oct 9, 2019

Conversation

svenfuchs
Copy link
Contributor

The version requirement = 0 advertised in early development stages was an unfortunate choice, as this is going to be the opt-out once the new build config validation feature will be rolled out further. Please use ~> 1.0 instead.

The conditions version v1 is now the default, so this key can be removed.

The version requirement `= 0` advertised in early development stages was an unfortunate choice, as this is going to be the opt-out once the new build config validation feature will be rolled out further. Please use `~> 1.0` instead.

The conditions version `v1` is now the default, so this key can be removed.
Copy link
Member

@asvetlov asvetlov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks.
Will merge after CI finishing

@asvetlov asvetlov merged commit f104e75 into aio-libs:master Oct 9, 2019
asvetlov pushed a commit that referenced this pull request Oct 9, 2019
The version requirement `= 0` advertised in early development stages was an unfortunate choice, as this is going to be the opt-out once the new build config validation feature will be rolled out further. Please use `~> 1.0` instead.

The conditions version `v1` is now the default, so this key can be removed.
(cherry picked from commit f104e75)

Co-authored-by: Sven Fuchs <me@svenfuchs.com>
asvetlov added a commit that referenced this pull request Oct 9, 2019
The version requirement `= 0` advertised in early development stages was an unfortunate choice, as this is going to be the opt-out once the new build config validation feature will be rolled out further. Please use `~> 1.0` instead.

The conditions version `v1` is now the default, so this key can be removed.
(cherry picked from commit f104e75)

Co-authored-by: Sven Fuchs <me@svenfuchs.com>
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.

2 participants