QuestarrNG v2.1.1

User-facing changes

Fixed

• Search: Parallel game metadata searches now wait in a bounded queue at the configured request pace instead of failing with rate-limit errors.
• Settings: Settings and configuration screens now load reliably after repeated visits instead of using stale cached API responses.

Container image: ghcr.io/snapetech-org/questarrng:2.1.1

• GitHub Container Registry

Pull with: docker pull ghcr.io/snapetech-org/questarrng:2.1.1.

Windows installer: QuestarrSetup-2.1.1-windows-x64.exe

• SHA-256 checksum

Helm chart: questarr-0.1.15.tgz

• SHA-256 checksum

Install channels: Compose, Home Assistant, CasaOS, Cosmos, Umbrel, Unraid, and Helm deploy the GHCR image; the Proxmox LXC installer builds from source.

QuestarrNG v2.1.0

User-facing changes

Added

• Database Migration: Operators can copy a current PostgreSQL library into a migrated, empty SQLite database. Questarr keeps the source read-only and verifies all table contents inside one transaction; the older pre-v1.1 migration procedure remains separate.
• Downloads: Download torrent and NZB files directly from search results, or send the release to a configured downloader. When updates are available, choose which ones to include with the main game.
• Library: Create personal game lists for any theme, add games from your library to multiple lists, and rename or delete lists whenever plans change. Lists are private to your account and do not change a game's library status.
• Community: GitHub's issue chooser now includes a question template that asks for steps, environment details, and relevant logs while reminding people to remove secrets.
• Games: Game cards, Add Game search results, and details now treat a 0/10 IGDB score as a real rating, game details show HowLongToBeat estimates for close title matches, and desktop download searches use more screen width so release data is easier to read.
• Downloads: Add selected release groups from the download search dialog to Preferred Release Groups in Settings. Saving these groups keeps the existing automatic search filter setting unchanged.
• Search: Release Search can filter by verified torrent file extensions such as NSP or XCI. It inspects bounded torrent manifests and excludes unknown payloads instead of guessing from release names.
• Library: Library cards distinguish available game updates from ordinary search results. Availability changes refresh the owning user's library even when update notifications are muted.
• Search: Public HTTPS JSON catalogs in Hydra format can now supply torrent releases alongside existing indexers, with source attribution, bounded downloads, and normal search and acquisition rules.
• Discover: RAWG is now an optional game discovery provider alongside IGDB, with encrypted API key settings and separate provider game IDs.
• Downloads: Users can save an optional release-scoring profile to rank manual search results and limit automatic searches to releases that meet their format and quality preferences.

Changed

• Downloads: Long release names now wrap in the mobile download list instead of being clipped. When an indexer provides a safe comments page, the full title remains a link to that release.
• Library: The Library now uses clearer empty states with a direct next step. Add your first game from an empty library, add a searched title that is not in your collection, or clear filters when they hide every game.
• Operations: The operations guide now covers container health checks, log inspection, and safe SQLite or Postgres backup and recovery steps.
• Container: The default Compose file pulls the published GHCR image. Main builds use dev, while versioned releases update latest and keep an exact semantic-version tag for pinning.
  • Action required: Run docker compose pull and docker compose up -d to update an existing installation.
• Integrations: The xREL release browser now enables the next page only when another game release is available. It no longer relies on an unreliable upstream page count or shows a guessed total.
• Contribution Policy: Human contributors must sign off each non-merge commit with the Developer Certificate of Origin; GitHub-verified automation pull requests are exempt.
• Install: Unraid 6.10+ setup instructions now show how to install the QuestarrNG user template and configure its container path mapping.
• Containers: Breaking: New QuestarrNG container images are published under ghcr.io/snapetech-org/questarrng. Update Compose, Helm, Unraid, and other deployment configurations from ghcr.io/snapetech/questarrng. Existing tags in the old package remain available, but new releases will only appear in the organization package.
  • Action required: Update container references to ghcr.io/snapetech-org/questarrng.
