-
Notifications
You must be signed in to change notification settings - Fork 112
4.2.1 #233
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
4.2.1 #233
Conversation
@austince I believe you need to push a tag so travis deploys to npm. |
@vieiralucas sure, I can draft a new release soon. Thanks for the review + merge! |
@keithamus @JamesMessinger, since you guys usually do the releasing, do you mind just giving a quick 'ok' before I go ahead and publish a GH release? |
How does the "build" script in package.json get run? I don't see it being called in the CI script, so does it have to be run manually and committed as part of this PR? As far as I can tell, the CI script will just deploy whatever is checked into git. And looking at the last-modified dates of the files, it seems like the build script hasn't been run in at least 4 months. |
My understanding is that it will run for commits that are tags. The deploy job will run if the commit is a tag. |
Right, the deploy script will run for tagged commits. But all the deploy script does is run @keithamus - Or am I missing something? |
@JamesMessinger you're correct - all that happens is tagged commits get Typically the release cycle starts by running I've gone and made https://github.com/chaijs/chai-http/releases/tag/4.2.1 which should get deployed shortly. |
I've run |
@JamesMessinger That makes sense 😄 |
Perhaps we could use something like semantic-release to save some of Keith's time? |
Chore commit for version 4.2.1
Fixes: