Release v0.5.0 (#360)

.changes/v0.5.0.md

@@ -0,0 +1,10 @@
+## <a name="v0.5.0">v0.5.0</a> - 2024-08-25
+
+### Added
+- submit: Add `spice.submit.publish` configuration to allow making `--no-publish` the default. Use this to work with unsupported Git hosting services.
+- branch checkout: Add `spice.branchCheckout.showUntracked` configuration to always show untracked branches in checkout prompt.
+- branch create: Add `--[no-]commit` flag and accompanying `spice.branchCreate.commit` configuration to create stacked branches without committing changes.
+- submit: When importing existing CRs, also detect existing stack navigation comments and update them instead of posting duplicates. This will only work for comments posted git-spice v0.5 or newer.
+### Fixed
+- submit: When submitting with `--no-publish`, don't fail if the repository is hosted in an unsupported Git hosting services.
+- {branch, upstack} onto: Always rebase commits after the operation--even if the branch's base already matches the target. This better matches user expectations when the branch and base diverge.

CHANGELOG.md

@@ -5,6 +5,17 @@ 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.5.0">v0.5.0</a> - 2024-08-25
+
+### Added
+- submit: Add `spice.submit.publish` configuration to allow making `--no-publish` the default. Use this to work with unsupported Git hosting services.
+- branch checkout: Add `spice.branchCheckout.showUntracked` configuration to always show untracked branches in checkout prompt.
+- branch create: Add `--[no-]commit` flag and accompanying `spice.branchCreate.commit` configuration to create stacked branches without committing changes.
+- submit: When importing existing CRs, also detect existing stack navigation comments and update them instead of posting duplicates. This will only work for comments posted git-spice v0.5 or newer.
+### Fixed
+- submit: When submitting with `--no-publish`, don't fail if the repository is hosted in an unsupported Git hosting services.
+- {branch, upstack} onto: Always rebase commits after the operation--even if the branch's base already matches the target. This better matches user expectations when the branch and base diverge.
+
 ## <a name="v0.4.0">v0.4.0</a> - 2024-08-09
 
 This release adds support for configuring the behavior of git-spice

doc/src/cli/config.md

@@ -32,7 +32,7 @@ or at the repository level with the `--local` flag.
 
 ### spice.branchCheckout.showUntracked
 
-<!-- gs:version unreleased -->
+<!-- gs:version v0.5.0 -->
 
 When running $$gs branch checkout$$ without any arguments,
 git-spice presents a prompt to select a branch to checkout.
@@ -45,7 +45,7 @@ This option controls whether untracked branches are shown in the prompt.
 
 ### spice.branchCreate.commit
 
-<!-- gs:version unreleased -->
+<!-- gs:version v0.5.0 -->
 
 Whether $$gs branch create$$ should commit staged changes to the new branch.
 Set this to `false` to default to creating new branches without committing,
@@ -93,7 +93,7 @@ should post or update a navigation comment to the CR.
 
 ### spice.submit.publish
 
-<!-- gs:version unreleased -->
+<!-- gs:version v0.5.0 -->
 
 Whether submission commands ($$gs branch submit$$ and friends)
 should publish a CR to the forge.

doc/src/guide/pr.md

@@ -143,7 +143,7 @@ For example, if you have the GitHub CLI installed:
 This will work even for PRs that were not created by git-spice,
 or authored by someone else, as long as the above conditions are met.
 
-In <!-- gs:version unreleased --> or newer,
+In <!-- gs:version v0.5.0 --> or newer,
 this will also auto-detect [navigation comments](#navigation-comments)
 posted to the PR by git-spice, and update them if necessary.
 

doc/src/recipes.md

@@ -11,7 +11,7 @@ description: >-
 
 ### Create branches without committing
 
-<!-- gs:version unreleased -->
+<!-- gs:version v0.5.0 -->
 
 The default workflow for git-spice forces you to commit immediately
 to new branches: $$gs branch create$$ will create a new branch,