Skip to content

Releases

Product direction for upcoming versions is on the Roadmap.

JellyGlance releases are driven by a version file on main or BETA. The Release Bot pipeline bumps package versions, builds the app, publishes the Docker image to GHCR, creates the git tag, and opens the GitHub release.

Current releaseJellyGlance v1.2.9
Open Latest Release
Newest release

JellyGlance v1.2.9

4 September 2026

Open on GitHub

⬇️ Downloads

  • Full queue parity — Transmission, Deluge, NZBGet, and rTorrent join qBittorrent/SABnzbd — add, pause, remove
  • "Why stalled?" — No peers, client error, or stalled time — shown on the queue and Home ops
  • autobrr hits — Filter matches now surface on the Downloads page
  • One-click retry — Retry a failed webhook delivery from Health, or a failed Arr/Seerr grab from Item Glance, Requests, or Downloads

▶️ Sessions & Playback

  • Session command bar — Stop playback, push a Jellyfin on-screen message, and see why a stream is transcoding
  • Repair Hub — New playback-quality repair flow for clients stuck transcoding and titles that won't start
  • Item pages — Watching-now chip, refresh item / scan libraries, and Open in Jellyfin

🏠 Home & Glance

  • Stream capacity widget — Concurrent vs. cap, transcode vs. direct play, over-limit alerts — right on Home
  • Ops digest — Live Jellyfin jobs, library storage size, Arr upcoming-size estimate
  • Item Glance / My Glance — One view pulling Jellyfin + Seerr + Arr + downloads + Tdarr + Maintainerr; a lighter cut for viewers
  • Activity Timeline — Now in the main nav — Calendar stays hidden until Sonarr, Radarr, or Lidarr is connected
  • Offline banner — Persistent nav banner when Jellyfin's unreachable, with last-seen version

🔔 Notifications

  • **ntfy, Telegram, Pushover** join Discord and Gotify as webhook targets
  • **Quiet hours** for webhooks, with an optional morning playback digest
  • **Discord cards** wrap long titles on a tighter canvas instead of clipping

⚙️ Settings

  • Jellyfin job schedules — Set daily, weekly, interval, or startup times for Jellyfin library scans, metadata, and other scheduled jobs. The Jellyfin Jobs page shows those times and still lets you run a job now
  • Quick Connect — Login starts the Jellyfin approval flow as soon as the page is ready

🎨 Themes & App

  • **Searchable theme picker**, grouped palettes — preview freely, hit **Apply** to sync it to your account across devices
  • **Installable PWA** for phone and kiosk home screens

☁️ Backup

  • **S3-compatible backup copy (SigV4)**, alongside WebDAV/HTTP
  • Changing language no longer posts External URL and fails with *"Error Updating Configuration: undefined"*
  • Requests status filters no longer break the Vite build
  • Downloads no longer black-screens from a missing integrations import
  • Settings and navbar no longer crash on missing remixicon imports after the theme picker work
  • Users no longer drops Jellyfin server administrators from the activity list
  • Tdarr Active Transcodes no longer shows `[object Object]` for format, status, or reason
  • Theme choice is preview-only in Settings and the account menu until Apply; Apply writes locally and syncs to the signed-in user
  • i18n catch-up for Requests, Repair Hub, My Glance, Command Center, newsletter, and newer ops copy
  • Discord playback and status images use a smaller wrapped card
  • Desktop pages no longer look zoomed or soft; type, spacing, and the sidebar stay sharp and a bit denser

How to cut a release

  1. Update .github/release.md (stable) or .github/release-beta.md (beta):
md
version: v1.2.9
title: JellyGlance v1.2.9
---
feat: short summary for the release

Added
- ...

Fixed
- ...
  1. Push that file change to main (or BETA).
  2. The JellyGlance Release Bot workflow:
    • Reads the version from the release file
    • Bumps root and workspace package.json / package-lock.json
    • Runs lint and builds (web + docs)
    • Commits chore(release): vX.Y.Z [skip ci] back to the branch
    • Builds and pushes multi-arch Docker images
    • Creates the annotated tag and GitHub release
    • Optionally posts to Discord

Commit message conventions

Release notes in the file can use Conventional Commit style for clarity:

  • fix: — bug fixes and stability
  • feat: — new features
  • feat!: / BREAKING CHANGE: — major changes

The file-driven pipeline does not auto-increment from commits; the version in .github/release.md is the source of truth.

Manual semantic-release

Release / Manual (npm run release + .releaserc.json) remains available for maintainers who want commit-analyzer driven releases. Prefer the file-driven Release Bot for normal stable/beta ships.

Local checks

Run these before merging release-bound changes:

sh
npm run lint
npm run build
npm run build:docs

Repository

Project releases live at:

text
https://github.com/Nerdy-Technician/JellyGlance/releases