# Tenzir Ship v1.1.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.

## 🐞 Bug Fixes

### Consistent entry ordering in multi-project show command

Jan 22, 2026 · [@mavam](https://github.com/mavam), [@claude](https://github.com/claude) · [#6](https://github.com/tenzir/ship/pull/6)

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.

### Release recovery instructions show actual branch name

Jan 22, 2026 · [@mavam](https://github.com/mavam), [@claude](https://github.com/claude) · [#5](https://github.com/tenzir/ship/pull/5)

When a release fails during the branch push step, the recovery instructions now display the actual branch name instead of a placeholder:

```plaintext
╭──────────────────── Release Progress (2/5) ────────────────────╮
│ ✔ git commit -m "Release v1.2.0"                               │
│ ✔ git tag -a v1.2.0 -m "Release v1.2.0"                        │
│ ✘ git push origin main:main                                    │
│ ○ git push origin v1.2.0                                       │
│ ○ gh release create v1.2.0 --repo tenzir/ship ...              │
╰────────────────────────────────────────────────────────────────╯
```

Previously, the failed step showed `git push origin <branch>:<branch>` instead of the actual branch name.

[ Download on GitHub ](https://github.com/tenzir/ship/releases/tag/v1.1.1)

[Get the release artifacts and source code.](https://github.com/tenzir/ship/releases/tag/v1.1.1)