From df671ea994f2ccc8ea17b507378a8e0c572eff1c Mon Sep 17 00:00:00 2001 From: lebaudantoine Date: Wed, 22 Oct 2025 05:29:41 +0200 Subject: [PATCH] =?UTF-8?q?=F0=9F=90=9B(frontend)=20posthog-cli=200.5.0=20?= =?UTF-8?q?release=20introduced=20breaking=20changes?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Posthog-cli version wasn't pinned. Please check issue #39846, which describe our issue, starting 0.5.0, the cli needs an API token and a Project ID. Pin to the last stable version we used 0.4.8, and wait a bit they already released a 0.5.1 that mitigate some of the breaking change. I would wait the 0.5.x to be stable and battle tested by other developpers before switching. Also as I consider switching the Error tracking to sentry. --- docker/dinum-frontend/Dockerfile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docker/dinum-frontend/Dockerfile b/docker/dinum-frontend/Dockerfile index cf8680e0..1e94968a 100644 --- a/docker/dinum-frontend/Dockerfile +++ b/docker/dinum-frontend/Dockerfile @@ -24,7 +24,7 @@ RUN npm run build # Inject PostHog sourcemap metadata into the built assets # This metadata is essential for correctly mapping errors to source maps in production RUN set -e && \ - npx @posthog/cli sourcemap inject --directory ./dist/assets + npx @posthog/cli@0.4.8 sourcemap inject --directory ./dist/assets COPY ./docker/dinum-frontend/dinum-styles.css \ ./dist/assets/