Feature request: Add ability to NOT mark GitHub releases as latest #551
Description
When creating a GitHub release, the standard behavior is that it gets marked as the latest release. This is the release that is displayed on the front page of the repo, before you navigate to the releases page proper.
Changesets already handles prereleases, by marking them as a prerelase automatically if the branch is in pre mode. However, there is also a case where you want to publish a bugfix/patch to an older version of your package(s). In that case, you probably don't want that release to show up as the newest release when there is a newer version available (that presumably also has the fix).
Suggestion:
Add a flag markGithubReleaseAsLatest (or similar) that defaults to true. This matches the behavior in Octokit, and should make it very easy to implement.
I'll be happy to create a PR implementing this if needed.
Further info:
The relevant parameter of the GitHub API endpoint is make_latest, which defaults to "true" and can be either of "true", "false" or "legacy"