Merge branch 'main' into dependabot/github_actions/actions/download-artifact-4

Author: AidanDelaney

.github/workflows/main.yml

@@ -18,7 +18,7 @@ jobs:
       - name: Git Checkout
         uses: actions/checkout@v4
       - name: Setup Go environment
-        uses: actions/setup-go@v4
+        uses: actions/setup-go@v5
         with:
           go-version: '1.x'
       - name: Install Dependencies

Makefile

@@ -170,22 +170,8 @@ tools-tidy:
 	cd tools; go mod tidy
 
 .PHONY: prepare-for-pr
-prepare-for-pr: check-links test tools-tidy katacoda
+prepare-for-pr: check-links test tools-tidy
 	@echo "========"
 	@echo "It looks good! :)"
 	@echo "Make sure to commit all changes!"
 	@echo "========"
-
-.PHONY: katacoda
-katacoda:
-	@echo "========"
-	@echo "Generating Katacoda docs..."
-	@go run katacoda/main.go
-	@echo "All done!"
-	@echo "========"
-
-.PHONY: check-katacoda
-check-katacoda: katacoda
-	@echo "Checking if Katacoda docs are up-to-date..."
-	@git diff --quiet HEAD -- katacoda/scenarios || ( echo "Katacoda docs are not up-to-date! Please run 'make katacoda' and commit the katacoda/scenarios folder" && exit 1)
-	@echo "All katacoda docs are up-to-date"

content/docs/app-developer-guide/_index.md

@@ -5,8 +5,6 @@ include_summaries=true
 expand=true
 +++
 
-{{< katacoda-button href="https://katacoda.com/buildpacks/scenarios/app-developer-guide" color="green" >}} Learn on Katacoda {{</>}}
-
 ## Prerequisites
 
 A lot of the examples used within this guide will require the following: 

content/docs/app-developer-guide/build-an-app.md

