Should CLI version be bumped after API is?
See original GitHub issueSo whenever we bump the API should we also bump the CLI version? This is currently not the case as CLI has clean-css 4.x
as dependency since API interface does not change. However not updating CLI leads to a problem when it has to be updated by reinstalling it, see https://github.com/jakubpawlowicz/clean-css-cli/issues/4
Bumping CLI also implies these:
- Whenever there’s a bug in CLI it gets a patch version bump which will eventually lead to different API and CLI versions
- Whenever API gets a minor version bump so does CLI
I just want to know what is the good practice here.
Thoughts?
Issue Analytics
- State:
- Created 7 years ago
- Comments:6
Top Results From Across the Web
What Semantic Version increment to use for a filename change?
Since this is a backward incompatible API change, you should bump to 2.0.0. Changing the name of a command line app is backward...
Read more >bump-cli - npm
The Bump CLI is used to interact with your API documentation hosted on Bump by using the API of developers.bump.sh. Latest version: 2.4.1, ......
Read more >node.js - NPM: How to get bumped version in my CLI command?
TL;DR The answer is: Use version instead of preversion in npm-scripts. You can found more details here in explanation of scripts order.
Read more >Semantic Versioning Sucks! Long Live Semantic Versioning
We run the cmp goal during CI and releases which will fail if there is a breaking change (or if a minor version...
Read more >theogravity/version-bump - GitHub
the bump parameter of the cli strategy is set to minor , so the minor version will bump; after the strategy bumps minor,...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Let’s do this.
Here’s an example from babel-cli which bumps patch version when a dependent package is bumped too: https://github.com/babel/babel/commit/368485828fff8aa0341b779776cc41a013577648#diff-e918bc613bd1a4e122e36dcda10c7cb4 and nyc: https://github.com/istanbuljs/nyc/compare/8f7af3a5acb87f1380f18d6c516a3439610d12e4...e03cd4803872d4650d19171239d60c2feef2fc3c
I think we should be doing it too.