13 Commits

Author SHA1 Message Date
ae5ef47877 🐛 fix: add test for asset name format and bump to 0.5.2
All checks were successful
continuous-integration/drone/tag Build is passing
continuous-integration/drone/push Build is passing
Adds a unit test that asserts detect_arch returns names prefixed
with 'tmuxido-' and suffixed with '-linux', matching what CI uploads.
2026-03-01 03:43:10 -03:00
319e8349db 📝 docs: add changelog entry for 0.5.1
All checks were successful
continuous-integration/drone/tag Build is passing
continuous-integration/drone/push Build is passing
2026-03-01 03:38:04 -03:00
2a3d1ffdbc 🔖 chore: bump version to 0.5.0
All checks were successful
continuous-integration/drone/push Build is passing
Update version in Cargo.toml and add CHANGELOG entry for the new
interactive configuration wizard feature.
2026-03-01 02:23:52 -03:00
79f1551f33 🐛 fix: bump version to 0.4.2 to fix self-update version mismatch
All checks were successful
continuous-integration/drone/tag Build is passing
continuous-integration/drone/push Build is passing
The Cargo.toml was still at 0.4.0 while the release was tagged as 0.4.1,
causing the --update command to always think there's a new version available.

Bumping to 0.4.2 ensures the binary version matches the release tag.
2026-03-01 01:13:21 -03:00
eacd41c2db force update
All checks were successful
continuous-integration/drone/push Build is passing
continuous-integration/drone/tag Build is passing
2026-03-01 01:04:15 -03:00
66c2343851 feat: add self-update capability
Add `tmuxido --update` command to update binary from latest release.
- New `self_update` module with version comparison
- Atomic binary replacement with backup/rollback
- Fetches latest release from Gitea API
- Downloads correct binary for system architecture
2026-03-01 00:34:42 -03:00
d77d17a7ea 🐛 fix(ci): read DRONE_TAG via awk ENVIRON to fix empty release body
All checks were successful
continuous-integration/drone/tag Build is passing
continuous-integration/drone/push Build is passing
Drone CI substitutes ${VAR} in commands before the shell runs.
Since TAG is a local shell variable (not a Drone var), ${TAG} was
replaced with an empty string, causing the awk pattern to match
nothing and the release body to be empty.

Fix: read DRONE_TAG directly inside awk via ENVIRON["DRONE_TAG"]
and strip the v-prefix with gsub — no intermediate shell variable needed.

Also translate CHANGELOG.md to English.
2026-03-01 00:19:10 -03:00
579916bbf1 🐛 fix(ci): corrigir pipeline release para tags v*
All checks were successful
continuous-integration/drone/push Build is passing
continuous-integration/drone/tag Build is passing
- Filtro de ref corrigido: [0-9]* → v* para bater em tags "v0.3.0"
- awk agora strip o prefixo 'v' de DRONE_TAG antes de buscar no CHANGELOG
- Adiciona entrada 0.3.0 no CHANGELOG.md
2026-03-01 00:01:29 -03:00
f1b5b4e304 chore: bump version to 0.2.4
All checks were successful
continuous-integration/drone/tag Build is passing
continuous-integration/drone/push Build is passing
2026-02-28 21:23:31 -03:00
d1446730b9 ci: use Gitea generic package registry for coverage badge 2026-02-28 21:08:39 -03:00
a6666dced9 chore: bump version to 0.2.2
Some checks failed
continuous-integration/drone/push Build is failing
continuous-integration/drone/tag Build is passing
2026-02-28 21:04:39 -03:00
71971c7b1b ci: add coverage badge pipeline and README badges
Some checks failed
continuous-integration/drone/push Build is failing
2026-02-28 21:04:05 -03:00
7c02b9f55d docs: add CHANGELOG and use it as release description in CI
All checks were successful
continuous-integration/drone/push Build is passing
2026-02-28 20:26:29 -03:00