diff --git a/.github/workflows/build-packages.yaml b/.github/workflows/build-packages.yaml
index 5206947d..dde7fa07 100644
--- a/.github/workflows/build-packages.yaml
+++ b/.github/workflows/build-packages.yaml
@@ -14,6 +14,7 @@ jobs:
     steps:
       - uses: actions/checkout@v4
         with:
+          submodules: true
           persist-credentials: false
 
       - name: Setup NodeJS
diff --git a/.github/workflows/dev-packages.yaml b/.github/workflows/dev-packages.yaml
index 67b0c882..8b39bd06 100644
--- a/.github/workflows/dev-packages.yaml
+++ b/.github/workflows/dev-packages.yaml
@@ -1,16 +1,8 @@
 # Action to publish packages under the `next` tag for testing
 # Packages are versioned as `0.0.0-dev.{short-sha}`
-# Submodule packages are versioned by default, but can be disabled
-# if using a package from the external submodule repo.
 name: Packages Deploy
 
-on:
-  workflow_dispatch:
-    inputs:
-      include_submodules:
-        type: boolean
-        description: Dev version submodule packages?
-        default: true
+on: workflow_dispatch
 
 jobs:
   publish:
@@ -19,7 +11,7 @@ jobs:
     steps:
       - uses: actions/checkout@v4
         with:
-          submodules: ${{ github.event.inputs.include_submodules }}
+          submodules: true
           persist-credentials: false
 
       - name: Setup NodeJS
diff --git a/README.md b/README.md
index 05750b43..cd910d18 100644
--- a/README.md
+++ b/README.md
@@ -42,11 +42,13 @@ yarn build:packages
 
 
 ### Development Packages
-Development packages can be published by manually triggering the `dev-packages` workflow. Development packages are versioned as `0.0.0-dev.{short-sha}`. Submodule packages are checked out, versioned and published by default, but this can be disabled if using submodule packages which are published from it's own repository.
+Development packages can be published by manually triggering the `dev-packages` workflow. Development packages are versioned as `0.0.0-dev.{short-sha}`. 
 
 ### Production Packages
 Packages should be versioned with Lerna after PR approval.
 
+Submodule production packages should be versioned, tagged and published from their own repository. Any dependencies should be updated here (if applicable) before versioning local packages.
+
 ```bash
 lerna version  --no-private
 ```