Read the `sdk/kronk/kronk.go` file and find the version information from
the `Version` variable. That variable will contain the new latest version.

We need release notes for the next release so please look at all the changes
in git we made since the last tagged version.

Copy the final markdown into the clipboard.

Please use the release note template below to learn what sections are required
and the format to use.

RELEASE NOTE TEMPLATE

# Release Notes - vX.YY.Z

**Release Date:** <Month-Name DD, YYYY>

## Overview

Version X.YY.Z brings <FILL IN THE DESCRIPTION>

## Detailed Changes

### New Features

#### Feature <NAME>

- **Author:** <NAME>
- <ITEM 1>
- <ITEM 2>
- <ITEM 3>

### Improvements

#### Improvement <NAME>

- **Author:** <NAME>
- <ITEM 1>
- <ITEM 2>
- <ITEM 3>

#### Library Updates

- **Author:** <NAME>
- <ITEM 1>
- <ITEM 2>
- <ITEM 3>

### Bug Fixes

#### Bug Fix <NAME>

- **Author:** <NAME>
- <ITEM 1>
- <ITEM 2>
- <ITEM 3>

### Documentation

#### Documentation <NAME>

- **Author:** <NAME>
- <ITEM 1>
- <ITEM 2>
- <ITEM 3>

### Dependencies

#### Dependency <NAME>

- <ITEM 1>
- <ITEM 2>
- <ITEM 3>

### Statistics

| Category      | Count |
| ------------- | ----- |
| Total Commits | INT   |
| New Features  | INT   |
| Improvements  | INT   |
| Bug Fixes     | INT   |
| Documentation | INT   |

**Contributors:**

- <NAME 1>
- <NAME 2>
- <NAME 3>

### Upgrade Notes

#### Breaking Changes

<NOTES> OR NONE

#### Migration

<NOTES> OR No migration required

#### Recommended Actions

- <ITEM 1>
- <ITEM 2>
- <ITEM 3>
