Use the most recently released version when comparing versions

[hawkrives]

The prior behavior would error if you had an "unreleased" section at the top of your changelog.

I like to keep the section there, even empty, so that I don't have to remember to add it back in when I need to add an entry.

This finds the first changelog entry with a non-null version, rather than just the first changelog entry.

[ungoldman]

Thanks @hawkrives, makes sense to me!

Array.prototype.find() is ES6+, would you be willing to rewrite that line to support older Node versions? Lots of people still using 0.10 & 0.12 out there.

[ungoldman]

Looks like the test is failing in iojs too: https://travis-ci.org/ngoldman/gh-release/jobs/84983915

I need to update .travis.yml to target 0.10, 0.12, and stable (4). Reasoning for covering all those versions is here:

ungoldman/module-init#25 (comment)

[hawkrives]

Sure thing! I was trying to figure out why that wasn't working… guess I'm too used to es6.

Is ES5 OK for a target?

[ungoldman]

result.versions.filter(function (release) { return release.version !== null })[0] is a little less elegant but would probably do the trick.

[hawkrives]

That's pretty much what I was thinking. Crossing fingers...

[ungoldman]

@hawkrives yeah that's fine, most of ES5 has been supported in v8 for a long time. http://kangax.github.io/compat-table/es5/ helps me remember what's what (blessings unto @kangax).

[hawkrives]

Indeed. Would you like a second PR for updating .travis.yml for 0.10, 0.12, and stable, or would you rather do that yourself?

[ungoldman]

Thanks @hawkrives! I'll take care of the .travis.yml versions.

[hawkrives]

Thanks!