-
Notifications
You must be signed in to change notification settings - Fork 5
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
Version numbers do not match #15
Comments
Wow, never thought of that. So, each small commit would require to bump versions in those two files? That's mess. |
Not necessarily each commit. But each tagged release, yes. |
There is no need in duplication of a tag within the code itself. It's just a waste of time (waste bigger than re-fetching). Version locking works perfectly with tags-only approach - shards installed and udpated correctly and the repository isn't bloated with useless bumps. Your issue looks more like Or you can try to convince me more 😃 |
You're right, updating |
Version information
0.25.0
0.2.2
Problem summary
The version numbers contained within code/metadata do not match the git tag. This causes funny behavior in
shards
, For example, running$ shards check
in a project which depends on migrate.cr will always show that the dependencies are not satisfied, which will cause it to re-fetch all dependencies (this is slow and annoying, especially with lots of deps)Mismatched version locations
The text was updated successfully, but these errors were encountered: