Skip to content

Commit 7e01f8d

Browse files
committed
Release v1.1.1
1 parent e680232 commit 7e01f8d

File tree

6 files changed

+35
-2
lines changed

6 files changed

+35
-2
lines changed

changelog/unreleased/consistent-entry-ordering-in-multi-project-show-command.md renamed to changelog/releases/v1.1.1/entries/consistent-entry-ordering-in-multi-project-show-command.md

File renamed without changes.

changelog/unreleased/release-recovery-instructions-show-actual-branch-name.md renamed to changelog/releases/v1.1.1/entries/release-recovery-instructions-show-actual-branch-name.md

File renamed without changes.
Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
created: 2026-01-23
2+
title: Bugfixes for Multi-Project Display
3+
intro: >-
4+
This release fixes two bugs: the multi-project `show` command now displays entries
5+
in consistent chronological order, and release recovery instructions show the actual
6+
branch name instead of a placeholder.

changelog/releases/v1.1.1/notes.md

Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
This release fixes two bugs: the multi-project `show` command now displays entries in consistent chronological order, and release recovery instructions show the actual branch name instead of a placeholder.
2+
3+
## 🐞 Bug fixes
4+
5+
### Consistent entry ordering in multi-project show command
6+
7+
The multi-project `show` command now displays changelog entries in chronological order, with the newest entry at the bottom of the table where users expect it. Previously, entries were sorted newest-first, which was inconsistent with single-project behavior and user expectations. This brings the multi-project display in line with the rest of the application's sorting behavior.
8+
9+
*By @mavam and @claude in #6.*
10+
11+
### Release recovery instructions show actual branch name
12+
13+
When a release fails during the branch push step, the recovery instructions now display the actual branch name instead of a placeholder:
14+
15+
```
16+
╭──────────────────── Release Progress (2/5) ────────────────────╮
17+
│ ✔ git commit -m "Release v1.2.0" │
18+
│ ✔ git tag -a v1.2.0 -m "Release v1.2.0" │
19+
│ ✘ git push origin main:main │
20+
│ ○ git push origin v1.2.0 │
21+
│ ○ gh release create v1.2.0 --repo tenzir/ship ... │
22+
╰────────────────────────────────────────────────────────────────╯
23+
```
24+
25+
Previously, the failed step showed `git push origin <branch>:<branch>` instead of the actual branch name.
26+
27+
*By @mavam and @claude in #5.*

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.1.0"
3+
version = "1.1.1"
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)