Hey,

This idea is similar to #322 and they may be considered as a single issue.

Releases created by the action do not specify make_latest param for the createRelease call and the default behavior of Github is

Defaults to true for newly published releases.

With a repository being a host to many packages the Latest release doesn't necessarily mean the most recently published package. In my particular case none of the packages should claim the Latest release status. The project release workflow that we consider to be the Latest is managed separately from the changeset publishing workflow.

I'm happy to contribute with the code change or to learn that this is not the direction you envisioned for this action to take.

Possible solution

1. Extend the action to inputs to allow set make_latest to false when a new Github release is created
2. Always create a release with make_latest set to false (potentially a breaking change to some users)

Considered alternative

Set createGithubReleases to false and create releases outside of this action