diff --git a/.github/actions/setup-clightning/action.yaml b/.github/actions/setup-clightning/action.yaml
index 970df42..850881d 100644
--- a/.github/actions/setup-clightning/action.yaml
+++ b/.github/actions/setup-clightning/action.yaml
@@ -5,7 +5,7 @@ inputs:
   checkout-version:
     description: Core lightning version
     required: true
-    default: 'v23.08'
+    default: 'v23.11'
 
 runs:
   using: 'composite'
diff --git a/.github/actions/setup-lnd-lsp/action.yaml b/.github/actions/setup-lnd-lsp/action.yaml
index 8074010..cf612c0 100644
--- a/.github/actions/setup-lnd-lsp/action.yaml
+++ b/.github/actions/setup-lnd-lsp/action.yaml
@@ -5,7 +5,7 @@ inputs:
   lsp-ref:
     description: 'The Git reference for the LSP version of LND'
     required: true
-    default: 'breez-node-v0.16.2-beta'
+    default: 'breez-node-v0.17.2-beta'
 
   go-version:
     description: 'The Go version for building LND'
diff --git a/README.md b/README.md
index 49b971b..b74e3be 100644
--- a/README.md
+++ b/README.md
@@ -29,8 +29,8 @@ The lsp supports probing non-mpp payments if the payment hash for probing is sha
 In order to run the integration tests, you need:
 - Docker running
 - python3 installed
-- A development build of lightningd v23.08
-- lnd v0.16.4 lsp version https://github.com/breez/lnd/commit/cebcdf1b17fdedf7d69207d98c31cf8c3b257531
+- A development build of lightningd v23.11
+- lnd v0.17.2 lsp version https://github.com/breez/lnd/commit/0c939786ced78a981bd77c7da628bfcf86ada568
 - lnd v0.16.4 breez client version https://github.com/breez/lnd/commit/3c0854adcfc924a6d759a6ee4640c41266b9f8b4
 - bitcoind (tested with v23.0)
 - bitcoin-cli (tested with v23.0)
diff --git a/deploy/deploy.yml b/deploy/deploy.yml
index 6852edf..bb702a2 100644
--- a/deploy/deploy.yml
+++ b/deploy/deploy.yml
@@ -222,6 +222,7 @@ Resources:
             sudo mkdir /etc/lightningd
             #cat <<EOL | sudo tee /home/lightning/.lightning/config
             cat <<EOL | sudo tee /etc/lightningd/lightningd.conf
+            developer
             bitcoin-rpcuser=cln
             bitcoin-rpcpassword=$RPCPASSWORD
             bitcoin-rpcconnect=127.0.0.1
@@ -240,8 +241,8 @@ Resources:
             chmod 755 /etc/lightningd/
             git clone https://github.com/ElementsProject/lightning.git /opt/lightning
             cd /opt/lightning
-            git checkout v23.05
-            ./configure --enable-developer
+            git checkout v23.11
+            ./configure
             make
             make install
             cat <<EOL | sudo tee /etc/systemd/system/lightningd.service
diff --git a/deploy/lspd-install.sh b/deploy/lspd-install.sh
index fe2c11f..d852adc 100644
--- a/deploy/lspd-install.sh
+++ b/deploy/lspd-install.sh
@@ -153,6 +153,7 @@ sudo mkdir /home/lightning/.lightning/
 sudo mkdir /etc/lightningd
 #cat <<EOL | sudo tee /home/lightning/.lightning/config
 cat <<EOL | sudo tee /etc/lightningd/lightningd.conf
+developer
 bitcoin-rpcuser=cln
 bitcoin-rpcpassword=$RPCPASSWORD
 bitcoin-rpcconnect=127.0.0.1
@@ -171,8 +172,8 @@ EOL
 chmod 755 /etc/lightningd/
 git clone https://github.com/ElementsProject/lightning.git /opt/lightning
 cd /opt/lightning
-git checkout v23.05
-./configure --enable-developer
+git checkout v23.11
+./configure
 make
 make install
 cat <<EOL | sudo tee /etc/systemd/system/lightningd.service
diff --git a/docs/CLN.md b/docs/CLN.md
index 8d979a2..352cab0 100644
--- a/docs/CLN.md
+++ b/docs/CLN.md
@@ -1,7 +1,7 @@
 
 ## Installation instructions for core lightning and lspd
 ### Requirements 
-- CLN (compiled with developer mode on)
+- CLN
 - lspd
 - lspd plugin for cln
 - postgresql
@@ -61,6 +61,7 @@ NODES='[ { "name": "${LSPName}", "nodePubkey": "$PUBKEY", "lspdPrivateKey": "$LS
 In order to run lspd on top of CLN, you need to run the lspd process and run cln with the provided cln plugin.
 
 1. Run cln with the following options set:
+    - `--developer`: to allow passing the `--dev-allowdustreserve` flag
     - `--plugin=/path/to/lspd_plugin`: to use lspd as plugin
     - `--max-concurrent-htlcs=30`: In order to use zero reserve channels on the client side, (local max_accepted_htlcs + remote max_accepted_htlcs + 2) * dust limit must be lower than the channel capacity. Reduce max-concurrent-htlcs or increase channel capacity accordingly.
     - `--dev-allowdustreserve=true`: In order to allow zero reserve on the client side (requires developer mode turned on)