Skip to content
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

Increment version to 2.0.1. #374

Merged
merged 1 commit into from Feb 23, 2015
Merged

Increment version to 2.0.1. #374

merged 1 commit into from Feb 23, 2015

Conversation

@jmm
Copy link
Contributor

@jmm jmm commented Feb 23, 2015

See /issues/373

keithamus added a commit that referenced this issue Feb 23, 2015
Increment version to 2.0.1.
@keithamus keithamus merged commit 45f9e6a into chaijs:master Feb 23, 2015
1 check passed
Loading
@keithamus
Copy link
Member

@keithamus keithamus commented Feb 23, 2015

Thanks for this @jmm. Really appreciated. While trying to release 2.0.1 I noticed there is a new feature that has been merged, so I've bumped the release to 2.1.0. Your commit is still in mainline and you've been credited on the homepage, thanks for your efforts 😄

Loading

@jmm
Copy link
Contributor Author

@jmm jmm commented Feb 23, 2015

Thanks @keithamus.

Loading

@jmm
Copy link
Contributor Author

@jmm jmm commented Feb 24, 2015

@keithamus I noticed that all of the < v2 tags are in the format major.minor.patch, then there was v2.0.0, and the next one is back to 2.1.0. Just wanted to point this out in case you were wanting to start a new format from 2.0.0 onward.

Loading

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

2 participants