Skip to content

Fix dependency version range - #111

Merged
Exelord merged 1 commit into
minutebase:masterfrom
ondrejsevcik:patch-1
Jan 16, 2020
Merged

Fix dependency version range#111
Exelord merged 1 commit into
minutebase:masterfrom
ondrejsevcik:patch-1

Conversation

@ondrejsevcik

Copy link
Copy Markdown
Contributor

Fixed version range is unnecessary in this case and will cause troubles to consumers.

Fixed version range is unnecessary in this 
case and will cause troubles to consumers.
@Exelord

Exelord commented Jan 16, 2020

Copy link
Copy Markdown
Collaborator

I can't agree here :/ We cannot guarantee this package will be compatible with every future version of its dependency. We can put trust on this but then things are "released" without testing and are out of the control.

However, I think, we can use ~ as it will use the latest 0.0.X fix release of the package. Im still very skeptical to it, as I think more troubles can make auto-updated dependency than strictly bound version

@Exelord
Exelord merged commit 717bb5e into minutebase:master Jan 16, 2020
@ondrejsevcik

Copy link
Copy Markdown
Contributor Author

Version ranges is a topic on it's own, but fixed versions are almost never good in library package.
When every library would have a fixed version numbers, I would have a project with dozens identical dependencies in different versions that will most likely not play nice together.

@Exelord Exelord added the bug label May 27, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants