fix: pin luxon to fix build (#1315)

* fix: pin luxon to fix build

* chore: changelog

Author: dervoeti

CHANGELOG.md

@@ -49,6 +49,7 @@ All notable changes to this project will be documented in this file.
 - hbase: move hbck2.env to hbase-operator-tools image and add log4j2 properties for this tool ([#1300]).
 - hbase: replace `sed` calls with `config-utils template` where possible ([#1301]).
 - superset: Fix the 4.1.2 build when building from source ([#1309])
+- superset: Pin `luxon` to version 3.6.1 to fix build ([#1315])
 
 ### Fixed
 
@@ -106,6 +107,7 @@ All notable changes to this project will be documented in this file.
 [#1308]: https://github.com/stackabletech/docker-images/pull/1308
 [#1309]: https://github.com/stackabletech/docker-images/pull/1309
 [#1311]: https://github.com/stackabletech/docker-images/pull/1311
+[#1315]: https://github.com/stackabletech/docker-images/pull/1315
 
 ## [25.7.0] - 2025-07-23
 

superset/stackable/patches/4.1.2/0001-fix-pin-luxon-to-fix-build.patch

@@ -0,0 +1,23 @@
+From 1b11f3ff47f46105289f7f9dcaa4fc10d6ea3571 Mon Sep 17 00:00:00 2001
+From: dervoeti <[email protected]>
+Date: Wed, 22 Oct 2025 17:04:19 +0200
+Subject: fix: pin luxon to fix build
+
+For some reason npm tries to use a newer version of luxon than the version in the lock file. I suspect this might be related to how npm before version 11 handles workspace dependencies in lock files. The luxon version is set to 3.6.1 now to prevent npm from trying to select a newer version, so that the same packages as in the original Superset build are used.
+---
+ superset-frontend/package.json | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/superset-frontend/package.json b/superset-frontend/package.json
+index ebca197a25..3490ecaa93 100644
+--- a/superset-frontend/package.json
++++ b/superset-frontend/package.json
+@@ -148,7 +148,7 @@
+     "json-bigint": "^1.0.0",
+     "json-stringify-pretty-compact": "^2.0.0",
+     "lodash": "^4.17.21",
+-    "luxon": "^3.5.0",
++    "luxon": "3.6.1",
+     "mapbox-gl": "^2.10.0",
+     "markdown-to-jsx": "^7.4.7",
+     "match-sorter": "^6.3.4",

superset/stackable/patches/4.1.2/0001-fix.patch

@@ -0,0 +1,23 @@
+From 23a71074574336d3cbdf0b27e3650bf21b39b337 Mon Sep 17 00:00:00 2001
+From: dervoeti <[email protected]>
+Date: Wed, 22 Oct 2025 16:42:08 +0200
+Subject: fix: pin luxon to fix build
+
+For some reason npm tries to use a newer version of luxon than the version in the lock file. I suspect this might be related to how npm before version 11 handles workspace dependencies in lock files. The luxon version is set to 3.6.1 now to prevent npm from trying to select a newer version, so that the same packages as in the original Superset build are used.
+---
+ superset-frontend/package.json | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/superset-frontend/package.json b/superset-frontend/package.json
+index 066ce89764..cd6ca2a53f 100644
+--- a/superset-frontend/package.json
++++ b/superset-frontend/package.json
+@@ -148,7 +148,7 @@
+     "json-bigint": "^1.0.0",
+     "json-stringify-pretty-compact": "^2.0.0",
+     "lodash": "^4.17.21",
+-    "luxon": "^3.5.0",
++    "luxon": "3.6.1",
+     "mapbox-gl": "^2.10.0",
+     "markdown-to-jsx": "^7.4.7",
+     "match-sorter": "^6.3.4",