-
Notifications
You must be signed in to change notification settings - Fork 1
Release History
ecamacho edited this page Jul 10, 2026
·
2 revisions
Past Jellyx releases. Notes are sourced from GitHub Release bodies and the git log between tags. There is no CHANGELOG file in the repo.
-
Tag:
v0.3.2 -
Release title:
Jellyx 0.3.2 - Status: Alpha.
Known version-sync issue: The
v0.3.2tag exists and the GitHub release is0.3.2, but at that tag the three version files (jellyx-desktop/Cargo.toml,jellyx-desktop/tauri.conf.json,ui/package.json) still report0.3.1. As a result, the in-app About page may show0.3.1for the v0.3.2 build. This is a packaging-time sync bug, not a different application. Future releases must bump all three files before tagging. See Release Process.
- Conventional commits between tags are read by
scripts/generate-release-body.sh. - The maintainer pastes the generated body into the GitHub Release.
- There is no standalone CHANGELOG file.
See Platform Support and Packaging Guide for the standard artifact set:
- Linux:
.deb,.rpm, AppImage,.tar.gz - macOS: DMG (Apple Silicon/aarch64 only; Intel DMG deferred/not currently produced)
- Windows: NSIS
setup.exe,.msi, portable.exe
When a new release ships, add an entry here in the same release work unit (see Wiki Maintenance):
- Add a
### vX.Y.Zsection at the top of Current. - Include tag, release title, status, and a short summary.
- Pull notable changes from the GitHub Release body.
- Add a Known note if any version-sync or packaging issue exists.
- Move older releases into a History section as the list grows.
- Release Process — how releases are cut
- Wiki Maintenance — the wiki-update rule
- Installation — install a release