Skip to content

docs: cut 0.13.0 #10

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
M0LTE merged 1 commit into from
Sep 17, 2026
Merged

docs: cut 0.13.0 #10

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ What changed in each release. The section for a version is lifted into that vers

Newest first. Add a section before tagging.

## 0.13.0 - unreleased
## 0.13.0 - 2026-09-17

- **`apt install tait-codeplug` now works**, on Debian, Ubuntu and Raspberry Pi OS, for `amd64`, `arm64` and `armhf`. Three lines to add the [packet-net apt repository](https://github.com/packet-net/apt) and it installs like any other package, and `apt upgrade` keeps it current along with everything else on the machine; the README has the lines. The package is the same self-contained single-file binary as the release asset for that architecture, built by the same publish with the same flags, so nothing needs .NET installed. A release now attaches the three `.deb` files as assets too, for installing one by hand.
- **`--upgrade` refuses on a copy installed from apt**, and says to run `sudo apt update && sudo apt install --only-upgrade tait-codeplug` instead. It used to overwrite whatever binary was running, which for a packaged copy means writing over a file dpkg owns: the package database would then describe something that is no longer there, and the next apt upgrade would put the old version back over the top. A copy you downloaded yourself still upgrades itself exactly as before, including one sitting in `/usr/local/bin` on a machine that also has the package.
Expand Down