<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Core on</title><link>https://deploy-preview-3608--amazing-golick-2d0138.netlify.app/docs/core/</link><description>Recent content in Core on</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Wed, 22 Jul 2026 15:31:31 +0200</lastBuildDate><atom:link href="https://deploy-preview-3608--amazing-golick-2d0138.netlify.app/docs/core/index.xml" rel="self" type="application/rss+xml"/><item><title>Manifest Order</title><link>https://deploy-preview-3608--amazing-golick-2d0138.netlify.app/docs/core/order/</link><pubDate>Wed, 15 Apr 2026 07:21:01 +0200</pubDate><guid>https://deploy-preview-3608--amazing-golick-2d0138.netlify.app/docs/core/order/</guid><description>&lt;div class="sect1"&gt;
&lt;h2 id="_description"&gt;Description&lt;/h2&gt;
&lt;div class="sectionbody"&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;By default, Updatecli treats each manifest as an independent pipeline and do not guarantee ordering.
When you run multiple manifests from the same directory, Updatecli can now order them explicitly before execution.&lt;/p&gt;
&lt;/div&gt;</description></item><item><title>Action</title><link>https://deploy-preview-3608--amazing-golick-2d0138.netlify.app/docs/core/action/</link><pubDate>Fri, 11 Apr 2025 15:21:01 +0200</pubDate><guid>https://deploy-preview-3608--amazing-golick-2d0138.netlify.app/docs/core/action/</guid><description>&lt;div class="sect1"&gt;
&lt;h2 id="_description"&gt;Description&lt;/h2&gt;
&lt;div class="sectionbody"&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;An Updatecli action defines what happens after a change is detected and validated. While Updatecli’s sources find changes (like a new version), and targets define where to apply them (like a file), actions describe what to do next—such as creating a pull request.&lt;/p&gt;
&lt;/div&gt;</description></item><item><title>Compose</title><link>https://deploy-preview-3608--amazing-golick-2d0138.netlify.app/docs/core/compose/</link><pubDate>Sun, 01 Oct 2023 12:21:01 +0200</pubDate><guid>https://deploy-preview-3608--amazing-golick-2d0138.netlify.app/docs/core/compose/</guid><description>&lt;div class="sect1"&gt;
&lt;h2 id="_description"&gt;Description&lt;/h2&gt;
&lt;div class="sectionbody"&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;The updatecli compose feature allows specifying a list of updatecli policies to enforce.
This is useful when applying the same policies on multiple repositories.&lt;/p&gt;
&lt;/div&gt;</description></item><item><title>Updatecli Policy</title><link>https://deploy-preview-3608--amazing-golick-2d0138.netlify.app/docs/core/shareandreuse/</link><pubDate>Sun, 01 Oct 2023 12:21:01 +0200</pubDate><guid>https://deploy-preview-3608--amazing-golick-2d0138.netlify.app/docs/core/shareandreuse/</guid><description>&lt;div class="sect1"&gt;
&lt;h2 id="_description"&gt;Description&lt;/h2&gt;
&lt;div class="sectionbody"&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;As the number of updatecli policies increases, more and more, we realize that we need the ability to scale updatecli.
Somewhere between what we have now, duplicated manifest(s) for each Git repository, and the Autodiscovery feature.&lt;/p&gt;
&lt;/div&gt;</description></item><item><title>Autodiscovery</title><link>https://deploy-preview-3608--amazing-golick-2d0138.netlify.app/docs/core/autodiscovery/</link><pubDate>Sun, 09 Jan 2022 15:21:01 +0200</pubDate><guid>https://deploy-preview-3608--amazing-golick-2d0138.netlify.app/docs/core/autodiscovery/</guid><description>&lt;div class="sect1"&gt;
&lt;h2 id="_description"&gt;Description&lt;/h2&gt;
&lt;div class="sectionbody"&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;In the lifecycle of a software project, dependencies are everywhere.
From that third application used to lint our code, the tool used to build our documentation website, or the container image used to distribute our application.
As the project grows, the number of dependencies grows as long.
Some dependencies are context-dependent, and others are expressed using a standard data structure.&lt;/p&gt;
&lt;/div&gt;</description></item><item><title>Condition</title><link>https://deploy-preview-3608--amazing-golick-2d0138.netlify.app/docs/core/condition/</link><pubDate>Sat, 09 Jan 2021 15:21:01 +0200</pubDate><guid>https://deploy-preview-3608--amazing-golick-2d0138.netlify.app/docs/core/condition/</guid><description>&lt;div class="sect1"&gt;
&lt;h2 id="_description"&gt;Description&lt;/h2&gt;
&lt;div class="sectionbody"&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;A &amp;#34;condition&amp;#34; stage defines whether to run the &lt;a href="../target"&gt;&amp;#34;Target&amp;#34; stage&lt;/a&gt; stage of a pipeline.
It runs a check (depending on the resource kind) that returns a boolean indicating its success (&lt;code&gt;true&lt;/code&gt;) or failure (&lt;code&gt;true&lt;/code&gt;).&lt;/p&gt;
&lt;/div&gt;</description></item><item><title>Source</title><link>https://deploy-preview-3608--amazing-golick-2d0138.netlify.app/docs/core/source/</link><pubDate>Sat, 09 Jan 2021 15:21:01 +0200</pubDate><guid>https://deploy-preview-3608--amazing-golick-2d0138.netlify.app/docs/core/source/</guid><description>&lt;div class="sect1"&gt;
&lt;h2 id="_description"&gt;Description&lt;/h2&gt;
&lt;div class="sectionbody"&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;The &amp;#34;source&amp;#34; stage retrieves information from a third &amp;#34;resource&amp;#34; like a file, or an API and then uses that information in later stages.&lt;/p&gt;
&lt;/div&gt;</description></item><item><title>Target</title><link>https://deploy-preview-3608--amazing-golick-2d0138.netlify.app/docs/core/target/</link><pubDate>Sat, 09 Jan 2021 15:21:01 +0200</pubDate><guid>https://deploy-preview-3608--amazing-golick-2d0138.netlify.app/docs/core/target/</guid><description>&lt;div class="sect1"&gt;
&lt;h2 id="_description"&gt;Description&lt;/h2&gt;
&lt;div class="sectionbody"&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;The &amp;#34;target&amp;#34; stage is updated if the necessary &amp;#34;resource&amp;#34;, like a file based on information retrieved from a source. This happens provided all condition checks succeed.&lt;/p&gt;
&lt;/div&gt;</description></item><item><title>Transformer</title><link>https://deploy-preview-3608--amazing-golick-2d0138.netlify.app/docs/core/transformer/</link><pubDate>Sat, 09 Jan 2021 15:21:01 +0200</pubDate><guid>https://deploy-preview-3608--amazing-golick-2d0138.netlify.app/docs/core/transformer/</guid><description>&lt;div class="sect1"&gt;
&lt;h2 id="_description"&gt;Description&lt;/h2&gt;
&lt;div class="sectionbody"&gt;
&lt;div class="paragraph"&gt;
&lt;p&gt;The &amp;#34;transformers&amp;#34; parameter can be used by any stage definition as a &amp;#34;source&amp;#34;, &amp;#34;condition&amp;#34;, or &amp;#34;target&amp;#34;.
A &amp;#34;transformers&amp;#34; object contains a list of transformers. Each kind of transformer rules applies a string manipulation like adding or removing characters.&lt;/p&gt;
&lt;/div&gt;</description></item><item><title>Configuration</title><link>https://deploy-preview-3608--amazing-golick-2d0138.netlify.app/docs/core/configuration/</link><pubDate>Tue, 13 Oct 2020 15:21:01 +0200</pubDate><guid>https://deploy-preview-3608--amazing-golick-2d0138.netlify.app/docs/core/configuration/</guid><description>&lt;div class="paragraph"&gt;
&lt;p&gt;Updatecli requires a configuration file, or &amp;#34;manifest&amp;#34;, which describes the update pipeline.
A manifest describes the &amp;#34;what&amp;#34;, the &amp;#34;when&amp;#34;, and the &amp;#34;where&amp;#34; of the update pipeline.&lt;/p&gt;
&lt;/div&gt;</description></item></channel></rss>