[Release Checklist]: release 0.10.16

[digikata]

Release Checklist

The following checklist covers all the steps for running release.

For more detail, refer to RELEASE.md

• Create a new issue with this checklist template
• Review all the Getting Started and API docs. Verify if they are up to date or will need updates
• Inform team that release is about to begin
• Ensure no merges are in flight
• Create a PR for release
  • Update VERSION and CHANGELOG.md files (do not place a \n in the VERSION file, it breaks the CI)
  • Update CHANGELOG with replacement of the UNRELEASED date
  • Update dependency in connector template
  • Merge the PR
• Run the Release workflow in Github Actions (Retry at least once if failure)

If you are doing a prelease stop here before publishing crates. Only run publish crates for the finalized release.

• Verify that the crates publish to crates.io succeeds (Retry at least once if failure)
• Announce new release in Discord
• To close this issue, create a PR for post release updates and use release_template.md
  • Add form data template=release_template.md to the PR URL while creating in order to use template
  • e.g. https://github.com/infinyon/fluvio/compare/master...username:your-branch?expand=1&template=release_template.md
  • or gh pr create --template=release_template.md a closes issue #x in the body will automatically close this issue on merge.

Generating Release notes

To get a starting point for generating release notes. A git ref, or last release tag can also be used.

git cliff 673e60c0..HEAD > changes.md

# or use the previous release tag
git cliff v0.10.6..HEAD > changes.md