Skip to content

Commit cfdb1be

Browse files
committed
Release v1.1.0
1 parent 9311f3a commit cfdb1be

File tree

5 files changed

+20
-2
lines changed

5 files changed

+20
-2
lines changed

changelog/unreleased/progress-tracking-for-release-publish-failures.md renamed to changelog/releases/v1.1.0/entries/progress-tracking-for-release-publish-failures.md

File renamed without changes.
Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
created: 2026-01-17
2+
title: Publish Progress Tracking
3+
intro: "This release improves the user experience when `release publish` encounters\n\
4+
failures mid-workflow. You now see a clear progress summary showing which steps\n\
5+
completed, which step failed, and what remains pending\u2014making recovery\nstraightforward."

changelog/releases/v1.1.0/notes.md

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
This release improves the user experience when `release publish` encounters failures mid-workflow. You now see a clear progress summary showing which steps completed, which step failed, and what remains pending—making recovery straightforward.
2+
3+
## 🚀 Features
4+
5+
### Progress tracking for release publish failures
6+
7+
The `release publish` command now displays a progress summary when a step fails mid-workflow, showing which steps completed successfully and which step failed.
8+
9+
When using `--commit` or `--tag` flags, the publish workflow executes multiple git operations (commit, tag, push branch, push tag) before publishing to GitHub. If any step fails, you now see a panel with checkmarks for completed steps, an X for the failed step, and circles for pending steps. This helps you understand exactly where the workflow stopped and what manual commands you need to run to recover.
10+
11+
For example, if the branch push fails due to network issues, you'll see that the commit and tag were created successfully, the push failed, and the tag push and GitHub publish are still pending—making it clear you can safely retry after fixing the network issue.
12+
13+
*By @mavam and @claude.*

pyproject.toml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
[project]
22
name = "tenzir-ship"
3-
version = "1.0.0"
3+
version = "1.1.0"
44
description = "Reusable changelog management toolkit for Tenzir repositories."
55
readme = "README.md"
66
requires-python = ">=3.12"

uv.lock

Lines changed: 1 addition & 1 deletion
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

0 commit comments

Comments
 (0)