Release v0.10.0 (#539)

.changes/v0.10.0.md

@@ -0,0 +1,19 @@
+## <a name="v0.10.0">v0.10.0</a> - 2025-01-02
+
+This release addresses a long-standing limitation of navigation comments:
+they were limited only to open CRs.
+With the help of [@VenelinMartinov](https://github.com/VenelinMartinov),
+git-spice will now retain history of merged downstack CRs when posting navigation comments.
+
+### Added
+- commit create: Add `--fixup` flag to create fixup commits. You can use `git rebase --interactive` or `gs branch edit` to combine these fixup commits into their targets.
+- rebase continue: Add `--[no-]edit` flag to specify whether an editor should open to change the commit message. Defaults to the value of the `spice.rebaseContinue.edit` configuration option if set, or true if not.
+- Add `--no-verify` flag to bypass pre-commit and commit-msg Git hooks for commands that create new commits. This includes 'commit create', 'commit amend', 'commit split', and 'branch create'.
+- state: Track version of the state store layout in use. This should be a no-op for users, but it protects against future changes to the layout.
+- submit: Add `--update-only` flag to update open CRs but not create new ones. Branches that would create new CRs are ignored.
+### Changed
+- submit: Include merged downstack changes in navigation comments when restacking and resubmitting changes based on them.
+- commit amend: Deprecate `-n` form of `--no-edit`. This will be deleted in a future version.
+- branch delete: If multiple branches are provided, delete them in a more predictable order.
+### Fixed
+- Reduce repeated work between git-spice commands that invoke each other.

CHANGELOG.md

@@ -5,6 +5,26 @@ 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.10.0">v0.10.0</a> - 2025-01-02
+
+This release addresses a long-standing limitation of navigation comments:
+they were limited only to open CRs.
+With the help of [@VenelinMartinov](https://github.com/VenelinMartinov),
+git-spice will now retain history of merged downstack CRs when posting navigation comments.
+
+### Added
+- commit create: Add `--fixup` flag to create fixup commits. You can use `git rebase --interactive` or `gs branch edit` to combine these fixup commits into their targets.
+- rebase continue: Add `--[no-]edit` flag to specify whether an editor should open to change the commit message. Defaults to the value of the `spice.rebaseContinue.edit` configuration option if set, or true if not.
+- Add `--no-verify` flag to bypass pre-commit and commit-msg Git hooks for commands that create new commits. This includes 'commit create', 'commit amend', 'commit split', and 'branch create'.
+- state: Track version of the state store layout in use. This should be a no-op for users, but it protects against future changes to the layout.
+- submit: Add `--update-only` flag to update open CRs but not create new ones. Branches that would create new CRs are ignored.
+### Changed
+- submit: Include merged downstack changes in navigation comments when restacking and resubmitting changes based on them.
+- commit amend: Deprecate `-n` form of `--no-edit`. This will be deleted in a future version.
+- branch delete: If multiple branches are provided, delete them in a more predictable order.
+### Fixed
+- Reduce repeated work between git-spice commands that invoke each other.
+
 ## <a name="v0.9.0">v0.9.0</a> - 2024-11-26
 
 This release adds support for using git-spice with GitLab.

doc/src/cli/config.md

@@ -103,7 +103,7 @@ instead of showing just the current stack.
 
 ### spice.rebaseContinue.edit
 
-<!-- gs:version unreleased -->
+<!-- gs:version v0.10.0 -->
 
 Whether $$gs rebase continue$$ should open an editor to modify the commit message
 when continuing after resolving a rebase conflict.

doc/src/guide/cr.md

@@ -82,7 +82,7 @@ configuration key.
 
 !!! info "Stack history in navigation comments"
 
-    <!-- gs:version unreleased -->
+    <!-- gs:version v0.10.0 -->
     When possible, git-spice will remember CRs as they're merged into trunk,
     and continue to list them in navigation comments of branches
     based on those changes.
@@ -137,7 +137,7 @@ and push to a branch anyway, use the `--force` flag.
 
 ### Update existing CRs only
 
-<!-- gs:version unreleased -->
+<!-- gs:version v0.10.0 -->
 
 All submit commands support the `--update-only` flag.
 If provided, the submission will update existing CRs in a stack,