From 7fde2fba50dd2e6c4d54d824d759c39ef5586b11 Mon Sep 17 00:00:00 2001 From: Guilherme Gomes Date: Tue, 14 Jul 2026 16:47:25 -0300 Subject: [PATCH] fix(docker): restore the patches/ directory the builder copies The only patch file (patches/baileys+7.0.0-rc.6.patch) was dropped in dd552c77 when Baileys moved to rc13, which left the directory untracked. The builder still runs COPY ./patches ./patches before npm ci, so every image build since has failed with: failed to compute cache key: "/patches": not found. Keep the directory tracked (patch-package is still wired into postinstall) so the COPY resolves and a future patch works by just dropping in a .patch file. --- patches/README.md | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 patches/README.md diff --git a/patches/README.md b/patches/README.md new file mode 100644 index 000000000..b0cd64eb9 --- /dev/null +++ b/patches/README.md @@ -0,0 +1,8 @@ +# patches/ + +`patch-package` patches for third-party dependencies. They are applied by the +`postinstall` hook (`package.json`) and re-applied inside the Docker builder, +which copies this directory before `npm ci` (`COPY ./patches ./patches`). + +Keep this directory tracked even when there is no patch: removing it breaks the +Docker build, since the `COPY` above cannot resolve a path that does not exist.