@@ -62,12 +62,6 @@ docker run --rm -p 8080:8080 sample-app
 The app should now be running and accessible via [localhost:8080](http://localhost:8080).
 <!--+end+-->
 
-<!--+ `
-Now open your favorite browser and point it to port "8080" of your host and take a minute to enjoy the view.
-
-On Katacoda you can do this by [clicking here](https://[[HOST_SUBDOMAIN]]-8080-[[KATACODA_HOST]].environments.katacoda.com)
-` +-->
-
 ## What about ARM apps?
 
 Linux ARM image builds are now supported!

content/docs/app-developer-guide/using-inline-buildpacks.md

@@ -23,7 +23,7 @@ version = "1.0"
 id = "me/rake-tasks"
 
   [io.buildpacks.group.script]
-  api = "0.6"
+  api = "0.10"
   inline = "rake package"
 ```
 
@@ -38,7 +38,7 @@ Inline buildpacks aren't constrained to a single command, however. You can defin
 id = "me/cleanup"
 
   [io.buildpacks.group.script]
-  api = "0.9"
+  api = "0.10"
   inline = """
 set -e
 source scripts/utils.sh

content/docs/app-journey.md

@@ -7,15 +7,13 @@ getting-started=true
 ## Pack for the journey
 
 In this tutorial, we'll explain how to use `pack` and **buildpacks** to create a runnable app image from source code.
-<!--+if false+-->
-{{< katacoda-button href="https://katacoda.com/buildpacks/scenarios/app-journey" color="green" >}} Learn on Katacoda {{</>}}
 
 In order to run the build process in an isolated fashion, `pack` uses **Docker**. That means you'll need to make sure you have both `docker` and `pack` installed:
 
 {{< download-button href="https://store.docker.com/search?type=edition&offering=community" color="blue" >}} Install Docker {{</>}}
 
 {{< download-button href="/docs/install-pack" color="pink" >}} Install pack {{</>}}
-<!--+end+-->
+
 > **NOTE:** `pack` is only one implementation of the [Cloud Native Buildpacks Platform Specification][cnb-platform-spec]. Additionally, not all Cloud Native Buildpacks Platforms require Docker.
 
 [cnb-platform-spec]: https://github.com/buildpacks/spec/blob/main/platform.md
@@ -86,14 +84,8 @@ To test out your new app image locally, you can run it with Docker:
 docker run --rm -p 8080:8080 myapp
 ```
 <!--+- "{{execute}}"+-->
-<!--+- if false+-->
 Now hit [`localhost:8080`](http://localhost:8080) in your favorite browser and take a minute to enjoy the view.
-<!--+- end+-->
-<!--+ `
-Now open your favorite browser and point it to port "8080" of your host and take a minute to enjoy the view.
 
-On Katacoda you can do this by [clicking here](https://[[HOST_SUBDOMAIN]]-8080-[[KATACODA_HOST]].environments.katacoda.com)
-` +-->
 
 ### Take your image to the skies
 
@@ -107,9 +99,7 @@ deploying your new image to your favorite cloud!
 
 Windows image builds are now supported!
 
-<!--+- if false+-->
 <a href="/docs/app-developer-guide/build-a-windows-app" class="button bg-blue">Windows build guide</a>
-<!--+end+-->
 
 [builder]: /docs/concepts/components/builder/
 [buildpack]: /docs/concepts/components/buildpack/

content/docs/buildpack-author-guide/create-buildpack/adding-bill-of-materials.md

@@ -43,7 +43,7 @@ First, annotate the `buildpack.toml` to specify that it emits CycloneDX:
 <!-- test:file=node-js-buildpack/buildpack.toml -->
 ```toml
 # Buildpack API version
-api = "0.8"
+api = "0.10"
 
 # Buildpack ID and metadata
 [buildpack]
@@ -144,7 +144,7 @@ EOL
 cat >> "${CNB_LAYERS_DIR}/launch.toml" << EOL
 [[processes]]
 type = "web"
-command = "node app.js"
+command = ["node", "app.js"]
 default = true
 EOL
 

content/docs/buildpack-author-guide/create-buildpack/building-blocks-cnb.md

@@ -17,7 +17,7 @@ Example:
 <!-- test:exec -->
 ```bash
 pack buildpack new examples/node-js \
-    --api 0.8 \
+    --api 0.10 \
     --path node-js-buildpack \
     --version 0.0.1 \
     --stacks io.buildpacks.samples.stacks.jammy
@@ -40,7 +40,7 @@ You will have `node-js-buildpack/buildpack.toml`<!--+"{{open}}"+--> in your buil
 <!-- test:file=node-js-buildpack/buildpack.toml -->
 ```toml
 # Buildpack API version
-api = "0.8"
+api = "0.10"
 
 # Buildpack ID and metadata
 [buildpack]
@@ -91,7 +91,7 @@ These two files are executable `detect` and `build` scripts. You are now able to
 
 ### Using your buildpack with `pack`
 
-In order to test your buildpack, you will need to run the buildpack against your sample Ruby app using the `pack` CLI.
+In order to test your buildpack, you will need to run the buildpack against your sample Node.js app using the `pack` CLI.
 
 Set your default [builder][builder] by running the following:
 
@@ -117,7 +117,7 @@ pack build test-node-js-app --path ./node-js-sample-app --buildpack ./node-js-bu
 ```
 <!--+- "{{execute}}"+-->
 
-The `pack build` command takes in your Ruby sample app as the `--path` argument and your buildpack as the `--buildpack` argument.
+The `pack build` command takes in your Node.js sample app as the `--path` argument and your buildpack as the `--buildpack` argument.
 
 After running the command, you should see that it failed to detect, as the `detect` script is currently written to simply error out.
 
@@ -137,4 +137,4 @@ ERROR: failed to detect: buildpack(s) failed with err
 <a href="/docs/buildpack-author-guide/create-buildpack/detection" class="button bg-pink">Next Step</a>
 
 [builder]: /docs/concepts/components/builder
-<!--+ end +-->
+<!--+ end +-->

content/docs/buildpack-author-guide/create-buildpack/caching.md

@@ -54,13 +54,13 @@ cat > "${CNB_LAYERS_DIR}/launch.toml" << EOL
 # our web process
 [[processes]]
 type = "web"
-command = "node app.js"
+command = ["node", "app.js"]
 default = true
 
 # our debug process
 [[processes]]
 type = "debug"
-command = "node --inspect app.js"
+command = ["node", "--inspect", "app.js"]
 EOL
 ```
 
@@ -121,7 +121,7 @@ EOL
 cat >> "${CNB_LAYERS_DIR}/launch.toml" << EOL
 [[processes]]
 type = "web"
-command = "node app.js"
+command = ["node", "app.js"]
 default = true
 EOL
 ```

content/docs/buildpack-author-guide/create-buildpack/make-app-runnable.md

@@ -15,7 +15,7 @@ To make your app runnable, a default start command must be set. You'll need to a
 cat > "${CNB_LAYERS_DIR}/launch.toml" << EOL
 [[processes]]
 type = "web"
-command = "node app.js"
+command = ["node", "app.js"]
 default = true
 EOL
 
@@ -48,7 +48,7 @@ echo -e '[types]\nlaunch = true' > "${CNB_LAYERS_DIR}/node-js.toml"
 cat > "${CNB_LAYERS_DIR}/launch.toml" << EOL
 [[processes]]
 type = "web"
-command = "node app.js"
+command = ["node", "app.js"]
 default = true
 EOL
 ```