FaynoSync

v1.6.3 Feature

This release adds 2 notable features for engineering teams evaluating rollout.

Published 25d Deployment Automation

✓ No known CVEs patched

✓ No known CVEs patched in this version

Topics

api auto-update cross-platform desktop-app electron electron-updater

+8 more

go mongodb s3 self-hosted software-updates tauri tuf update-server

Affected surfaces

deps

Summary

AI summary

Redis caching for Squirrel updater responses improves update analytics and artifact handling.

Full changelog

Added Redis caching for squirrel_windows updater responses, including the rewritten RELEASES feed served as a raw text/plain body (filename column rewritten to absolute storage URLs so Squirrel downloads each .nupkg directly from storage).
Added the updater parameter to the edge CDN object key so edge responses are cached per updater.

Team users now store artifacts under their admin: UpdateSpecificApp resolves the request owner via ResolveRequestOwner before uploading to S3.
.blockmap and .nupkg artifacts are now excluded from the checkLatest response since they are derived by updaters (electron-builder from the .yml, Squirrel from the RELEASES feed) and must not be returned.
Cached squirrel_windows RELEASES feeds no longer skew update analytics: the update status is now persisted in the cache entry (HasUpdate) and reused on cache hits, so outdated clients are correctly counted as outdated instead of falling through to clients_using_latest_version (the raw string body could not be inspected for update_available).

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Track FaynoSync

Get notified when new releases ship.

About FaynoSync

Self-hosted Dynamic Update Server with statistics, supporting multiple updaters. Flexible features for seamless app updates and insights.