Release v0.3.0 (#306)

Author: abhinav

.changes/unreleased/Added-20240723-222630.yaml

@@ -0,0 +1,8 @@
+## <a name="v0.3.0">v0.3.0</a> - 2024-07-24
+### Added
+- Authentication: If a secure storage is not available, fall back to plain text, but warn the user about it.
+- gs branch submit: Add short form `-c` for the `--fill` flag.
+### Removed
+- branch delete: Drop short form `-f` for the `--force` flag.
+### Fixed
+- commit split: Fix bug where canceling the split would fail to revert to original state.

.changes/unreleased/Added-20240724-121944.yaml

@@ -5,6 +5,15 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html),
 and is generated by [Changie](https://github.com/miniscruff/changie).
 
+## <a name="v0.3.0">v0.3.0</a> - 2024-07-24
+### Added
+- Authentication: If a secure storage is not available, fall back to plain text, but warn the user about it.
+- gs branch submit: Add short form `-c` for the `--fill` flag.
+### Removed
+- branch delete: Drop short form `-f` for the `--force` flag.
+### Fixed
+- commit split: Fix bug where canceling the split would fail to revert to original state.
+
 ## <a name="v0.2.0">v0.2.0</a> - 2024-07-23
 ### Added
 - Publish pre-built Linux ARM binaries.

.changes/unreleased/Fixed-20240723-172718.yaml

@@ -47,7 +47,7 @@ and the position of the current branch in it.
 
 ### Non-interactive submission
 
-Use the `--fill` flag (or `-c` since <!-- gs:version unreleased -->)
+Use the `--fill` flag (or `-c` since <!-- gs:version v0.3.0 -->)
 provided by all the above commands
 to fill in the PR information from commit messages
 and skip the interactive prompts.

.changes/unreleased/Removed-20240724-120607.yaml

@@ -210,7 +210,7 @@ On Linux, it uses the [Secret Service](https://specifications.freedesktop.org/se
 which is typically provided by [GNOME Keyring](https://specifications.freedesktop.org/secret-service/latest/).
 <!-- TODO (if we enable Windows): On Windows, it uses the Windows Credential Manager APIs. -->
 
-Since version <!-- gs:version unreleased -->,
+Since version <!-- gs:version v0.3.0 -->,
 if your system does not provide a secure storage service,
 git-spice will fall back to storing secrets in a plain-text file
 at `$XDG_CONFIG_HOME/git-spice/secrets.json` or the user's configuration directory.