1.16 Release

[ikatyang]

This issue tracks the 1.16 release progress. I should be able to write the blog post next week but feel free to take this work over if you're interested (cc @prettier/core).

• prepare
  • Complete milestone items
  • Run on other projects to check for regressions
    • npm install prettier/prettier
  • Write release notes
    • add a Markdown file named YYYY-MM-DD-version.md in website/blog
      • -> docs(blog): 1.16 release #5752
    • prs-merged-since may be useful
• publish
  • Run release script
• postpublish
  • Merge release notes
  • Wait for release notes to deploy
  • Tweet from @PrettierCode account via TweetDeck
  • Close milestone
  • Send schema PR generated by scripts/generate-schema.js to SchemaStore if we added a new option.
  • Update the release checklist with possible changes

[j-f1]

For the release notes, I’m wondering if we should make a work-in-progress blog post for the next release and ask everyone to add information from their PR to it so we don’t need to write it all after the fact.

[suchipi]

@j-f1 great idea

[lipis]

Once the template is ready post let's update the description to link to it.

[duailibe]

The problem is we don't know for sure when we'll do a minor or a patch release..

But sure once we decide the next release will be a minor, all new PRs could already add "itself" to the WIP blog post.

[j-f1]

If we decide to make a patch release, we can just remove the relevant PRs from the WIP blog post.

[ikatyang]

Sounds good, we could add an Unreleased section in the CHANGELOG.md (or something similar) and move them to the blog post if we'd like to release a minor version, it should speed up our release process.

[ikatyang]

WIP blog post -> #5752

[ikatyang]

Done. https://twitter.com/PrettierCode/status/1086897608805609472

[lydell]

Thanks, @ikatyang. Awesome work, as always! 💯