Bump pack version in CI (#793)

* Bump pack version in CI

Update to pack 0.36.0

Signed-off-by: Aidan Delaney <[email protected]>

* Update tools to latest pack

Do not require an older dependency

Signed-off-by: Aidan Delaney <[email protected]>

---------

Signed-off-by: Aidan Delaney <[email protected]>

docs/for-buildpack-authors/tutorials/basic-buildpack/02_building-blocks-cnb/index.html

@@ -922,15 +922,14 @@ <h2 id="using-the-pack-cli">Using the Pack CLI</h2>
 </span></span></span><span class="line"><span class="cl"><span class="se"></span>    --api 0.10 <span class="se">\
 </span></span></span><span class="line"><span class="cl"><span class="se"></span>    --path node-js-buildpack <span class="se">\
 </span></span></span><span class="line"><span class="cl"><span class="se"></span>    --version 0.0.1 <span class="se">\
-</span></span></span><span class="line"><span class="cl"><span class="se"></span>    --stacks io.buildpacks.samples.stacks.noble
+</span></span></span><span class="line"><span class="cl"><span class="se"></span>    --targets <span class="s2">&#34;linux/amd64&#34;</span>
 </span></span></code></pre></div><!--+- "{{execute}}"+-->
 <p>This command will create <code>node-js-buildpack</code> directory which contains <code>buildpack.toml</code>, <code>bin/build</code>,  <code>bin/detect</code> files.</p>
 <h3 id="additional-parameters">Additional Parameters</h3>
 <ul>
 <li><code>-a, --api</code> Buildpack API compatibility of the generated buildpack</li>
 <li><code>-h, --help</code> Help for &rsquo;new'</li>
 <li><code>--path</code> the location on the filesystem to generate the artifacts</li>
-<li><code>--stacks</code> Stacks (deprecated) the buildpack will work with</li>
 <li><code>-V, --version</code> the version of the buildpack in buildpack.toml</li>
 </ul>
 <h3 id="buildpacktoml">buildpack.toml</h3>
@@ -947,10 +946,7 @@ <h3 id="buildpacktoml">buildpack.toml</h3>
 </span></span><span class="line"><span class="cl"><span class="c"># Targets the buildpack will work with</span>
 </span></span><span class="line"><span class="cl"><span class="p">[[</span><span class="nx">targets</span><span class="p">]]</span>
 </span></span><span class="line"><span class="cl"><span class="nx">os</span> <span class="p">=</span> <span class="s2">&#34;linux&#34;</span>
-</span></span><span class="line"><span class="cl">
-</span></span><span class="line"><span class="cl"><span class="c"># Stacks (deprecated) the buildpack will work with</span>
-</span></span><span class="line"><span class="cl"><span class="p">[[</span><span class="nx">stacks</span><span class="p">]]</span>
-</span></span><span class="line"><span class="cl">  <span class="nx">id</span> <span class="p">=</span> <span class="s2">&#34;io.buildpacks.samples.stacks.noble&#34;</span>
+</span></span><span class="line"><span class="cl"><span class="nx">architecture</span> <span class="p">=</span> <span class="s2">&#34;amd64&#34;</span>
 </span></span></code></pre></div><p>The buildpack ID is the way you will reference the buildpack when you create buildpack groups, builders, etc.
 <a href="/docs/for-buildpack-authors/concepts/targets/">Targets</a> identifies the kind of build and run base images the buildpack will work with.
 The stack ID (deprecated) uniquely identifies a build and run image configuration the buildpack will work with. This example can be run on Ubuntu Noble.</p>
@@ -989,9 +985,9 @@ <h3 id="using-your-buildpack-with-pack">Using your buildpack with <code>pack</co
 <!-- test:assert=contains;ignore-lines=... -->
 <pre tabindex="0"><code>===&gt; DETECTING
 ...
-err:  examples/[email protected] (1)
-ERROR: No buildpack groups passed detection.
-ERROR: failed to detect: buildpack(s) failed with err
+[detector] err:  examples/[email protected] (1)
+[detector] ERROR: No buildpack groups passed detection.
+[detector] ERROR: failed to detect: buildpack(s) failed with err
 ERROR: failed to build: executing lifecycle: failed with status code: 21
 </code></pre><!--+ if false+-->
 <hr>

docs/for-buildpack-authors/tutorials/basic-buildpack/04_build-app/index.html

@@ -965,8 +965,8 @@ <h3 id="running-the-build">Running the Build</h3>
 ...
 ===&gt; RESTORING
 ===&gt; BUILDING
----&gt; NodeJS Buildpack
----&gt; Downloading and extracting NodeJS
+[builder] ---&gt; NodeJS Buildpack
+[builder] ---&gt; Downloading and extracting NodeJS
 ...
 ===&gt; EXPORTING
 ...

docs/for-buildpack-authors/tutorials/basic-buildpack/06_caching/index.html

@@ -1007,8 +1007,8 @@ <h2 id="cache-the-runtime-layer">Cache the runtime layer</h2>
 <!-- test:assert=contains;ignore-lines=... -->
 <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-text" data-lang="text"><span class="line"><span class="cl">===&gt; BUILDING
 </span></span><span class="line"><span class="cl">...
-</span></span><span class="line"><span class="cl">---&gt; NodeJS Buildpack
-</span></span><span class="line"><span class="cl">-----&gt; Reusing NodeJS
+</span></span><span class="line"><span class="cl">[builder] ---&gt; NodeJS Buildpack
+</span></span><span class="line"><span class="cl">[builder] -----&gt; Reusing NodeJS
 </span></span></code></pre></div><p>Next, let&rsquo;s see how buildpack users may be able to provide configuration to the buildpack.</p>
 <!--+if false+-->
 <hr>

docs/for-buildpack-authors/tutorials/basic-buildpack/07_make-buildpack-configurable/index.html

@@ -990,8 +990,8 @@ <h2 id="select-nodejs-version">Select NodeJS version</h2>
 <!-- test:assert=contains;ignore-lines=... -->
 <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-text" data-lang="text"><span class="line"><span class="cl">===&gt; BUILDING
 </span></span><span class="line"><span class="cl">...
-</span></span><span class="line"><span class="cl">---&gt; NodeJS Buildpack
-</span></span><span class="line"><span class="cl">-----&gt; Downloading and extracting NodeJS 18.18.1
+</span></span><span class="line"><span class="cl">[builder] ---&gt; NodeJS Buildpack
+</span></span><span class="line"><span class="cl">[builder] -----&gt; Downloading and extracting NodeJS 18.18.1
 </span></span></code></pre></div><h2 id="going-further">Going further</h2>
 <p>Now that you&rsquo;ve finished your buildpack, how about extending it? Try:</p>
 <ul>

docs/for-buildpack-authors/tutorials/basic-buildpack/index.xml

@@ -19,7 +19,7 @@
       <link>https://buildpacks.io/docs/for-buildpack-authors/tutorials/basic-buildpack/02_building-blocks-cnb/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       <guid>https://buildpacks.io/docs/for-buildpack-authors/tutorials/basic-buildpack/02_building-blocks-cnb/</guid>
-      <description>&lt;!-- test:suite=create-buildpack;weight=2 --&gt;&#xA;&lt;p&gt;Now we will set up the buildpack scaffolding.&lt;/p&gt;&#xA;&lt;p&gt;Let&amp;rsquo;s create the directory where your buildpack will live:&lt;/p&gt;&#xA;&lt;h2 id=&#34;using-the-pack-cli&#34;&gt;Using the Pack CLI&lt;/h2&gt;&#xA;&lt;p&gt;The &lt;code&gt;buildpack new &amp;lt;id&amp;gt;&lt;/code&gt; command will create a directory named for the buildpack ID.&#xA;Make sure to run this command outside the &lt;code&gt;node-js-sample-app&lt;/code&gt; directory created previously.&lt;/p&gt;&#xA;&lt;p&gt;Example:&lt;/p&gt;&#xA;&lt;!-- test:exec --&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; class=&#34;chroma&#34;&gt;&lt;code class=&#34;language-bash&#34; data-lang=&#34;bash&#34;&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;pack buildpack new examples/node-js &lt;span class=&#34;se&#34;&gt;\&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;&lt;span class=&#34;se&#34;&gt;&lt;/span&gt;    --api 0.10 &lt;span class=&#34;se&#34;&gt;\&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;&lt;span class=&#34;se&#34;&gt;&lt;/span&gt;    --path node-js-buildpack &lt;span class=&#34;se&#34;&gt;\&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;&lt;span class=&#34;se&#34;&gt;&lt;/span&gt;    --version 0.0.1 &lt;span class=&#34;se&#34;&gt;\&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;&lt;span class=&#34;se&#34;&gt;&lt;/span&gt;    --stacks io.buildpacks.samples.stacks.noble&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;!--+- &#34;{{execute}}&#34;+--&gt;&#xA;&lt;p&gt;This command will create &lt;code&gt;node-js-buildpack&lt;/code&gt; directory which contains &lt;code&gt;buildpack.toml&lt;/code&gt;, &lt;code&gt;bin/build&lt;/code&gt;,  &lt;code&gt;bin/detect&lt;/code&gt; files.&lt;/p&gt;</description>
+      <description>&lt;!-- test:suite=create-buildpack;weight=2 --&gt;&#xA;&lt;p&gt;Now we will set up the buildpack scaffolding.&lt;/p&gt;&#xA;&lt;p&gt;Let&amp;rsquo;s create the directory where your buildpack will live:&lt;/p&gt;&#xA;&lt;h2 id=&#34;using-the-pack-cli&#34;&gt;Using the Pack CLI&lt;/h2&gt;&#xA;&lt;p&gt;The &lt;code&gt;buildpack new &amp;lt;id&amp;gt;&lt;/code&gt; command will create a directory named for the buildpack ID.&#xA;Make sure to run this command outside the &lt;code&gt;node-js-sample-app&lt;/code&gt; directory created previously.&lt;/p&gt;&#xA;&lt;p&gt;Example:&lt;/p&gt;&#xA;&lt;!-- test:exec --&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; class=&#34;chroma&#34;&gt;&lt;code class=&#34;language-bash&#34; data-lang=&#34;bash&#34;&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;pack buildpack new examples/node-js &lt;span class=&#34;se&#34;&gt;\&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;&lt;span class=&#34;se&#34;&gt;&lt;/span&gt;    --api 0.10 &lt;span class=&#34;se&#34;&gt;\&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;&lt;span class=&#34;se&#34;&gt;&lt;/span&gt;    --path node-js-buildpack &lt;span class=&#34;se&#34;&gt;\&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;&lt;span class=&#34;se&#34;&gt;&lt;/span&gt;    --version 0.0.1 &lt;span class=&#34;se&#34;&gt;\&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;&lt;span class=&#34;se&#34;&gt;&lt;/span&gt;    --targets &lt;span class=&#34;s2&#34;&gt;&amp;#34;linux/amd64&amp;#34;&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;!--+- &#34;{{execute}}&#34;+--&gt;&#xA;&lt;p&gt;This command will create &lt;code&gt;node-js-buildpack&lt;/code&gt; directory which contains &lt;code&gt;buildpack.toml&lt;/code&gt;, &lt;code&gt;bin/build&lt;/code&gt;,  &lt;code&gt;bin/detect&lt;/code&gt; files.&lt;/p&gt;</description>
     </item>
     <item>
       <title>Detecting your application</title>

docs/for-buildpack-authors/tutorials/basic-extension/02_why-dockerfiles/index.html

@@ -929,6 +929,7 @@ <h3 id="create-a-builder-with-extensions-and-publish-it">Create a builder with e
 <!-- test:exec -->
 <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">pack builder create localhost:5000/extensions-builder <span class="se">\
 </span></span></span><span class="line"><span class="cl"><span class="se"></span>  --config <span class="nv">$PWD</span>/samples/builders/alpine/builder.toml <span class="se">\
+</span></span></span><span class="line"><span class="cl"><span class="se"></span>  --target <span class="s2">&#34;linux/amd64&#34;</span> <span class="se">\
 </span></span></span><span class="line"><span class="cl"><span class="se"></span>  --publish
 </span></span></code></pre></div><h3 id="build-the-application-image">Build the application image</h3>
 <p>Run <code>pack build</code> (note that the &ldquo;source&rdquo; directory is effectively ignored in our example):</p>

docs/for-platform-operators/how-to/integrate-ci/pack/cli/pack_config_lifecycle-image/index.html

@@ -906,11 +906,11 @@ <h1 class="title">pack config lifecycle-image</h1>
         <h2 id="pack-config-lifecycle-image">pack config lifecycle-image</h2>
 <p>Configure a custom container image for the lifecycle</p>
 <h3 id="synopsis">Synopsis</h3>
-<p>You can use this command to set a custom image to fetch the lifecycle from.This will be used for untrusted builders. If unset, defaults to: buildpacksio/lifecycleFor more on trusted builders, and when to trust or untrust a builder, check out our docs here: <a href="https://buildpacks.io/docs/tools/pack/concepts/trusted_builders/">https://buildpacks.io/docs/tools/pack/concepts/trusted_builders/</a></p>
+<p>You can use this command to set a custom image to fetch the lifecycle from.This will be used for untrusted builders. If unset, defaults to: docker.io/buildpacksio/lifecycleFor more on trusted builders, and when to trust or untrust a builder, check out our docs here: <a href="https://buildpacks.io/docs/tools/pack/concepts/trusted_builders/">https://buildpacks.io/docs/tools/pack/concepts/trusted_builders/</a></p>
 <pre tabindex="0"><code>pack config lifecycle-image &lt;lifecycle-image&gt; [flags]
 </code></pre><h3 id="options">Options</h3>
 <pre tabindex="0"><code>  -h, --help    Help for &#39;lifecycle-image&#39;
-  -u, --unset   Unset custom lifecycle image, and use the lifecycle images from [94mbuildpacksio/lifecycle[0m
+  -u, --unset   Unset custom lifecycle image, and use the lifecycle images from [94mdocker.io/buildpacksio/lifecycle[0m
 </code></pre><h3 id="options-inherited-from-parent-commands">Options inherited from parent commands</h3>
 <pre tabindex="0"><code>      --force-color   Force color output
       --no-color      Disable color output

docs/for-platform-operators/how-to/integrate-ci/pack/index.html

@@ -919,7 +919,7 @@ <h1 class="title">Pack</h1>
 <hr>
 <h2 id="pack-cli"><code>pack</code> CLI</h2>
 <h3 id="install">Install</h3>
-<p>You can install the most recent version of the <code>pack</code> CLI (version <strong>0.35.1</strong>) on the following operating systems:</p>
+<p>You can install the most recent version of the <code>pack</code> CLI (version <strong>0.36.0</strong>) on the following operating systems:</p>
 
 
 
@@ -1001,7 +1001,7 @@ <h4 id="tags">Tags</h4>
 </li>
 <li>Use a version tag to pin a specific release:
 <ul>
-<li><code>buildpacksio/pack:0.35.1</code></li>
+<li><code>buildpacksio/pack:0.36.0</code></li>
 <li><a href="https://hub.docker.com/r/buildpacksio/pack/tags">other versions</a></li>
 </ul>
 </li>
@@ -1040,7 +1040,7 @@ <h4 id="usage">Usage</h4>
 
               <div class="tab-pane px-3 fade " id="linux-script-install">
                 <p>The following command will download the latest version of <code>pack</code> from <a href="https://github.com/buildpacks/pack/releases">GitHub</a> and install it in <code>/usr/local/bin/</code>.</p>
-<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl"><span class="o">(</span>curl -sSL <span class="s2">&#34;https://github.com/buildpacks/pack/releases/download/v0.35.1/pack-v0.35.1-linux.tgz&#34;</span> <span class="p">|</span> sudo tar -C /usr/local/bin/ --no-same-owner -xzv pack<span class="o">)</span>
+<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl"><span class="o">(</span>curl -sSL <span class="s2">&#34;https://github.com/buildpacks/pack/releases/download/v0.36.0/pack-v0.36.0-linux.tgz&#34;</span> <span class="p">|</span> sudo tar -C /usr/local/bin/ --no-same-owner -xzv pack<span class="o">)</span>
 </span></span></code></pre></div>
               </div>
 
@@ -1101,7 +1101,7 @@ <h4 id="tags">Tags</h4>
 </li>
 <li>Use a version tag to pin a specific release:
 <ul>
-<li><code>buildpacksio/pack:0.35.1</code></li>
+<li><code>buildpacksio/pack:0.36.0</code></li>
 <li><a href="https://hub.docker.com/r/buildpacksio/pack/tags">other versions</a></li>
 </ul>
 </li>
@@ -1131,9 +1131,9 @@ <h4 id="usage">Usage</h4>
               <div class="tab-pane px-3 fade " id="macos-script-install">
                 <p>The following command will download the latest version of <code>pack</code> from <a href="https://github.com/buildpacks/pack/releases">GitHub</a> and install it in <code>/usr/local/bin/</code>.</p>
 <p>Intel:</p>
-<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl"><span class="o">(</span>curl -sSL <span class="s2">&#34;https://github.com/buildpacks/pack/releases/download/v0.35.1/pack-v0.35.1-macos.tgz&#34;</span> <span class="p">|</span> sudo tar -C /usr/local/bin/ --no-same-owner -xzv pack<span class="o">)</span>
+<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl"><span class="o">(</span>curl -sSL <span class="s2">&#34;https://github.com/buildpacks/pack/releases/download/v0.36.0/pack-v0.36.0-macos.tgz&#34;</span> <span class="p">|</span> sudo tar -C /usr/local/bin/ --no-same-owner -xzv pack<span class="o">)</span>
 </span></span></code></pre></div><p>Apple Silicon:</p>
-<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl"><span class="o">(</span>curl -sSL <span class="s2">&#34;https://github.com/buildpacks/pack/releases/download/v0.35.1/pack-v0.35.1-macos-arm64.tgz&#34;</span> <span class="p">|</span> sudo tar -C /usr/local/bin/ --no-same-owner -xzv pack<span class="o">)</span>
+<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl"><span class="o">(</span>curl -sSL <span class="s2">&#34;https://github.com/buildpacks/pack/releases/download/v0.36.0/pack-v0.36.0-macos-arm64.tgz&#34;</span> <span class="p">|</span> sudo tar -C /usr/local/bin/ --no-same-owner -xzv pack<span class="o">)</span>
 </span></span></code></pre></div>
               </div>
 
@@ -1185,7 +1185,7 @@ <h4 id="usage">Usage</h4>
 
               <div class="tab-pane px-3 fade active in show" id="windows-chocolatey">
                 <p>To install <code>pack</code> on Windows, we recommend using <a href="https://chocolatey.org/">Chocolatey</a>:</p>
-<pre tabindex="0"><code>choco install pack --version=0.35.1
+<pre tabindex="0"><code>choco install pack --version=0.36.0
 </code></pre>
               </div>
 
@@ -1202,7 +1202,7 @@ <h4 id="tags">Tags</h4>
 </li>
 <li>Use a version tag to pin a specific release:
 <ul>
-<li><code>buildpacksio/pack:0.35.1</code></li>
+<li><code>buildpacksio/pack:0.36.0</code></li>
 <li><a href="https://hub.docker.com/r/buildpacksio/pack/tags">other versions</a></li>
 </ul>
 </li>

index.html

@@ -2,7 +2,7 @@
 <html lang="en">
 
 <head>
-	<meta name="generator" content="Hugo 0.139.2">
+	<meta name="generator" content="Hugo 0.139.4">