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

Make type resolution respect semver semantics #49

Closed
1 of 3 tasks
jackgr opened this issue Nov 12, 2015 · 0 comments
Closed
1 of 3 tasks

Make type resolution respect semver semantics #49

jackgr opened this issue Nov 12, 2015 · 0 comments
Assignees

Comments

@jackgr
Copy link
Contributor

jackgr commented Nov 12, 2015

Currently, we require an exact match of the version to resolve chart reference. Instead, we should use semver semantics, meaning that:

  • We should prevent breaking changes. For example, a reference to redis:v1,0,0 cannot be satisfied by redis:v2.0.0.
  • We should resolve chart references to compatible versions, defined as versions with the same major and minor number, plus higher patch number . For example, a reference to redis:v1.0.0 should resolve to redis:v1.0.1.
  • We should take the latest compatible version. For example, if redis:v1.0.1 and redis:v1.0.2 are available, a reference to redis:v1.0.0 should resolve to redis:v1.0.2.
@jackgr jackgr modified the milestone: Sprint 14 Jan 4, 2016
@jackgr jackgr added the helm label Jan 4, 2016
@jackgr jackgr modified the milestones: Sprint 14, Sprint 15 Jan 27, 2016
@jackgr jackgr modified the milestones: Sprint 15, Sprint 16 Feb 8, 2016
@jackgr jackgr modified the milestones: Sprint 16, Sprint 17 Feb 25, 2016
@jackgr jackgr modified the milestone: Sprint 17 Mar 8, 2016
@jackgr jackgr self-assigned this Apr 5, 2016
@jackgr jackgr added priority/P2 and removed helm labels Apr 11, 2016
MichaelMorrisEst pushed a commit to Nordix/helm that referenced this issue Nov 17, 2023
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

No branches or pull requests

2 participants