Skip to content

Conversation

@coolaj86
Copy link

  • include proper versions for deps
  • bump to 1.0.0-alpha (breaking changes allowed)

If not a proper bump to 1.0.0-alpha this should at least be bumped to 0.1.0 so that there's some scale to version changes.

* include proper versions for deps
* bump to 1.0.0-alpha (breaking changes allowed)

If not a proper bump to 1.0.0-alpha this should at least be bumped to 0.1.0 so that there's some scale to version changes.
michielbdejong added a commit that referenced this pull request May 28, 2015
@michielbdejong
Copy link
Owner

OK, can you test current master (5d4b1e6) and confirm it works? Then I'll add a changelog file and tag 0.1.0. We'll do the common "pre-semver" practice to bump up the pre-1.0 minor version whenever there is a breaking change in the API. So we'll stay on 0.1.X until we change the API, and then go to 0.2.X. The '0.' prefix here only indicates that it's a very young bit of software. :) Do you agree?

@coolaj86
Copy link
Author

coolaj86 commented Jun 8, 2015

I'm round-robin-ing between the aspects of the project I'm working on. Eventually I will get back to this and test it - just so you know that I haven't forgotten.

@michielbdejong
Copy link
Owner

I now pushed 0.0.5 to npm with the 'deprecated' message in the readme: https://www.npmjs.com/package/node-letsencrypt

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants