<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Release on RenderCache.com</title>
    <link>https://rendercache.com/tags/release/</link>
    <description>Recent content in Release on RenderCache.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 16 Oct 2026 18:00:00 +0300</lastBuildDate>
    <atom:link href="https://rendercache.com/tags/release/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The alpha you can run today</title>
      <link>https://rendercache.com/alpha-release/</link>
      <pubDate>Fri, 16 Oct 2026 18:00:00 +0300</pubDate>
      <guid>https://rendercache.com/alpha-release/</guid>
      <description>&lt;p&gt;The first RenderCache alpha is available as a Linux amd64 archive with SHA-256 checksums and matching engine source. It keeps the runtime small in one specific sense: one Go service executable manages the reverse proxy, disk store, warm queue, receipts and protected admin app. Chrome is still a separate process and dependency. The Dockerfile installs Chromium for container deployments.&lt;/p&gt;&#xA;&lt;p&gt;The release pipeline checked the actual rendering path, rather than stopping at compilation. Race-enabled tests use real Chrome. The container check warms a page under a non-root user with restricted resources and filesystems, using an explicit sandbox opt-out inside an isolated test network. The nginx example is exercised against the executable, and the archive is rebuilt deterministically before its extracted binary is tested.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
