bump to 1.0.0 for semver support
See original GitHub issueNot a bug, just a friendly request. 😄
By bumping to 1.0.0
it means minor and patch releases are backwards compatible and projects that depend on depcheck
like npm-check can easily upgrade.
If you think the API is not stable enough for a 1.0.0
I still wouldn’t worry. I personally don’t mind frequent major bumps - it tells me the API is evolving and that’s great too. Browserify is on version 13.x.y.
On a totally different note, I just noticed the release notes with each deploy, thank you for taking the time to do this! I wish I could be as disciplined.
Issue Analytics
- State:
- Created 7 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
When using semver when to upgrade/bump to 1.0.0 (stable)
The development team decides when they have version 1.0.0. It is possible for a project to remain in experimental/prototype mode for very ...
Read more >Semantic Versioning 1.0.0
Having to bump major versions to release incompatible changes means you'll think through the impact of your changes, and evaluate the cost/benefit ratio ......
Read more >Convention: how to get from 0.0.0 to 1.0.0 · Issue #363 - GitHub
Assign a version to your project -- obviously SemVer-compatible version in 0.y.z range. Have at least some "tongue-in-cheek" semantics to that version. Make...
Read more >What is the significance of reaching major version 1.0.0?
I don't think If the project is using Semantic Versioning, then a 1.0.0 release means that the public API is stable. is true....
Read more >Version Incrementing - GitVersion
Semantic Versioning is all about releases, not commits or builds. ... major version will merely bump the minor (eg from 0.2.0 to 0.3.0...
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
Next one then, I wanted to add a bunch of stuff before going 1.0 but I guess after 6 years we can say that it is time
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.