<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>CPA on Lynx Tech Blog</title><link>https://blog.lynxflow.co/en/tags/cpa/</link><description>Recent content in CPA on Lynx Tech Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Thu, 13 Aug 2026 00:00:00 +0800</lastBuildDate><atom:link href="https://blog.lynxflow.co/en/tags/cpa/index.xml" rel="self" type="application/rss+xml"/><item><title>My Auto-Update Kept Running Late, So I Counted Upstream's Release Hours</title><link>https://blog.lynxflow.co/en/posts/cpa-autoupdate-release-schedule/</link><pubDate>Thu, 13 Aug 2026 00:00:00 +0800</pubDate><guid>https://blog.lynxflow.co/en/posts/cpa-autoupdate-release-schedule/</guid><description>&lt;img src="https://blog.lynxflow.co/images/cpa-autoupdate-release-schedule.png" alt="Featured image of post My Auto-Update Kept Running Late, So I Counted Upstream's Release Hours" /&gt;The auto-update ran fine. It just ran at the wrong time. Last month I set up auto-update for my self-hosted CPA (CLIProxyAPI, a Claude proxy service): every day at 4 AM, a script pulls the upstream code, compiles, and restarts the service. I thought the time was clever — the middle of the night, nobody&amp;rsquo;s using it, plenty of room for a restart window.
This morning the update ran as usual and bumped me to v7.2.130. Then at around 2 PM the upstream shipped v7.2.131.</description></item></channel></rss>