<?xml version="1.0" standalone="yes"?><!-- sparkle-sign-warning:
IMPORTANT: This file was signed by Sparkle. Any modifications to this file requires re-signing this file with generate_appcast or sign_update! The signed signature will be embedded at the end of this file.
--><rss xmlns:sparkle="http://www.andymatuschak.org/xml-namespaces/sparkle" version="2.0">
    <channel>
        <title>Crisper</title>
        <item>
            <title>0.1.2</title>
            <pubDate>Wed, 12 Aug 2026 16:29:44 +0530</pubDate>
            <sparkle:version>102</sparkle:version>
            <sparkle:shortVersionString>0.1.2</sparkle:shortVersionString>
            <sparkle:minimumSystemVersion>26.0</sparkle:minimumSystemVersion>
            <description><![CDATA[<!--
	A maintenance release with genuinely nothing user-facing in it — the only
	commit since 0.1.1 is release engineering.

	The hard case for this file, and the reason it does not just say "bug fixes
	and improvements": that phrase is what an update reads as when nobody
	bothered, which is the exact failure CLAUDE.md's rule about empty changelogs
	is guarding against. Saying plainly that the app is unchanged is more
	trustworthy than inventing a feature to justify the window, and it is short
	enough that nobody feels they wasted the read.

	It is also the first release cut by the restructured Scripts/release.sh,
	which commits and tags before it builds. That is worth one honest sentence
	to a user of a notarized app distributed outside the App Store, and worth no
	more than one.
-->
<h2>Nothing in the app has changed</h2>
<p>
	This one is housekeeping. No new features, no fixes — 0.1.2 behaves exactly
	like 0.1.1, and there is nothing here you need to go and look at.
</p>

<h2>Why it exists</h2>
<p>
	Crisper is distributed directly rather than through the App Store, so the
	machinery that builds, signs and delivers these updates is ours to get right.
	Every release is now built from a recorded snapshot of its own source and
	tagged before it is built, rather than after — which means any version you
	are running can be traced back to exactly the code it came from. That
	guarantee is not worth much on its own; it is worth something when a later
	release needs to be checked, and it only works if it is in place beforehand.
</p>
<p>
	This release is also the first end-to-end test of the updater itself — the
	quiet daily check, the background download, and the <em>Install Update</em>
	line waiting in the menu instead of a window in front of your work.
</p>
]]></description>
            <enclosure url="https://github.com/jithinio/crisperflow-releases/releases/download/v0.1.2/Crisper-0.1.2.zip" length="3867389" type="application/octet-stream" sparkle:edSignature="Yp8ZoFtE/l9h/uQ3tSlM8dq0dVpr+Jf/QeFtjcoiFJ/BCneNbtB4Ml8AEakkitoVjgFPKqEaE6FpBTKPPArtCQ=="></enclosure>
        </item>
    </channel>
</rss><!-- sparkle-signatures:
edSignature: ijaxkKvYnl/2dTjLv23FpLClzit4WTTkLo6MUHxQYhPbFCTybTqJTdukfalrvp7lpyB09WtUhTcNf2IioA3eBQ==
length: 2896
-->
