diff --git a/.github/workflows/build-container.yml b/.github/workflows/build-container.yml
index 139f09e..40df554 100644
--- a/.github/workflows/build-container.yml
+++ b/.github/workflows/build-container.yml
@@ -5,7 +5,6 @@ on:
   # push:
   #   branches:
   #     - main
-  workflow_dispatch:
 
 defaults:
   run:
diff --git a/.github/workflows/build-extension.yml b/.github/workflows/build-extension.yml
index a354a0c..83c4661 100644
--- a/.github/workflows/build-extension.yml
+++ b/.github/workflows/build-extension.yml
@@ -9,8 +9,6 @@ on:
   pull_request:
     branches:
       - main
-  workflow_dispatch:
-
 
 defaults:
   run:
diff --git a/docs/developer/README.md b/docs/developer/README.md
index a78ff36..c64cb08 100644
--- a/docs/developer/README.md
+++ b/docs/developer/README.md
@@ -47,7 +47,7 @@ In order to assist Epinio UI end-to-end tests we should ensure that it's easy to
 
 ### Built-in / Embedded
 
-Any merge to `main` will kick off a build of the epinio extension with a version matching that from `dashboard/pkg/epinio/package.json. If there is an existing release with the same name it will overwrite it.
+Any merge to `main` that changes `dashboard/pkg/epinio/package.json` will kick off a build of the epinio extension with a version matching that from `dashboard/pkg/epinio/package.json`. If there is an existing release with the same name it will overwrite it. This is done via the `Build and Release Extension` gh action. Builds won't be available until the `pages-build-deployment` gh action completes as well.
 
 ### Standalone