• Deployment: Breaking: Production image releases now start only from a validated version-tag push; main merges and development/test image builds no longer publish latest or version tags.
  • Action required: Push a validated version tag to publish production images.
• Interface: More dialogs, settings, download screens, scoring, and provider controls now use the selected interface language, including status messages and file actions.
• Ci: The Windows service CI job now uses the .NET SDK selected for its runner on GitHub-hosted and trusted main runners.
• Documentation: New quick-start, indexer, notification, and RSS guides explain how to set up QuestarrNG and use its search and alert features.
• Validation: Independent validation tasks now run together in a bounded pool, reducing idle time while preserving dependencies, isolated results, and source checks. Superseded pull-request runs also release their concurrency slot after cancellation while current-run failures still reconcile.
• Localization: The interface now translates pages, settings, forms, and notifications into twelve locales alongside English. API errors show localized summaries while preserving their original details.
• Localization: Release group and release-name settings, category picker fallbacks, form validation, and log upload feedback now follow the selected interface language.
• Repository: QuestarrNG installation, support, and release links now use the snapetech-org repository address. Existing container image names remain unchanged.
• Ci: Trusted main checks and same-repository pull requests authored by snapetech can use the restricted runner pool after the readiness setting is enabled. Fork and bot pull requests remain on GitHub-hosted runners.
• Api: Questarr now translates recognized API and import diagnostic details, additional fixed labels in Custom Lists, downloader, logs, settings, indexer, and library workflows, and search empty-state guidance into the selected language. API clients continue to receive the existing English error details and stable error codes.
• Releases: Each version-tag release includes the Windows x64 installer and Helm chart with SHA-256 checksums; Home Assistant, CasaOS, Umbrel, and Helm metadata track the release version.
• Interface: Interface text across library, download, indexer, and settings screens now follows the selected language more consistently, including backlog roulette, download actions, file details, scoring, and provider configuration.

Fixed

• Downloads: Scheduled searches now include DLC and extras in the existing packs and add-ons results when those categories are enabled. Results from categories you turn off remain excluded.
• Calendar: Calendar release checks now recognize IGDB's explicit delayed release statuses, retain date-shift detection as a fallback, and notify users when a game first becomes delayed.
• Metadata: Manual metadata refresh now streams IGDB results in 100-game requests and saves updates in 50-game database transactions. A failed fetch no longer stops later batches, and the response reports games whose metadata could not be refreshed.
• Forms: Buttons used for form actions no longer submit the form unless they are explicitly marked as submit buttons.
• Downloads: When qBittorrent accepts a download but Questarr cannot confirm it yet, the app now shows that it is still checking and asks you to check qBittorrent before retrying.
• Imports: When you remove a game and choose to delete its files, Questarr now also removes files inside that user's enabled RomM library root. The configured root itself remains protected.
• Settings: Settings errors now explain that database migrations run at startup, show the manual migration command only for source installs, and offer a Try again action after the service is available.
  • Action required: Restart the service or container; source installs can run npm run db:migrate.
• Library: Add Game now handles records without IGDB IDs correctly. Mobile Add Game and preferred-release-group controls have clearer screen-reader names, and Deluge appears in the supported downloader list.
• Downloads: Linking a download that's already finished in a client now queues it for the normal import flow when post-processing is enabled. This also applies to bulk claims, so existing downloads can be added to the library without downloading them again.
• Deployment: Docker Compose once again accepts PORT from the project .env file as a fallback for both the host and container HTTP ports. Set HOST_SIDE_PORT or CONTAINER_INTERNAL_SIDE_PORT to override either side independently.
• Accessibility: The download-results options button now has a specific accessible name, making its purpose clearer to screen-reader users.
• Downloads: Manual download searches now use the game's chosen target platform before the account-wide default. If that platform is excluded by the Platforms setting, the dialog leaves its platform filter clear so results are not unexpectedly hidden.
• Downloads: The qBittorrent add request stops waiting for a matching torrent after 15 seconds while leaving accepted but unconfirmed downloads tracked, so users can check the client before retrying.
• Downloads Logs: Torrent errors now include qBittorrent's reported detail, and mobile logs explain when only the latest 200 entries are shown while Copy still includes every match.
• Imports: RomM import settings can now be saved by older clients that still send the fixed multiFilePlacement: "subfolder" field. The server ignores that legacy default while continuing to reject unrelated unknown settings.
• Usability: Search pagination stays available after date filtering, downloader and indexer priorities can be cleared and ...

