Updating package.json file for 0.4.2 release

[lirantal]

Preparing for 0.4.2 release, updating relevant files.

[lirantal]

@codydaig any other updates we need?

[codydaig]

@lirantal Don't forget to update the bower.json.
Also, I would run the changelog and merge that in with this PR so it's in the release tag.

I would like to vote to make 0.4.x a branch after the release but before we start merging 0.5 stuff in. I think there's a lot of people that picked up 0.4 and if there's any bugs, it gives us the opportunity to fix those bugs and release patches.

The generator does need to be updated, however, it's on hold until @ilanbiala hashes out a refactor for the built in fs to use some other module. There's a bunch of work that we still need to do to the generator, but it's on hold over a discussion over using this.fsversus the built in fs.

[lirantal]

@codydaig what is there to update in bower.js?
and are there specific arguments to provide to conventional-changelog to get it to create the changelog in our desired format?

[codydaig]

@lirantal We must have removed it, but I swore there was a version in the bower.json as well. Glad it's gone now! :)

and I put the exact command that needs to get ran in the CONTRIBUTING.md document.

[lirantal]

@codydaig I did run it as follows conventional-changelog -r 1 > CHANGELOG.md although git shows a great diff between the former and new file and I suspected that something was wrong. Maybe it's just spaces or something else.

[ilanbiala]

@lirantal it looks for all the commits between 2 tags, so you would have to tag 0.4.2 first and then rerun this and you should see it work.

[codydaig]

@lirantal I will run the changelog today and make a PR to your branch for you. If there's something that I documented wrong, I will also correct that.

[codydaig]

@lirantal @ilanbiala I made a PR to @lirantal's branch with the updated changelog.

[lirantal]

Hey guys,
Was a bit busy with work, and some hackathon that was going on.

I'll get back to this really quick!

[lirantal]

weird, no idea why it's having conflicts on this branch while I can merge it with my master branch.

[lirantal]

had to merge from master to resolve conflicts.

[ilanbiala]

How come these aren't being parsed out into a subheading?

[lirantal]

donnu, @codydaig ?

[ilanbiala]

@lirantal clarified, it's fine for this.

[ilanbiala]

@lirantal that's fine, just make sure to rebase and squash. I'm curious about why the changelog didn't come out with a subheading for bugs though. Ideas?

[codydaig]

@ilanbiala It did, but I removed them since there was only one or two things that fell under bugs. It only works with the new style and since the new style wasn't implemented until the very end most commits don't fall under a heading.

[ilanbiala]

Oh okay.

[lirantal]

@ilanbiala for whatever reason when I'm rebasing without a merge commit it is conflicting with master branch and we're unable to merge through Github. So I'll re-base again with a merge commit and merge for the 0.4.2 release.

[ilanbiala]

This should have the proper CLI command that prepends it

[codydaig]

This is probably where the merge conflict is.

[lirantal]

I'll go ahead and merge as is with the merge-commit.

[codydaig]

LGTM