-
Notifications
You must be signed in to change notification settings - Fork 16
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
chore: Release 1.1.0 #12
Conversation
- Add type definitions (chaijs#11)
b60cc3a
to
e9d6cda
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ping @chaijs/assertion-error team for 1 more review.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
Let's get this merged! Thanks @demurgos 😄
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
Let's get this merged! Thanks @demurgos 😄
@lucasfcosta I believe we need to create a Release on GitHub for this. Do you wanna do the honors? |
Could you please send a message here so we get a notification once it's published? Thanks. |
@demurgos this has been released ✌ |
This commit bumps the version number (following #11 (comment)).
It is a semver minor update because type definitions are a feature in my opinion. Even if they don't change runtime, formalizing the documentation as types allows Typescript users to benefit from type checking.
cc @keithamus