From 58af85fb137af1cf493b130f5416170be56f2959 Mon Sep 17 00:00:00 2001
From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com>
Date: Thu, 17 Oct 2024 08:34:15 +0000
Subject: [PATCH 1/2] chore(deps): update gcr.io/kaniko-project/executor docker
 tag to v1.23.2

---
 Dockerfile | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Dockerfile b/Dockerfile
index 35a822c..2c0fd25 100644
--- a/Dockerfile
+++ b/Dockerfile
@@ -2,7 +2,7 @@ FROM alpine as certs
 
 RUN apk --update add ca-certificates
 
-FROM gcr.io/kaniko-project/executor:v1.22.0-debug
+FROM gcr.io/kaniko-project/executor:v1.23.2-debug
 
 SHELL ["/busybox/sh", "-c"]
 

From be5ce625a52485739db88cc75ebb8a9f8d269bd4 Mon Sep 17 00:00:00 2001
From: Alex Viscreanu <alexviscreanu@gmail.com>
Date: Thu, 7 Nov 2024 19:00:36 +0100
Subject: [PATCH 2/2] docs: add warning about kaniko lacking maintainers

---
 README.md | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/README.md b/README.md
index 30f8528..56d6940 100644
--- a/README.md
+++ b/README.md
@@ -1,5 +1,8 @@
 # Kaniko image builder
 
+> [!WARNING]  
+> The kaniko project no longer seems to [have maintainers](https://github.com/GoogleContainerTools/kaniko/issues/3348). Keep this in mind before deciding to use kaniko as your image builder.
+
 This Action uses the [kaniko](https://github.com/GoogleContainerTools/kaniko) executor instead of the docker daemon. Kaniko builds the image
 by extracting the filesystem of the base image, making the changes in the user space, snapshotting any change and appending it to the base
 image filesystem.