-
Notifications
You must be signed in to change notification settings - Fork 697
WIP: Refactor publishing #350
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
Conversation
e6c5819 to
7258070
Compare
|
So I'm trying to figure out why this fails on linux 10, something with content type headers not being set... |
|
👍, but bump the minor version number when you release it. If it introduces the smallest bug, it will trouble people that depends on ~0.2.4. I suggest keeping this new 0.3 release in a new branch, just to simplify life for newcomers to the project, and merge when it is all done. |
|
I'm fine pushing it to an 0.3.0. Might be time for that bump soon anyways with the libgit changes from upstream. |
2dfad62 to
6188842
Compare
|
During the refactor a version check got missed, which usually caused a different version of http_parser to get pulled in for v10. That wasnt happening, causing a mismatch. |
cc3e106 to
d4bbb04
Compare
includes cleaning of npm registry based installs and a new debug build
d4bbb04 to
cad078e
Compare
|
Making a new PR for the 0.3 branch. |
So I've done quite a bit here.
npm run buildDebug