PowerSync .NET SDK

Releasing

Ensure all changes you want to release are merged into main.
Ensure the changelog files for both Common and Maui have been updated with new, well-formatted version numbers.
- The release workflow obtains the version number by searching for the top-most version line (prefixed with ## ), stripping the prefix, and taking the remaining text as the version number. It does this for both changelogs.
- If a release only includes changes to PowerSync.Common, don't forget to also update PowerSync.Maui's changelog so that a new release is created that uses the updated version of PowerSync.Common.
- By convention, we generally update the changelog within the PRs that add the changes. This sometimes leads to the version number in the changelog being a version ahead of the released version (eg. latest released version is v0.0.3, but changelog has v0.0.4.)
Run the Release workflow on Github. This will:
- Extract version numbers from the changelogs.
- Create a release for both packages on Nuget.
- Create a Github release containing the changelog contents.

Ensure all changes you want to release are merged into main.
!! IMPORTANT !! Ensure the changelog files have release numbers ending in -dev.xxx, eg. 0.1.0-dev.1.
- If you don't add the suffix, the workflow might try to create a release with a version number you didn't expect.
Run the Create Dev Release workflow on Github, selecting the branch with your changes as the base branch.