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

Travis build failing #2

Closed
craigmdennis opened this issue Feb 27, 2017 · 3 comments
Closed

Travis build failing #2

craigmdennis opened this issue Feb 27, 2017 · 3 comments
Labels

Comments

@craigmdennis
Copy link
Contributor

@balupton Everything works as expected but the Travis build is failing. I'm not sure what the issue is but happy to fix it if you can point me in the right direction.

@balupton
Copy link
Member

Seems all the docpad plugins are having the same issue. Do the npm release regardless. And I'll sort out the travis for all the plugins issue after my current batch of work.

@mikeumus mikeumus added the bug label Feb 27, 2017
@balupton
Copy link
Member

balupton commented Apr 9, 2017

@craigmdennis so the issue was due to the conventions not working for npm v3

I've released https://github.com/bevry/based which when run, will update the plugin conventions to the latest. However it requires secret tokens for use in the initial travis setup. As such, for now, I need to run it for each plugin. Will do it now for pug.

@balupton
Copy link
Member

balupton commented Apr 9, 2017

@craigmdennis okay, updated - from now on, to do a release, all you have to do is do the package.json version bump and the HISTORY.md entry, commit, and then run npm run our:release - full instructions in CONTRIBUTING.md

@balupton balupton closed this as completed Apr 9, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants