<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Versions on Solo</title><link>https://solo.hiero.org/tags/versions/</link><description>Recent content in Versions on Solo</description><generator>Hugo</generator><language>en</language><atom:link href="https://solo.hiero.org/tags/versions/index.xml" rel="self" type="application/rss+xml"/><item><title>One-Shot Deploy with Custom Component Versions</title><link>https://solo.hiero.org/docs/advanced-solo-setup/one-shot-deploy-with-custom-versions/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://solo.hiero.org/docs/advanced-solo-setup/one-shot-deploy-with-custom-versions/</guid><description>&lt;h2 id="overview"&gt;Overview&lt;a class="td-heading-self-link" href="#overview" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;Solo&amp;rsquo;s &lt;code&gt;one-shot single deploy&lt;/code&gt; and &lt;code&gt;one-shot multi deploy&lt;/code&gt; commands accept
an &lt;code&gt;--edge&lt;/code&gt; flag that switches every component from its built-in stable
default to a separate set of &amp;ldquo;edge&amp;rdquo; versions. Each edge version is read from
an environment variable at startup, so you can pin any component to any tag
the container registry exposes — including release candidates and unreleased
builds — without editing Solo source or rebuilding the CLI.&lt;/p&gt;</description></item></channel></rss>