Add support for make_latest property

[samueljseay]

Closes #297

This PR supports the make_latest property of the releases REST API.

I've tested this on my fork and it works well for me. I've kept the behaviour with previous versions by defaulting to true for this property.

I also:

• updated a dependency via npm audit fix to fix a high risk npm security flag
• updated tests
• updated documentation

Please note: make_latest is oddly a string which is why parseConfig returns a string for this property. See the docs.

[softprops]

Thanks!

There's some nuance in the docs that give me pause for the default though

Drafts and prereleases cannot be set as latest.

Does this mean those creating drafts and prereleases would start getting errors with this actions new default?

Defaults to true for newly published releases. legacy specifies that the latest release should be determined based on the release creation date and higher semantic version.

I'm wondering if legacy is the better default for backwards compat or event better leaving it undefined as a default unless a user specifies it explicitly to guarantees compatibility with current behavior

[samueljseay]

Leaving undefined sounds probably better I agree. I'll add a change for that.

[samueljseay]

@softprops I've adjusted the behaviour to default to undefined.

[jackalcooper]

Hi, will this PR be merged?

[DameonSmith]

Would also like to see this feature.

[damian3031]

I'm also interested in this feature

[DariuszPorowski]

@softprops any updates on this? :)

[koehlecn]

@softprops Please, can your merge this PR? That would be great! Thank you!

[leon1995]

any news on this?

[kdmiltner]

Could support to update an existing tag with make_latest be added? Or would this would to set an existing tag to the latest? https://github.com/softprops/action-gh-release/issues/385

[theo-issarni-wmx]

Any news on this ? That would be great !

[softprops]

@samueljseay thanks for the pull and sorry for the delay

[softprops]

this should be available in the new v2 tag