QuestarrNG v2.0.0

Release assets

• Download QuestarrSetup-2.0.0-windows-x64.exe
• Windows installer SHA-256
• Download Helm chart questarr-0.1.12.tgz
• Helm chart SHA-256

QuestarrNG v1.11.0

User-facing changes

Added

• Support: The repository funding configuration now includes Ko-fi as an option for users who want to support project maintenance.
• Settings: Settings > Appearance separates interface language from regional date, time, and number formats; translated navigation, the calendar, and download dialogs honor those choices, including localized release dates and calendar week starts.
• Localization: Choose a display language during initial setup or later in Settings. Navigation and language controls are translated in twelve locales; other screens continue to fall back to English.

Changed

• Integrations: The fork guide now records QuestarrNG's current upstream comparison, standalone and SeerrNG-specific additions, and the capabilities needed to stop maintaining the fork.
• Localization: The Release Calendar and game download dialog now translate headings, controls, search filters, empty states, release categories, result guidance, and update actions where catalog entries are available. Dates and counts use the selected regional format. Missing text falls back to English; Arabic labels use local direction metadata, with full RTL review still outstanding.

Security

• Supply Chain: Build workflows now use an integrity-locked npm runtime, and the Home Assistant build pins its QuestarrNG base image by digest.
• Security: Breaking: JWT secrets are validated and rotated, invalidating affected sessions; CI audits locked dependencies and npm tooling, and version tags wait for clean Trivy scans of both Linux architectures plus zero open alerts and successful CodeQL and Semgrep scans.
  • Action required: Use a random JWT_SECRET containing at least 32 bytes, or unset it to generate one. Release maintainers must complete all security scans and resolve open alerts before publishing.
• Validation: Validation tasks now isolate inherited credentials and configuration, keep Playwright browsers available to isolated test processes, and remove task-owned temporary files after execution.
• Ci: Validation now keeps local credentials out of test snapshots while preserving legitimate source and deployment files. It also masks the original checkout under runtime mount aliases and requires sandbox verification in CI, so candidate tests cannot read private host files or silently skip isolation checks.
• Ci: Pull-request test jobs no longer receive the Codecov upload token, preventing candidate test processes from reaching it through later upload steps.
• Validation: Pull request tests and builds run inside an isolated sandbox with offline dependencies and source-bound receipts. The sandbox supports loopback-only tests while keeping host services, resolver settings, and external networking unavailable. Base-sourced checks validate the exact candidate snapshot, while Codecov uploads and Discord tag announcements run from trusted default-branch workflows.
• Ci Security: Validation snapshots hide dotted and extensionless credentials, private/API keys, access/refresh tokens, client secrets, and non-source files beneath credential folders while retaining source modules. The local launcher isolates the host root, skips deleted indexed files, and requires an explicit command; CI receipt downloads are limited to the current workflow attempt.

Removed

• Packaging: Breaking: QuestarrNG no longer publishes a YunoHost package, so existing installations will not receive future updates through YunoHost.
  • Action required: Migrate existing YunoHost installations to a supported deployment to continue receiving QuestarrNG updates.

Container image: ghcr.io/snapetech/questarrng:1.11.0

• GitHub Container Registry

Pull with: docker pull ghcr.io/snapetech/questarrng:1.11.0.

