-
Notifications
You must be signed in to change notification settings - Fork 7.1k
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
Dependency aliases not working with semver logic #2794
Comments
apeschel
changed the title
Dependency aliases not working when using semver logic
Dependency aliases not working with semver logic
Aug 10, 2017
llsheldon
pushed a commit
to llsheldon/helm
that referenced
this issue
Aug 17, 2017
The alias functionality only works when a hardcoded version is used. Any use of semver logic causes unexpected behavior. I use version.IsCompatibleRange to check the dependency version. Closes helm#2794
lllsheldon
pushed a commit
to lllsheldon/helm
that referenced
this issue
Aug 25, 2017
The alias functionality only works when a hardcoded version is used. Any use of semver logic causes unexpected behavior. I use version.IsCompatibleRange to check the dependency version. Closes helm#2794
lllsheldon
pushed a commit
to lllsheldon/helm
that referenced
this issue
Aug 25, 2017
The alias functionality only works when a hardcoded version is used. Any use of semver logic causes unexpected behavior. I use version.IsCompatibleRange to check the dependency version. Closes helm#2794
lllsheldon
pushed a commit
to lllsheldon/helm
that referenced
this issue
Aug 25, 2017
The alias functionality only works when a hardcoded version is used. Any use of semver logic causes unexpected behavior. I use version.IsCompatibleRange to check the dependency version. Closes helm#2794
lllsheldon
pushed a commit
to lllsheldon/helm
that referenced
this issue
Aug 25, 2017
The alias functionality only works when a hardcoded version is used. Any use of semver logic causes unexpected behavior. I use version.IsCompatibleRange to check the dependency version. Closes helm#2794
llsheldon
added a commit
to llsheldon/helm
that referenced
this issue
Aug 25, 2017
The alias functionality only works when a hardcoded version is used. Any use of semver logic causes unexpected behavior. I use version.IsCompatibleRange to check the dependency version. Closes helm#2794
llsheldon
added a commit
to llsheldon/helm
that referenced
this issue
Aug 28, 2017
The alias functionality only works when a hardcoded version is used. Any use of semver logic causes unexpected behavior. I use version.IsCompatibleRange to check the dependency version. Closes helm#2794
llsheldon
added a commit
to llsheldon/helm
that referenced
this issue
Sep 1, 2017
The alias functionality only works when a hardcoded version is used. Any use of semver logic causes unexpected behavior. I use version.IsCompatibleRange to check the dependency version. Closes helm#2794
llsheldon
added a commit
to llsheldon/helm
that referenced
this issue
Sep 7, 2017
The alias functionality only works when a hardcoded version is used. Any use of semver logic causes unexpected behavior. I use version.IsCompatibleRange to check the dependency version. Closes helm#2794
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue found on v2.5.1
The alias functionality only works when a hardcoded version is used. Any use of semver logic causes unexpected behavior.
Expected behavior:
Example 1
All aliased dependencies use semver logic.
Given:
Produces
Example 2
Only one aliased dependency uses hardcoded version logic.
Given:
Produces:
Example 3
Mix of semver logic and hard coded versions.
Given:
Produces:
The text was updated successfully, but these errors were encountered: