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 a 'metadata' version instead of the package version #44

Closed
ThierryO opened this issue Jun 21, 2019 · 3 comments
Closed

Use a 'metadata' version instead of the package version #44

ThierryO opened this issue Jun 21, 2019 · 3 comments
Labels
enhancement New feature or request
Milestone

Comments

@ThierryO
Copy link
Member

Currently the package version is stored in the metadata. Upgrading the package requires upgrading the metadata. Using a separate metadata version instead would ease this requirement.

@ThierryO ThierryO added the enhancement New feature or request label Jun 21, 2019
ThierryO added a commit that referenced this issue Jul 3, 2019
@krlmlr
Copy link

krlmlr commented Jul 19, 2019

With semantic versioning, maybe storing (and comparing) major-minor would be sufficient?

@ThierryO
Copy link
Member Author

Yes, that is the current idea.

@ThierryO ThierryO added this to the Version 0.1.1 milestone Aug 12, 2019
@ThierryO ThierryO mentioned this issue Aug 14, 2019
ThierryO added a commit that referenced this issue Aug 14, 2019
@ThierryO
Copy link
Member Author

fixed in #51

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants