<?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 BareProxy.com</title>
    <link>https://bareproxy.com/tags/release/</link>
    <description>Recent content in Release on BareProxy.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 05 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://bareproxy.com/tags/release/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>BareProxy 0.1 Alpha Adds Plan, Apply and Rollback</title>
      <link>https://bareproxy.com/bareproxy-0.1-alpha-adds-plan-apply-and-rollback/</link>
      <pubDate>Mon, 05 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://bareproxy.com/bareproxy-0.1-alpha-adds-plan-apply-and-rollback/</guid>
      <description>&lt;p&gt;BareProxy 0.1 Alpha is out. It adds the part of the design that makes a config change safe: &lt;code&gt;plan&lt;/code&gt; says which requests a change will hand to a different place, &lt;code&gt;apply&lt;/code&gt; makes it live, and &lt;code&gt;rollback&lt;/code&gt; takes it back.&lt;/p&gt;&#xA;&lt;p&gt;&lt;code&gt;bareproxy plan&lt;/code&gt; compares the config file with the running config and lists the requests that change hands, in lines such as &amp;ldquo;example.com, any method, /api/v2 and below&amp;rdquo;. It warns about a rule that can never match. Each plan has an ID, and &lt;code&gt;bareproxy apply --plan&lt;/code&gt; refuses if the file or the running config changed since, so two people can&amp;rsquo;t apply over each other.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