QuestarrNG v1.10.0

User-facing changes

Changed

• Integrations: SeerrNG can show verified Steam-library ownership and community play-time estimates; requests retain exact IGDB identity, distinguish local files from ownership, offer multi-file archives, and stage Real-Debrid downloads locally before import.

Container image: ghcr.io/snapetech/questarrng:1.10.0

• GitHub Container Registry

Pull with: docker pull ghcr.io/snapetech/questarrng:1.10.0.

QuestarrNG v1.9.3

User-facing changes

Changed

• Release Pipeline: QuestarrNG CI now records source-bound receipts for the full test suite and both Node build runners. Final CI reconciliation requires all three results to come from the same workflow attempt, source snapshot, and test inventory.

Fixed

• Validation: Validation CI now isolates nested contract fixtures from GitHub runner source metadata and pins its receipt download action correctly, allowing valid source-bound results to be reconciled.

Container image: ghcr.io/snapetech/questarrng:1.9.3

• GitHub Container Registry

Pull with: docker pull ghcr.io/snapetech/questarrng:1.9.3.

QuestarrNG v1.9.2

User-facing changes

Added

• Integration: SeerrNG requests can now retrieve a request-scoped .tar.gz bundle when an imported game has multiple registered files, while single-file downloads keep using the existing stream route.

Container image: ghcr.io/snapetech/questarrng:1.9.2

• GitHub Container Registry

Pull with: docker pull ghcr.io/snapetech/questarrng:1.9.2.

QuestarrNG v1.9.1

User-facing changes

Added

• Game Files: Game file browsing now lets you set a file’s category, and completed downloads record installed versions so older updates are no longer suggested.

Security

• Indexers: Prowlarr sync requires HTTPS by default and blocks HTTP redirects, preventing API keys from being forwarded without explicit opt-in to trusted local network transport.
• Deployment: Breaking: Production and Home Assistant images now run the app as the unprivileged questarr user; Compose definitions map it to PUID/PGID, and the Home Assistant startup helper can change ownership only within its persistent /data volume. The scanner toolchain and HTTP cache parser also received fixes for the open PyJWT and ReDoS alerts.
  • Action required: For direct Docker installs or custom PUID/PGID values, match the runtime user to the mounted data owner before upgrading.

Container image: ghcr.io/snapetech/questarrng:1.9.1

• GitHub Container Registry

Pull with: docker pull ghcr.io/snapetech/questarrng:1.9.1.

QuestarrNG v1.9.0

User-facing changes

Added

• Game Details: Game details now include an expansions tab with available DLC and expansion covers, release years, category labels, and links to their IGDB pages.
• Library Platforms: Platform preferences now carry across library filters, discovery, game adding, download searches, and import eligibility. Hide shelved or already-owned results by default, and track games on a Playing page with notes, milestones, screenshots, and Steam achievements.
• Discovery: Settings now support a global release-name blacklist that filters matching terms from manual searches, auto-search cycles, and AI-assisted release selection.

Security

• Imports: Optional VirusTotal hash lookups and local ClamAV scans run before downloads are unpacked or moved into the library. Flagged files are quarantined and create a Security Alert instead of being imported.

Container image: ghcr.io/snapetech/questarrng:1.9.0

• GitHub Container Registry

Pull with: docker pull ghcr.io/snapetech/questarrng:1.9.0.

QuestarrNG v1.8.3

User-facing changes

Added

• Settings: System settings now include a Ko-fi link for users who want to support QuestarrNG fork maintenance.

Security

• Dependencies: All application dependencies now pass the full npm security audit, including development tooling. The cache-policy fix from upstream PR #60 is covered locally while it awaits maintainer review, and license checks no longer pull in a separate npm resolver stack.

Container image: ghcr.io/snapetech/questarrng:1.8.3

• GitHub Container Registry

Pull with: docker pull ghcr.io/snapetech/questarrng:1.8.3.