diff --git a/.github/workflows/checks.yml b/.github/workflows/checks.yml
index dd61a67a..aed34d8e 100644
--- a/.github/workflows/checks.yml
+++ b/.github/workflows/checks.yml
@@ -9,44 +9,44 @@ jobs:
     name: Code formatting
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v3
-      - uses: actions/setup-node@v3
+      - uses: actions/checkout@v4
+      - uses: actions/setup-node@v4
         with:
           node-version: 18
-      - uses: c-hive/gha-yarn-cache@v2
+          cache: 'yarn'
       - run: yarn
       - run: yarn verify:formatting
   codeStyles:
     name: Code styles
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v3
-      - uses: actions/setup-node@v3
+      - uses: actions/checkout@v4
+      - uses: actions/setup-node@v4
         with:
           node-version: 18
-      - uses: c-hive/gha-yarn-cache@v2
+          cache: 'yarn'
       - run: yarn
       - run: yarn verify:code-styles
   types:
     name: Types check
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v3
-      - uses: actions/setup-node@v3
+      - uses: actions/checkout@v4
+      - uses: actions/setup-node@v4
         with:
           node-version: 18
-      - uses: c-hive/gha-yarn-cache@v2
+          cache: 'yarn'
       - run: yarn
       - run: yarn typecheck
   tests:
     name: Tests
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v3
-      - uses: actions/setup-node@v3
+      - uses: actions/checkout@v4
+      - uses: actions/setup-node@v4
         with:
           node-version: 18
-      - uses: c-hive/gha-yarn-cache@v2
+          cache: 'yarn'
       - run: yarn
       - run: yarn test --coverage
       - run: bash <(curl -s https://codecov.io/bash)
diff --git a/.github/workflows/firebase-hosting-merge.yml b/.github/workflows/firebase-hosting-merge.yml
index b8b5f0bc..1d638de5 100644
--- a/.github/workflows/firebase-hosting-merge.yml
+++ b/.github/workflows/firebase-hosting-merge.yml
@@ -11,10 +11,10 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       # Checkout
-      - uses: actions/checkout@v3
+      - uses: actions/checkout@v4
 
       # Build
-      - uses: actions/setup-node@v3
+      - uses: actions/setup-node@v4
         with:
           node-version: 18
           cache: yarn
diff --git a/.github/workflows/firebase-hosting-pull-request.yml b/.github/workflows/firebase-hosting-pull-request.yml
index 9b9a6d75..9aee3c78 100644
--- a/.github/workflows/firebase-hosting-pull-request.yml
+++ b/.github/workflows/firebase-hosting-pull-request.yml
@@ -9,10 +9,10 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       # Checkout
-      - uses: actions/checkout@v3
+      - uses: actions/checkout@v4
 
       # Build
-      - uses: actions/setup-node@v3
+      - uses: actions/setup-node@v4
         with:
           node-version: 18
           cache: yarn
diff --git a/.github/workflows/search-trigger.yml b/.github/workflows/search-trigger.yml
index a2828301..615cd1ba 100644
--- a/.github/workflows/search-trigger.yml
+++ b/.github/workflows/search-trigger.yml
@@ -6,7 +6,7 @@ jobs:
     name: Update search index
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v3
+      - uses: actions/checkout@v4
       - uses: darrenjennings/algolia-docsearch-action@da2ed379c147b356d60dbfec68bdcfacb2791a98
         with:
           algolia_application_id: 'E57FOT37U9'
diff --git a/docs/03-github-cloud-runner/03-examples/02-github-examples/02-aws.mdx b/docs/03-github-cloud-runner/03-examples/02-github-examples/02-aws.mdx
index 2317f92f..8bafa486 100644
--- a/docs/03-github-cloud-runner/03-examples/02-github-examples/02-aws.mdx
+++ b/docs/03-github-cloud-runner/03-examples/02-github-examples/02-aws.mdx
@@ -17,7 +17,7 @@ If you're using GitHub you can use a GitHub Action:
 
 ```yaml
 - name: Configure AWS Credentials
-  uses: aws-actions/configure-aws-credentials@v1
+  uses: aws-actions/configure-aws-credentials@v4
   with:
     aws-access-key-id: ${{ secrets.AWS_ACCESS_KEY_ID }}
     aws-secret-access-key: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
diff --git a/docs/03-github/01-getting-started.mdx b/docs/03-github/01-getting-started.mdx
index f0cf99e6..db490d58 100644
--- a/docs/03-github/01-getting-started.mdx
+++ b/docs/03-github/01-getting-started.mdx
@@ -77,7 +77,7 @@ jobs:
     steps:
       # Checkout
       - name: Checkout repository
-        uses: actions/checkout@v3
+        uses: actions/checkout@v4
         with:
           lfs: true
 
@@ -91,7 +91,7 @@ jobs:
 
       # Test
       - name: Run tests
-        uses: game-ci/unity-test-runner@v3
+        uses: game-ci/unity-test-runner@v4
         env:
           UNITY_LICENSE: ${{ secrets.UNITY_LICENSE }}
         with:
@@ -99,7 +99,7 @@ jobs:
 
       # Build
       - name: Build project
-        uses: game-ci/unity-builder@v3
+        uses: game-ci/unity-builder@v4
         env:
           UNITY_LICENSE: ${{ secrets.UNITY_LICENSE }}
           UNITY_EMAIL: ${{ secrets.UNITY_EMAIL }}
@@ -132,7 +132,7 @@ jobs:
     steps:
       # Checkout (without LFS)
       - name: Checkout repository
-        uses: actions/checkout@v3
+        uses: actions/checkout@v4
 
       # Git LFS
       - name: Create LFS file list
@@ -161,7 +161,7 @@ jobs:
 
       # Test
       - name: Run tests
-        uses: game-ci/unity-test-runner@v3
+        uses: game-ci/unity-test-runner@v4
         env:
           UNITY_LICENSE: ${{ secrets.UNITY_LICENSE }}
         with:
@@ -169,7 +169,7 @@ jobs:
 
       # Build
       - name: Build project
-        uses: game-ci/unity-builder@v3
+        uses: game-ci/unity-builder@v4
         env:
           UNITY_LICENSE: ${{ secrets.UNITY_LICENSE }}
           UNITY_EMAIL: ${{ secrets.UNITY_EMAIL }}
@@ -202,7 +202,7 @@ jobs:
     steps:
       # Checkout
       - name: Checkout repository
-        uses: actions/checkout@v3
+        uses: actions/checkout@v4
         with:
           lfs: true
 
@@ -216,7 +216,7 @@ jobs:
 
       # Test
       - name: Run tests
-        uses: game-ci/unity-test-runner@v3
+        uses: game-ci/unity-test-runner@v4
         env:
           UNITY_LICENSE: ${{ secrets.UNITY_LICENSE }}
         with:
@@ -228,7 +228,7 @@ jobs:
     steps:
       # Checkout
       - name: Checkout repository
-        uses: actions/checkout@v3
+        uses: actions/checkout@v4
         with:
           lfs: true
 
@@ -242,7 +242,7 @@ jobs:
 
       # Build
       - name: Build project
-        uses: game-ci/unity-builder@v3
+        uses: game-ci/unity-builder@v4
         env:
           UNITY_LICENSE: ${{ secrets.UNITY_LICENSE }}
           UNITY_EMAIL: ${{ secrets.UNITY_EMAIL }}
@@ -294,7 +294,7 @@ jobs:
           - Android # Build an Android player.
           - WebGL # WebGL.
     steps:
-      - uses: actions/checkout@v3
+      - uses: actions/checkout@v4
         with:
           fetch-depth: 0
           lfs: true
@@ -308,7 +308,7 @@ jobs:
             Library-${{ matrix.projectPath }}-${{ matrix.targetPlatform }}-
             Library-${{ matrix.projectPath }}-
             Library-
-      - uses: game-ci/unity-test-runner@v3
+      - uses: game-ci/unity-test-runner@v4
         id: testRunner
         env:
           UNITY_LICENSE: ${{ secrets.UNITY_LICENSE }}
@@ -323,7 +323,7 @@ jobs:
           path: ${{ steps.testRunner.outputs.artifactsPath }}
       - if: matrix.targetPlatform == 'Android'
         uses: jlumbroso/free-disk-space@v1.2.0
-      - uses: game-ci/unity-builder@v3
+      - uses: game-ci/unity-builder@v4
         env:
           UNITY_LICENSE: ${{ secrets.UNITY_LICENSE }}
           UNITY_EMAIL: ${{ secrets.UNITY_EMAIL }}
@@ -340,7 +340,7 @@ jobs:
 
   buildForWindowsBasedPlatforms:
     name: Build for ${{ matrix.targetPlatform }}
-    runs-on: windows-2019
+    runs-on: windows-2022
     strategy:
       fail-fast: false
       matrix:
@@ -356,7 +356,7 @@ jobs:
           - WSAPlayer # Build a UWP App.
 
     steps:
-      - uses: actions/checkout@v3
+      - uses: actions/checkout@v4
         with:
           fetch-depth: 0
           lfs: true
@@ -370,7 +370,7 @@ jobs:
             Library-${{ matrix.projectPath }}-${{ matrix.targetPlatform }}-
             Library-${{ matrix.projectPath }}-
             Library-
-      - uses: game-ci/unity-builder@v3
+      - uses: game-ci/unity-builder@v4
         env:
           UNITY_LICENSE: ${{ secrets.UNITY_LICENSE }}
           UNITY_EMAIL: ${{ secrets.UNITY_EMAIL }}
@@ -400,7 +400,7 @@ jobs:
           - StandaloneOSX # Build a macOS standalone.
 
     steps:
-      - uses: actions/checkout@v3
+      - uses: actions/checkout@v4
         with:
           fetch-depth: 0
           lfs: true
@@ -416,7 +416,7 @@ jobs:
             Library-${{ matrix.projectPath }}-
             Library-
 
-      - uses: game-ci/unity-builder@v3
+      - uses: game-ci/unity-builder@v4
         env:
           UNITY_LICENSE: ${{ secrets.UNITY_LICENSE }}
           UNITY_EMAIL: ${{ secrets.UNITY_EMAIL }}
diff --git a/docs/03-github/02-activation.mdx b/docs/03-github/02-activation.mdx
index f75816d1..ba358904 100644
--- a/docs/03-github/02-activation.mdx
+++ b/docs/03-github/02-activation.mdx
@@ -17,96 +17,43 @@ Follow these steps if you are using a free version of Unity.
 
 #### Mental model
 
-1. Request an activation file for usage on GitHub
-2. Use that file to acquire a license
-3. Set the license as a secret
+1. Activate a license for use on Github via a local machine
+2. Set the license as a secret
 
-#### About the activation file
+#### Activating a license file
 
-You may use the
-[Unity - Request Activation File](https://github.com/marketplace/actions/unity-request-activation-file)
-action with the below instructions.
+1. Install [Unity Hub](https://unity.com/download) on your local machine.
+2. Log into Unity Hub with the Unity account that you are using for CI. Make sure you log into the
+   correct account or you may not activate the correct license.
+3. When prompted, activate your personal license. If you are not prompted, go to `Unity Hub` >
+   `Preferences` > `Licenses` > `Add` and choose `Get a free personal license`. You do not need to
+   install an editor on your local machine.
+4. Depending on the host you are using, find the `.ulf` file which is your Unity license in the
+   following paths:
 
-The activation file uses machine identifiers so you cannot perform this step locally.
+   - Windows: `C:\ProgramData\Unity\Unity_lic.ulf`
+   - Mac: `/Library/Application Support/Unity/Unity_lic.ulf`
+   - Linux: `~/.local/share/unity3d/Unity/Unity_lic.ulf`
 
-Let's go!
+   If you have issues locating the file, ensure you've logged into Unity Hub AND activated your
+   license. Otherwise the file will not be present. Keep in mind these folders might be hidden by
+   default, you may need to reveal hidden files to see them.
 
-#### Acquiring an activation file
+   > **Note:** The host platform you use to activate the license does not matter. You only need to
+   > get the ulf from the platform that is most convenient to you. For example, using Windows to
+   > activate your license and building on Ubuntu on Github is perfectly fine.
 
-Create a file called `.github/workflows/activation.yml` and add the below workflow definition to it:
-
-```yaml
-name: Acquire activation file
-on:
-  workflow_dispatch: {}
-jobs:
-  activation:
-    name: Request manual activation file 🔑
-    runs-on: ubuntu-latest
-    steps:
-      # Request manual activation file
-      - name: Request manual activation file
-        id: getManualLicenseFile
-        uses: game-ci/unity-request-activation-file@v2
-      # Upload artifact (Unity_v20XX.X.XXXX.alf)
-      - name: Expose as artifact
-        uses: actions/upload-artifact@v2
-        with:
-          name: ${{ steps.getManualLicenseFile.outputs.filePath }}
-          path: ${{ steps.getManualLicenseFile.outputs.filePath }}
-```
-
-Commit and push your workflow definition.
-
-#### Converting into a license
-
-:::caution
-
-**Unity no longer supports manual activation of Personal licenses**
-
-When activating your Personal Unity license, you may encounter an issue where only the "Unity Pro or
-Plus" option is available, preventing the activation of a Personal license. Here is a workaround to
-resolve this:
-
-1. Visit [license.unity3d.com](https://license.unity3d.com/manual) and upload the
-   `Unity_v20XX.X.XXXX.alf` file.
-2. On the "Activate your license" page, if the "Personal" option is not available, right-click on
-   the page and choose "Inspect" to open the browser's developer tools.
-3. Find the line of HTML that looks like this:
-   `<div class="option option-personal clear" style="display: none;">`.
-4. Delete `display: none;` from the `style` attribute to make the "Personal" option visible.
-5. Now you should be able to select the "Personal" option and proceed with the activation.
-
-You can discuss this issue or find additional assistance in the
-[related Discord conversation](https://discord.com/channels/710946343828455455/1138586951604248666)
-or [GitHub ticket](https://github.com/game-ci/documentation/issues/408).
-
-_For future reference, activating a license from the command line as documented on
-[Unity's Manual Page](https://docs.unity3d.com/Manual/ManagingYourUnityLicense.html) might be an
-alternative solution._
-
-:::
-
-Follow these (one-time) steps for simple activation.
-
-1. [Manually run](https://docs.github.com/en/actions/managing-workflow-runs/manually-running-a-workflow)
-   the above workflow.
-2. Download the manual activation file that now appeared as an artifact and extract the
-   `Unity_v20XX.X.XXXX.alf` file from the zip.
-3. Visit [license.unity3d.com](https://license.unity3d.com/manual) and upload the
-   `Unity_v20XX.X.XXXX.alf` file.
-4. You should now receive your license file (Unity_v20XX.x.ulf) as a download. It's ok if the
-   numbers don't match your Unity version exactly.
 5. Open `Github` > `<Your repository>` > `Settings` > `Secrets`.
 6. Create the following secrets;
    - `UNITY_LICENSE` - _(Copy the contents of your license file into here)_
    - `UNITY_EMAIL` - _(Add the email address that you use to login to Unity)_
    - `UNITY_PASSWORD` - _(Add the password that you use to login to Unity)_
+7. Return your personal license in Unity Hub on the local machine you used to ensure you aren't
+   using up one of the seats. You can do this by going to `Unity Hub` > `Preferences` > `Licenses`
+   and choose `Return license` on the Personal license listed in the window.
 
-**GameCI does not acquire nor store your Unity email or password. They are required for reactivating
-the license during build and test steps.**
-
-> _**Note:** When changing Unity version, you may need to repeat the same process._
+**GameCI does not acquire nor store your Unity email, password, or license file contents. They are
+required for activating the license during build and test steps.**
 
 ## Professional license
 
@@ -119,8 +66,8 @@ the license during build and test steps.**
    - `UNITY_EMAIL` - _(Add the email address that you use to login to Unity)_
    - `UNITY_PASSWORD` - _(Add the password that you use to login to Unity)_
 
-**GameCI does not acquire nor store your Unity email or password. They are required for reactivating
-the license during build and test steps.**
+**GameCI does not acquire nor store your Unity email, password, or serial number. They are required
+for activating the license during build and test steps.**
 
 > _**Note:** Do NOT follow the steps for the personal license if you have a professional license._
 
@@ -132,7 +79,7 @@ floating license will be acquired before the build, and returned after.
 Example of use:
 
 ```yaml
-- uses: game-ci/unity-builder@v3
+- uses: game-ci/unity-builder@v4
   with:
     targetPlatform: WebGL
     unityLicensingServer: [url to your license server]
diff --git a/docs/03-github/03-test-runner.mdx b/docs/03-github/03-test-runner.mdx
index 197ae5c0..cfdf0a24 100644
--- a/docs/03-github/03-test-runner.mdx
+++ b/docs/03-github/03-test-runner.mdx
@@ -29,7 +29,7 @@ license file and add it as a secret.
 Then, define the test step as follows:
 
 ```yaml
-- uses: game-ci/unity-test-runner@v3
+- uses: game-ci/unity-test-runner@v4
   env:
     UNITY_LICENSE: ${{ secrets.UNITY_LICENSE }}
   with:
@@ -48,7 +48,7 @@ Make sure you have set up these variables in the activation step.
 Define the test step as follows:
 
 ```yaml
-- uses: game-ci/unity-test-runner@v3
+- uses: game-ci/unity-test-runner@v4
   env:
     UNITY_EMAIL: ${{ secrets.UNITY_EMAIL }}
     UNITY_PASSWORD: ${{ secrets.UNITY_PASSWORD }}
@@ -66,7 +66,7 @@ floating license will be acquired before the tests run, and returned after.
 Example of use:
 
 ```yaml
-- uses: game-ci/unity-test-runner@v3
+- uses: game-ci/unity-test-runner@v4
   with:
     projectPath: path/to/your/project
     unityLicensingServer: [url to your license server]
@@ -89,7 +89,7 @@ To indicate that the test runner is being run for a Unity package rather than a
 the [`packageMode`](#packagemode) configuration option to `true`.
 
 ```yaml
-- uses: game-ci/unity-test-runner@v3
+- uses: game-ci/unity-test-runner@v4
   with:
     packageMode: true
 ```
@@ -100,7 +100,7 @@ Make sure that you explicitly pass the [`unityVersion`](#unityversion) argument,
 for the test runner to test Unity packages.
 
 ```yaml
-- uses: game-ci/unity-test-runner@v3
+- uses: game-ci/unity-test-runner@v4
   with:
     unityVersion: [your desired Unity version]
 ```
@@ -160,7 +160,7 @@ in order to view the tests results from
 [a check run](https://docs.github.com/en/rest/guides/getting-started-with-the-checks-api#about-check-runs).
 
 ```yaml
-- uses: game-ci/unity-test-runner@v3
+- uses: game-ci/unity-test-runner@v4
   with:
     githubToken: ${{ secrets.GITHUB_TOKEN }}
 ```
@@ -178,7 +178,7 @@ To do this, it is recommended to use the official Github Actions
 By default, Test Runner outputs its results to a folder named `artifacts`.
 
 ```yaml
-- uses: actions/upload-artifact@v2
+- uses: actions/upload-artifact@v3
   if: always()
   with:
     name: Test results
@@ -193,12 +193,12 @@ You can specify a different `artifactsPath` in the test runner and reference thi
 `id` of the test step.
 
 ```yaml
-- uses: game-ci/unity-test-runner@v3
+- uses: game-ci/unity-test-runner@v4
   id: myTestStep
 ```
 
 ```yaml
-- uses: actions/upload-artifact@v2
+- uses: actions/upload-artifact@v3
   if: always()
   with:
     name: Test results
@@ -212,7 +212,7 @@ read by the step's `outputs.coveragePath`. These coverage options can be configu
 test and by default will create an XML and HTML web page reports.
 
 ```yaml
-- uses: actions/upload-artifact@v2
+- uses: actions/upload-artifact@v3
   if: always()
   with:
     name: Coverage results
@@ -234,7 +234,7 @@ To do so, simply add Github Actions' official
 [cache action](https://github.com/marketplace/actions/cache) before any unity steps.
 
 ```yaml
-- uses: actions/cache@v2
+- uses: actions/cache@v3
   with:
     path: path/to/your/project/Library
     key: Library-MyProjectName-TargetPlatform
@@ -266,7 +266,7 @@ Specific docker image that should be used for testing the project. If packageMod
 image must have [`jq`](https://jqlang.github.io/jq/) installed.
 
 ```yaml
-- uses: game-ci/unity-test-runner@v3
+- uses: game-ci/unity-test-runner@v4
   with:
     customImage: 'unityci/editor:2020.1.14f1-base-0'
 ```
@@ -293,7 +293,7 @@ Parameters must start with a hyphen (`-`) and may be followed by a value (withou
 Parameters without a value will be considered booleans (with a value of true).
 
 ```yaml
-- uses: game-ci/unity-test-runner@v3
+- uses: game-ci/unity-test-runner@v4
   with:
     customParameters: -profile SomeProfile -someBoolean -someValue exampleValue
 ```
@@ -420,6 +420,36 @@ See [Testing Unity packages](#testing-unity-packages) for more information.
 
 _**required:** `false`_ _**default:** `false`_
 
+#### dockerCpuLimit
+
+Number of CPU cores to assign to the Docker container. Defaults to all available cores when no value
+is specified. Can accept fractional values, e.g., 0.5 for half of a CPU core's execution time.
+
+_**required:** `false`_ _**default:** `""`_
+
+#### dockerMemoryLimit
+
+Amount of memory to assign to the Docker container. Defaults to 95% of total system memory rounded
+down to the nearest megabyte on Linux and 80% on Windows. If the platform is unrecognized, it
+defaults to 75% of total system memory. To manually specify a value, use the format
+\<number\>\<unit\>. The units can be:
+
+- `m`: Megabytes (e.g., 512m = 512 megabytes)
+- `g`: Gigabytes (e.g., 4g = 4 gigabytes)
+
+_**required:** `false`_ _**default:** `""`_
+
+#### dockerIsolationMode
+
+Isolation mode to use for the Docker container when running on Windows. Can be one of:
+
+- `process`
+- `hyperv`
+- `default`: This mode will choose the recommended mode as described by Microsoft. Server versions
+  will use `process`, while desktop versions will use `hyperv`.
+
+_**required:** `false`_ _**default:** `"default"`_
+
 ## Complete example
 
 A complete workflow that tests all modes separately could look like this:
@@ -443,16 +473,16 @@ jobs:
           - editmode
           - standalone
     steps:
-      - uses: actions/checkout@v2
+      - uses: actions/checkout@v4
         with:
           lfs: true
-      - uses: actions/cache@v2
+      - uses: actions/cache@v3
         with:
           path: ${{ matrix.projectPath }}/Library
           key: Library-${{ matrix.projectPath }}
           restore-keys: |
             Library-
-      - uses: game-ci/unity-test-runner@v3
+      - uses: game-ci/unity-test-runner@v4
         id: tests
         env:
           UNITY_LICENSE: ${{ secrets.UNITY_LICENSE }}
@@ -463,12 +493,12 @@ jobs:
           githubToken: ${{ secrets.GITHUB_TOKEN }}
           checkName: ${{ matrix.testMode }} Test Results
           coverageOptions: 'generateAdditionalMetrics;generateHtmlReport;generateBadgeReport;assemblyFilters:+my.assembly.*'
-      - uses: actions/upload-artifact@v2
+      - uses: actions/upload-artifact@v3
         if: always()
         with:
           name: Test results for ${{ matrix.testMode }}
           path: ${{ steps.tests.outputs.artifactsPath }}
-      - uses: actions/upload-artifact@v2
+      - uses: actions/upload-artifact@v3
         if: always()
         with:
           name: Coverage results for ${{ matrix.testMode }}
@@ -499,10 +529,10 @@ jobs:
           - playmode
           - editmode
     steps:
-      - uses: actions/checkout@v2
+      - uses: actions/checkout@v4
         with:
           lfs: true
-      - uses: game-ci/unity-test-runner@v3
+      - uses: game-ci/unity-test-runner@v4
         id: tests
         env:
           UNITY_LICENSE: ${{ secrets.UNITY_LICENSE }}
@@ -515,12 +545,12 @@ jobs:
           githubToken: ${{ secrets.GITHUB_TOKEN }}
           checkName: ${{ matrix.testMode }} Test Results
           coverageOptions: 'generateAdditionalMetrics;generateHtmlReport;generateBadgeReport;assemblyFilters:+my.assembly.*'
-      - uses: actions/upload-artifact@v2
+      - uses: actions/upload-artifact@v3
         if: always()
         with:
           name: Test results for ${{ matrix.testMode }}
           path: ${{ steps.tests.outputs.artifactsPath }}
-      - uses: actions/upload-artifact@v2
+      - uses: actions/upload-artifact@v3
         if: always()
         with:
           name: Coverage results for ${{ matrix.testMode }}
diff --git a/docs/03-github/04-builder.mdx b/docs/03-github/04-builder.mdx
index 82468b79..eda9f56d 100644
--- a/docs/03-github/04-builder.mdx
+++ b/docs/03-github/04-builder.mdx
@@ -40,7 +40,7 @@ secret.
 Then, define the build step as follows:
 
 ```yaml
-- uses: game-ci/unity-builder@v3
+- uses: game-ci/unity-builder@v4
   env:
     UNITY_LICENSE: ${{ secrets.UNITY_LICENSE }}
     UNITY_EMAIL: ${{ secrets.UNITY_EMAIL }}
@@ -60,7 +60,7 @@ Make sure you have set up these variables in the activation step:
 Then, define the build step as follows:
 
 ```yaml
-- uses: game-ci/unity-builder@v3
+- uses: game-ci/unity-builder@v4
   env:
     UNITY_EMAIL: ${{ secrets.UNITY_EMAIL }}
     UNITY_PASSWORD: ${{ secrets.UNITY_PASSWORD }}
@@ -77,7 +77,7 @@ If you host your own Unity license server internally you can provide its url usi
 Example of use:
 
 ```yaml
-- uses: game-ci/unity-builder@v3
+- uses: game-ci/unity-builder@v4
   with:
     targetPlatform: WebGL
     unityLicensingServer: [url to your license server]
@@ -99,7 +99,7 @@ By default, Builder outputs it's builds to a folder named `build`.
 Example:
 
 ```yaml
-- uses: actions/upload-artifact@v2
+- uses: actions/upload-artifact@v3
   with:
     name: Build
     path: build
@@ -116,7 +116,7 @@ before any unity steps.
 Example:
 
 ```yaml
-- uses: actions/cache@v2
+- uses: actions/cache@v3
   with:
     path: path/to/your/project/Library
     key: Library-MyProjectName-TargetPlatform
@@ -152,7 +152,7 @@ _**required:** `false`_ _**default:** `auto`_
 Specific docker image that should be used for building the project.
 
 ```yaml
-- uses: game-ci/unity-builder@v3
+- uses: game-ci/unity-builder@v4
   with:
     customImage: 'unityci/editor:2020.1.14f1-base-0'
 ```
@@ -192,7 +192,7 @@ There are two conditions for a custom buildMethod:
 Example:
 
 ```yaml
-- uses: game-ci/unity-builder@v3
+- uses: game-ci/unity-builder@v4
   with:
     buildMethod: EditorNamespace.BuilderClassName.StaticBuildMethod
 ```
@@ -202,7 +202,7 @@ To get started with a modified version of the default Unity Builder build script
 `Assets/Editor/UnityBuilderAction` directory and reference it:
 
 ```yaml
-- uses: game-ci/unity-builder@v3
+- uses: game-ci/unity-builder@v4
   with:
     buildMethod: UnityBuilderAction.BuildScript.Build
 ```
@@ -220,7 +220,7 @@ Parameters must start with a hyphen (`-`) and may be followed by a value (withou
 Parameters without a value will be considered booleans (with a value of true).
 
 ```yaml
-- uses: game-ci/unity-builder@v3
+- uses: game-ci/unity-builder@v4
   with:
     customParameters: -profile SomeProfile -someBoolean -someValue exampleValue
 ```
@@ -240,7 +240,7 @@ _**required:** `false`_ _**default:** `""`_
 Configure a specific versioning strategy
 
 ```yaml
-- uses: game-ci/unity-builder@v3
+- uses: game-ci/unity-builder@v4
   with:
     versioning: Semantic
 ```
@@ -300,7 +300,7 @@ Set this flag to `androidPackage` to build an apk, `androidAppBundle` for an aab
 `androidStudioProject` to build an Android Studio Project.
 
 ```yaml
-- uses: game-ci/unity-builder@v3
+- uses: game-ci/unity-builder@v4
   with:
     androidExportType: 'androidAppBundle'
     androidKeystoreName: user.keystore
@@ -410,7 +410,7 @@ _**required:** `false`_ _**default:** `""`_
 Allows the branch of the build to be dirty, and still generate the build.
 
 ```yaml
-- uses: game-ci/unity-builder@v3
+- uses: game-ci/unity-builder@v4
   with:
     allowDirtyBuild: true
 ```
@@ -454,6 +454,56 @@ to avoid any conflicts.
 
 _**required:** `false`_ _**default:** `"/github/workspace"`_
 
+#### dockerCpuLimit
+
+Number of CPU cores to assign to the Docker container. Defaults to all available cores when no value
+is specified. Can accept fractional values, e.g., 0.5 for half of a CPU core's execution time.
+
+_**required:** `false`_ _**default:** `""`_
+
+#### dockerMemoryLimit
+
+Amount of memory to assign to the Docker container. Defaults to 95% of total system memory rounded
+down to the nearest megabyte on Linux and 80% on Windows. If the platform is unrecognized, it
+defaults to 75% of total system memory. To manually specify a value, use the format
+\<number\>\<unit\>. The units can be:
+
+- `m`: Megabytes (e.g., 512m = 512 megabytes)
+- `g`: Gigabytes (e.g., 4g = 4 gigabytes)
+
+_**required:** `false`_ _**default:** `""`_
+
+#### dockerIsolationMode
+
+Isolation mode to use for the Docker container when running on Windows. Can be one of:
+
+- `process`
+- `hyperv`
+- `default`: This mode will choose the recommended mode as described by Microsoft. Server versions
+  will use `process`, while desktop versions will use `hyperv`.
+
+_**required:** `false`_ _**default:** `"default"`_
+
+#### containerRegistryRepository
+
+Container registry and repository to pull the image from. Only applicable if `customImage` is not
+set.
+
+This allows you to host your own images and still leverage the logic to automatically determine the
+editor version and target platform. Accepts images from other registries too, for example
+`ghcr.io/namespace/imagename` for Github Container Registry.
+
+_**required:** `false`_ _**default:** `"unityci/editor"`_
+
+#### containerRegsitryImageVersion
+
+Container registry image version. Only applicable if `customImage` is not set.
+
+This allows you to roll back the image version to a previous version if needed or even use your own
+version numbering for custom built and maintained registries.
+
+_**required:** `false`_ _**default:** `"3"`_
+
 ## Outputs
 
 Below are outputs that can be accessed by using `${{ steps.myBuildStep.outputs.outputName }}`, where
@@ -465,7 +515,7 @@ Returns the version that was generated by Builder, following the strategy config
 `versioning`.
 
 ```yaml
-- uses: game-ci/unity-builder@v3
+- uses: game-ci/unity-builder@v4
   id: myBuildStep
 - run: echo 'Project Version: ${{ steps.myBuildStep.outputs.buildVersion }}'
 ```
@@ -475,7 +525,7 @@ Returns the version that was generated by Builder, following the strategy config
 Returns the version code that was generated by Builder for Android builds.
 
 ```yaml
-- uses: game-ci/unity-builder@v3
+- uses: game-ci/unity-builder@v4
   id: myBuildStep
 - run: echo 'Android Version Code: ${{ steps.myBuildStep.outputs.androidVersionCode }}'
 ```
@@ -510,11 +560,11 @@ run: |
 name: Accessing private repos
 runs-on: ubuntu-latest
 steps:
-  - uses: actions/checkout@v2
+  - uses: actions/checkout@v4
   - uses: webfactory/ssh-agent@v0.8.0
     with:
       ssh-private-key: ${{ secrets.SSH_PRIVATE_KEY }}
-  - uses: game-ci/unity-builder@v3
+  - uses: game-ci/unity-builder@v4
     with:
       sshAgent: ${{ env.SSH_AUTH_SOCK }}
 ```
@@ -554,7 +604,7 @@ using `sshPublicKeysDirectoryPath` and setting the `GIT_CONFIG_EXTENSIONS` envir
     } >> "$GITHUB_ENV"
   shell: bash
 
-- uses: game-ci/unity-builder@v3
+- uses: game-ci/unity-builder@v4
   with:
     sshAgent: ${{ env.SSH_AUTH_SOCK }}
     sshPublicKeysDirectoryPath: ${{ env.HOME }}/.ssh_docker
@@ -565,7 +615,7 @@ using `sshPublicKeysDirectoryPath` and setting the `GIT_CONFIG_EXTENSIONS` envir
 Unity requires an .upmconfig.toml to exist in the home directory to authenticate and download
 packages from private UPM registries. To create this file, first create the
 `/home/runner/work/_temp/_github_home` directory, and then create the .upmconfig.toml file inside
-that directory. This action must be done before running the game-ci/unity-builder@v2 action.
+that directory. This action must be done before running the game-ci/unity-builder@v4 action.
 
 ```yaml
 - name: Create .upmconfig.toml UPM authentication file
@@ -602,7 +652,7 @@ jobs:
           - Android # Build an Android .apk standalone app.
           - WebGL # WebGL.
     steps:
-      - uses: actions/checkout@v3
+      - uses: actions/checkout@v4
         with:
           fetch-depth: 0
           lfs: true
@@ -612,8 +662,8 @@ jobs:
           key: Library-${{ matrix.targetPlatform }}
           restore-keys: Library-
       - if: matrix.targetPlatform == 'Android'
-        uses: jlumbroso/free-disk-space@v1.3.0
-      - uses: game-ci/unity-builder@v3
+        uses: jlumbroso/free-disk-space@v1.3.1
+      - uses: game-ci/unity-builder@v4
         env:
           UNITY_LICENSE: ${{ secrets.UNITY_LICENSE }}
         with:
diff --git a/docs/03-github/06-deployment/android.mdx b/docs/03-github/06-deployment/android.mdx
index 88297d77..f9f1efcb 100644
--- a/docs/03-github/06-deployment/android.mdx
+++ b/docs/03-github/06-deployment/android.mdx
@@ -166,13 +166,13 @@ jobs:
     name: Build For Android Platform
     runs-on: ubuntu-latest
     steps:
-      - uses: jlumbroso/free-disk-space@v1.2.0
-      - uses: actions/checkout@v3
+      - uses: jlumbroso/free-disk-space@v1.3.1
+      - uses: actions/checkout@v4
       - uses: actions/cache@v3
         with:
           path: Library
           key: Library-Android
-      - uses: game-ci/unity-builder@v3
+      - uses: game-ci/unity-builder@v4
         with:
           targetPlatform: Android
           androidExportType: androidAppBundle
@@ -181,7 +181,7 @@ jobs:
           androidKeystorePass: ${{ secrets.ANDROID_KEYSTORE_PASS }}
           androidKeyaliasName: ${{ secrets.ANDROID_KEYALIAS_NAME }}
           androidKeyaliasPass: ${{ secrets.ANDROID_KEYALIAS_PASS }}
-          androidTargetSdkVersion: AndroidApiLevel31
+          androidTargetSdkVersion: AndroidApiLevel33
       - uses: actions/upload-artifact@v3
         with:
           name: build-Android
@@ -199,9 +199,9 @@ jobs:
       ANDROID_PACKAGE_NAME: ${{ secrets.ANDROID_PACKAGE_NAME }}
     steps:
       - name: Checkout Repository
-        uses: actions/checkout@v3
+        uses: actions/checkout@v4
       - name: Download Android Artifact
-        uses: actions/download-artifact@v2
+        uses: actions/download-artifact@v3
         with:
           name: build-Android
           path: build/Android
@@ -210,15 +210,15 @@ jobs:
       - name: Set up Fastlane
         uses: ruby/setup-ruby@v1
         with:
-          ruby-version: 2.7.2
+          ruby-version: 3.2
           bundler-cache: true
       - name: Upload to Google Play Internal
-        uses: maierj/fastlane-action@v2.0.1
+        uses: maierj/fastlane-action@v3.0.0
         with:
           lane: 'android internal' # Change to upload to a different lane
       - name: Cleanup to avoid storage limit
         if: always()
-        uses: geekyeggo/delete-artifact@v1
+        uses: geekyeggo/delete-artifact@v2
         with:
           name: build-Android
 ```
diff --git a/docs/03-github/06-deployment/ios.mdx b/docs/03-github/06-deployment/ios.mdx
index b791026a..a1c1ddc2 100644
--- a/docs/03-github/06-deployment/ios.mdx
+++ b/docs/03-github/06-deployment/ios.mdx
@@ -185,10 +185,10 @@ jobs:
   setup:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v2
+      - uses: actions/checkout@v4
       - uses: ruby/setup-ruby@v1
         with:
-          ruby-version: 2.6
+          ruby-version: 3.2
           bundler-cache: true
 
       - name: Build iOS
@@ -219,10 +219,10 @@ jobs:
   generate_certs:
     runs-on: macos-latest
     steps:
-      - uses: actions/checkout@v2
+      - uses: actions/checkout@v4
       - uses: ruby/setup-ruby@v1
         with:
-          ruby-version: 2.6
+          ruby-version: 3.2
           bundler-cache: true
 
       - name: Build iOS
@@ -429,18 +429,18 @@ jobs:
     name: Build for iOS
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v2
+      - uses: actions/checkout@v4
 
-      - uses: actions/cache@v2
+      - uses: actions/cache@v3
         with:
           path: Library
           key: Library-iOS
 
-      - uses: game-ci/unity-builder@v3
+      - uses: game-ci/unity-builder@v4
         with:
           targetPlatform: iOS
 
-      - uses: actions/upload-artifact@v2
+      - uses: actions/upload-artifact@v3
         with:
           name: build-iOS
           path: build/iOS
@@ -451,10 +451,10 @@ jobs:
     needs: buildForiOSPlatform
     steps:
       - name: Checkout Repository
-        uses: actions/checkout@v2
+        uses: actions/checkout@v4
 
       - name: Download iOS Artifact
-        uses: actions/download-artifact@v2
+        uses: actions/download-artifact@v3
         with:
           name: build-iOS
           path: build/iOS
@@ -485,7 +485,7 @@ jobs:
 
       - name: Cleanup to avoid storage limit
         if: always()
-        uses: geekyeggo/delete-artifact@v1
+        uses: geekyeggo/delete-artifact@v2
         with:
           name: build-iOS
 ```
diff --git a/docs/03-github/06-deployment/steam.mdx b/docs/03-github/06-deployment/steam.mdx
index a5a95049..7e82cb07 100644
--- a/docs/03-github/06-deployment/steam.mdx
+++ b/docs/03-github/06-deployment/steam.mdx
@@ -27,7 +27,7 @@ jobs:
     outputs:
       buildVersion: ${{ steps.build.outputs.buildVersion }}
     steps:
-      - uses: actions/checkout@v3
+      - uses: actions/checkout@v4
         with:
           fetch-depth: 0
           lfs: true
@@ -40,7 +40,7 @@ jobs:
           restore-keys: |
             Library-${{ matrix.targetPlatform }}-
             Library-
-      - uses: game-ci/unity-builder@v3
+      - uses: game-ci/unity-builder@v4
         id: build
         env:
           UNITY_LICENSE: ${{ secrets.UNITY_LICENSE }}
@@ -56,7 +56,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - name: Checkout Repository
-        uses: actions/checkout@v3
+        uses: actions/checkout@v4
         with:
           fetch-depth: 0
       - name: Download StandaloneWindows64 Artifact
diff --git a/docs/05-gitlab/02-activation.mdx b/docs/05-gitlab/02-activation.mdx
index 4ed4521f..70a2a9d6 100644
--- a/docs/05-gitlab/02-activation.mdx
+++ b/docs/05-gitlab/02-activation.mdx
@@ -77,9 +77,9 @@ All you need is [docker](https://www.docker.com/) installed on your machine.
    address_ for `UNITY_USERNAME` env var.
 
    ```bash
-   UNITY_VERSION=2020.1.11f1
+   UNITY_VERSION=2022.3.12f1
    IMAGE=unityci/editor # https://hub.docker.com/r/unityci/editor
-   IMAGE_VERSION=0.12 # https://github.com/game-ci/docker/releases
+   IMAGE_VERSION=3 # https://github.com/game-ci/docker/releases
    DOCKER_IMAGE=$IMAGE:$UNITY_VERSION-base-$IMAGE_VERSION
 
    docker run -it --rm \
@@ -150,9 +150,9 @@ All you need is [docker](https://www.docker.com/) installed on your machine.
    address_ for `UNITY_USERNAME` env var.
 
    ```bash
-   UNITY_VERSION=2020.1.11f1
+   UNITY_VERSION=2022.3.12f1
    IMAGE=unityci/editor # https://hub.docker.com/r/unityci/editor
-   IMAGE_VERSION=0.12 # https://github.com/game-ci/docker/releases
+   IMAGE_VERSION=3 # https://github.com/game-ci/docker/releases
    DOCKER_IMAGE=$IMAGE:$UNITY_VERSION-base-$IMAGE_VERSION
 
    docker run -it --rm \
diff --git a/docs/08-docker/02-windows-docker-images.mdx b/docs/08-docker/02-windows-docker-images.mdx
index c101f674..a6f52875 100644
--- a/docs/08-docker/02-windows-docker-images.mdx
+++ b/docs/08-docker/02-windows-docker-images.mdx
@@ -104,7 +104,7 @@ volumes = [
 
 ```dockerfile
 ARG UNITY_VERSION=''
-ARG UNITY_IMAGE_VERSION='1'
+ARG UNITY_IMAGE_VERSION='3'
 
 FROM unityci/editor:windows-${UNITY_VERSION}-windows-il2cpp-${UNITY_IMAGE_VERSION}
 
@@ -143,7 +143,7 @@ try {
 unity-windows-il2cpp-build:
   variables:
     UPM_CACHE_ROOT: $CI_PROJECT_DIR/.upm
-    UNITY_IMAGE_VERSION: "1"
+    UNITY_IMAGE_VERSION: "3"
     UNITY_MODULE: "il2cpp"
     UNITY_IMAGE_PREFIX: "unityci/editor"
     # Do not use quotes around this argument
@@ -243,7 +243,7 @@ _Option 2: Install PowerShell Core_
 
 ```dockerfile
 ARG UNITY_VERSION=''
-ARG UNITY_IMAGE_VERSION='1'
+ARG UNITY_IMAGE_VERSION='3'
 
 FROM unityci/editor:windows-${UNITY_VERSION}-windows-il2cpp-${UNITY_IMAGE_VERSION}
 
diff --git a/docs/09-troubleshooting/common-issues.mdx b/docs/09-troubleshooting/common-issues.mdx
index b50b0613..b89d8c1e 100644
--- a/docs/09-troubleshooting/common-issues.mdx
+++ b/docs/09-troubleshooting/common-issues.mdx
@@ -118,12 +118,12 @@ To know which docker images are available, you can visit the list of [all suppor
 here][unity-docker-versions].
 
 In this particular case, it is also important to look for the last part of the docker image which is
-the version for GameCI. `-0` means it is the latest `v0.x.x` version of the docker images. `v0.x.x`
-and `v1.x.x` are out of date as we moved to Version 2 as shown on
+the version for GameCI. `-0` means it is the latest `v0.x.x` version of the docker images. `v0.x.x`,
+`v1.x.x`, and `v2.x.x` are out of date as we moved to Version 3 as shown on
 [github.com/game-ci/docker/releases](https://github.com/game-ci/docker/releases). We are not
-publishing images for `v0.x.x` or `v1.x.x` anymore.
+publishing images for `v0.x.x`, `v1.x.x`, `v2.x.x` anymore.
 
-The correct image should be `unityci/editor:2021.3.0f1-android-2`.
+The correct image should be `unityci/editor:2021.3.0f1-android-3`.
 
 You can also test this locally:
 
@@ -133,24 +133,24 @@ docker pull unityci/editor:2021.3.0f1-android-0
 # Error response from daemon: manifest for unityci/editor:2021.3.0f1-android-0 not found: manifest unknown: manifest unknown
 
 # right
-docker pull unityci/editor:2021.3.0f1-android-2
-# 2021.3.0f1-android-2: Pulling from unityci/editor
+docker pull unityci/editor:2021.3.0f1-android-3
+# 2021.3.0f1-android-3: Pulling from unityci/editor
 # [...]
 ```
 
 #### Github Actions
 
-You need to make sure you are using Github Actions v3, check for the version of your actions in your
+You need to make sure you are using Github Actions v4, check for the version of your actions in your
 `.github/workflows/*.yml` files.
 
 ```diff
-- uses: game-ci/unity-builder@v2
-+ uses: game-ci/unity-builder@v3
+- uses: game-ci/unity-builder@v3
++ uses: game-ci/unity-builder@v4
 ```
 
 #### Gitlab CI
 
-Set the `IMAGE_VERSION` to 2 in
+Set the `IMAGE_VERSION` to 3 in
 [`.gitlab-ci.yml`](https://gitlab.com/game-ci/unity3d-gitlab-ci-example/-/blob/main/.gitlab-ci.yml#L12)
 
 ### Scripts have compiler errors.
diff --git a/docusaurus.config.js b/docusaurus.config.js
index 9311baf4..dc5e720b 100644
--- a/docusaurus.config.js
+++ b/docusaurus.config.js
@@ -49,7 +49,10 @@ const config = {
           lastVersion: 'current',
           versions: {
             current: {
-              label: 'v3 (current)',
+              label: 'v4 (current)',
+            },
+            3: {
+              label: 'v3',
             },
             2: {
               label: 'v2',
diff --git a/versioned_docs/version-3/02-getting-started/index.mdx b/versioned_docs/version-3/02-getting-started/index.mdx
new file mode 100644
index 00000000..ac28d8af
--- /dev/null
+++ b/versioned_docs/version-3/02-getting-started/index.mdx
@@ -0,0 +1,39 @@
+# Getting started
+
+The term for automatically testing, building, and deploying your project is Continuous Integration,
+or CI for short.
+
+The configuration for CI, we commonly call a CI-workflow.
+
+To get started creating your workflow, you need 3 things:
+
+- A Unity project
+- A Git host (GitHub, GitLab, your private server, etc.)
+- A CI system (GitHub Actions, GitLab pipelines, CircleCI, TravisCI, Jenkins, etc.)
+
+## Preparing the project
+
+**Create a repository** on your chosen Git host and follow their instructions to commit and push
+your project.
+
+Be sure to **ignore any automatically generated files**, by adding the reference
+[.gitignore](https://github.com/github/gitignore/blob/master/Unity.gitignore) file to the root of
+your project. Please note that you may have to extend this file to ignore the temporary files
+created by the runners, as the creation of these temporary files may cause a runners' local branch
+to become dirty (more info [here](/docs/troubleshooting/common-issues#branch-is-dirty])):
+
+Two common temporary folders that are created by GameCI are `artifacts` and `CodeCoverage`. You can
+ignore them by adding the following lines to your `.gitignore`:
+
+```
+# Ignore temporaries from GameCI
+/[Aa]rtifacts/
+/[Cc]odeCoverage/
+```
+
+To **ensure large files are handled correctly** (in [LFS](https://git-lfs.github.com/)), you can add
+our reference
+[.gitattributes](https://gist.github.com/webbertakken/ff250a0d5e59a8aae961c2e509c07fbc) file to the
+root of your project.
+
+You are now **ready** to create a workflow! Choose the CI system you chose in the menu on the left.
diff --git a/versioned_docs/version-3/03-github-cloud-runner/01-introduction.mdx b/versioned_docs/version-3/03-github-cloud-runner/01-introduction.mdx
new file mode 100644
index 00000000..d67936b5
--- /dev/null
+++ b/versioned_docs/version-3/03-github-cloud-runner/01-introduction.mdx
@@ -0,0 +1,104 @@
+# Introduction
+
+## Concept - What Does Cloud Runner Do
+
+**Cloud Runner enables you to run, build and test (Unity) projects in the cloud. You can start jobs
+from the command line, the "Workbench" GUI in the Unity Editor or from GitHub Actions.**
+
+**Cloud Runner will automatically provision an environment at a Cloud Provider such as GCP and AWS.
+It will then send the project to be built and/or tested depending on your workflow configuration.**
+
+**Cloud Runner is especially useful for game development because it supports large projects. Cloud
+Runner provides first class support for the Unity game engine.**
+
+Cloud Runner uses git to track and syncronize your projects and uses native cloud services such as
+AWS Fargate and Kubernetes to run your jobs. Other version control systems are not actively
+supported.
+
+## Why Cloud Runner?
+
+1. **Cloud runner is flexible and elastic**
+   1. _You can balance your use of high-performance and cost saving modes._ Configurable cost/speed
+      effeciency
+   2. _Works great for projects of almost any size, from AAA projects and assets to micro projects_
+   3. _Extended configuration options._ More control over disk size, memory and CPU
+   4. _Easily scale all job resources as your project grows_ e.g storage, CPU and memory
+2. **Scale fully on demand from zero (not in use) to many concurrent jobs.** Benefits from
+   "pay-for-what-you-use" cloud billing models. We have made an effort to make sure that it costs
+   you nothing (aside from artifact and cache storage) while there are no builds running (no
+   guarantees)
+3. **Easy setup and configuration**
+4. **Run custom jobs** and extend the system for any workload
+
+## Why not cloud runner?
+
+1. Your project is small in size. Below 5GB Cloud Runner should not be needed.
+2. You already have dedicated servers running you can use.
+
+Although the speed of a CI pipelines is an important metric to consider, there are real challenges
+for game development pipelines.
+
+This solution prefers convenience, ease of use, scalability, throughput and flexibility.
+
+Faster solutions exist, but would all involve self-hosted hardware with an immediate local cache of
+the large project files and working directory and a dedicated server.
+
+# Cloud Runner Release Status
+
+Cloud Runner is in "active development" ⚠️🔨
+
+Cloud Runner overall release status: `preview` This means some APIs may change, features are still
+being added but the minimum feature set works and is stable.
+
+Release Stages: `experimental` ➡️ `preview` ➡️ `full release`
+
+You must use a provider with Cloud Runner, each provider's release status is described below. This
+indicates the stability and support for cloud runner features and workflows.
+
+### Supported Cloud Runner Platforms
+
+```md
+| Cloud Provider Platform | Release Status     |
+| ----------------------- | ------------------ |
+| Kubernetes              | ✔️ preview release |
+| AWS                     | ✔️ full release    |
+| GCP                     | ⚠ Considered       |
+| Azure                   | ⚠ Considered       |
+```
+
+_Note for Kubernetes support:_ _Usually the cluster needs to be up and running at all times, as
+starting up a cluster is slow._ _Use Google Cloud's Kubernetes Autopilot you can scale down to the
+free tier automatically while not in use._ _Kubernetes support currently requires cloud storage,
+only S3 support is built-in._
+
+```md
+| Git Platform          | Release Status     |
+| --------------------- | ------------------ |
+| GitHub                | ✔️ full release    |
+| GitLab                | ✔️ preview release |
+| Command Line          | ✔️ preview release |
+| Any Git repository    | ✔️ preview release |
+| Any Git automation/Ci | ✔️ preview release |
+```
+
+## External Links
+
+### Cloud Runner Releases
+
+[Game CI Releases - GitHub](https://github.com/game-ci/unity-builder/releases) _Packaged and
+released with game-ci's unity-builder module._
+
+### Open Incoming Pull Requests
+
+[Cloud Runner PRs - GitHub](https://github.com/game-ci/unity-builder/pulls?q=is%3Apr+cloud+runner)
+
+### 💬Suggestions and 🐛Bugs (GitHub Issues):
+
+[Game CI Issues - GitHub](https://github.com/game-ci/unity-builder/labels/cloud-runner)
+
+### Community
+
+**Share your feedback with us!**
+
+- [**Discord Channel**](https://discord.com/channels/710946343828455455/789631903157583923)
+- [**Feedback Form**](https://forms.gle/3Wg1gGf9FnZ72RiJ9)
diff --git a/versioned_docs/version-3/03-github-cloud-runner/02-game-ci-vs-cloud-runner.mdx b/versioned_docs/version-3/03-github-cloud-runner/02-game-ci-vs-cloud-runner.mdx
new file mode 100644
index 00000000..1ba9ae94
--- /dev/null
+++ b/versioned_docs/version-3/03-github-cloud-runner/02-game-ci-vs-cloud-runner.mdx
@@ -0,0 +1,42 @@
+# Game-CI vs Cloud Runner
+
+# Standard Game-CI (Use Cases)
+
+The Game CI core is a maintained set of docker images that can be used to run workloads in many
+scenarios.
+
+Game CI also provides specific GitHub actions for running workflows on GitHub. And a similar
+workflow for running Game CI on GitLab and Circle CI. _All of these options use the build server
+resources provided by those systems, this can be a constraint or very convenient depending on the
+size of your project and the workloads you need to run._
+
+# Cloud Runner (Use Cases)
+
+## Sending Builds to the cloud
+
+You may want to take advantage of cloud resources for lots of reasons (scale, speed, cost,
+flexibility) or may want to start remote builds from the command line without slowing down your
+development machine. Cloud Runner can help you do this.
+
+This may be a preference, more effecient or you may want to use systems that struggle to handle
+large game development projects (GitHub being a good example).
+
+### Large GitHub Projects
+
+GitHub Actions by default run on
+[build machines provided by GitHub](https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners).
+For Unity projects the available disk size is quite small. You may experience an error related to
+running out of disk space. You may also want to run the build on a server with more memory or
+processing resources.
+
+### GitHub Self-Hosted Runners vs Game CI Cloud Runner
+
+_GitHub users can consider:
+[GitHub self-hosted runners](https://docs.github.com/en/actions/hosting-your-own-runners/about-self-hosted-runners)
+and Cloud Runner. Both can enable you to build larger projects._
+
+_Cloud Runner is better if you don't have a server setup or don't want to manage or maintain your
+own build server._
+
+_Self-hosted runners are best used when you already have a server available, running 24/7 that you
+can setup as a runner. And you're happy to maintain and keep that server available and running._
diff --git a/versioned_docs/version-3/03-github-cloud-runner/02-getting-started.mdx b/versioned_docs/version-3/03-github-cloud-runner/02-getting-started.mdx
new file mode 100644
index 00000000..7e12cfdf
--- /dev/null
+++ b/versioned_docs/version-3/03-github-cloud-runner/02-getting-started.mdx
@@ -0,0 +1,3 @@
+# Getting Started
+
+To get quickly started checkout one of our examples:
diff --git a/versioned_docs/version-3/03-github-cloud-runner/03-examples/01-command-line.mdx b/versioned_docs/version-3/03-github-cloud-runner/03-examples/01-command-line.mdx
new file mode 100644
index 00000000..5c315d0f
--- /dev/null
+++ b/versioned_docs/version-3/03-github-cloud-runner/03-examples/01-command-line.mdx
@@ -0,0 +1,49 @@
+# Command Line
+
+_Preview Support Only_
+
+You can install Game CI locally and start cloud runner jobs from the command line or by integrating
+your own tools. All parameters in [API Reference](../api-reference) can be specified as command line
+input fields.
+
+# Install
+
+Currently (development)
+
+```bash
+git clone https://github.com/game-ci/unity-builder.git
+yarn install
+yarn run cli -m {mode parameter} --projectPath {Your project path} {... other command line parameters}
+```
+
+# Planned (does not work currently)
+
+We plan to offer support for Game CI via Deno. This will enable fast, typescript native runtime and
+you will be able to access this via the following:
+
+```bash
+dpx game-ci build
+```
+
+# Help
+
+_You can run `yarn run cli -h` or `yarn run cli --help` to list all modes and paramters with
+descriptions_
+
+# Main Command Parameters
+
+- Default: `cli` (runs a standard build workflow)
+- See API Reference "Modes"
+
+# Keeping command line parameters short
+
+You can avoid specifying long command line input for credentials by using environment variables or
+[the input override feature](../advanced-topics/configuration-override#example) to shorten commands
+signficantly.
+
+This enables you to provide a command to pull input, e.g you can pull from a file or from a secret
+manager.
+
+```bash
+yarn run cli --populateOverride true --pullInputList UNITY_EMAIL,UNITY_SERIAL,UNITY_PASSWORD --inputPullCommand="gcloud secrets versions access 1 --secret=\"{0}\""
+```
diff --git a/versioned_docs/version-3/03-github-cloud-runner/03-examples/02-github-examples/02-aws.mdx b/versioned_docs/version-3/03-github-cloud-runner/03-examples/02-github-examples/02-aws.mdx
new file mode 100644
index 00000000..2317f92f
--- /dev/null
+++ b/versioned_docs/version-3/03-github-cloud-runner/03-examples/02-github-examples/02-aws.mdx
@@ -0,0 +1,71 @@
+# AWS
+
+## Requirements
+
+- You must have an AWS account setup and ready to create resources.
+- Create a service account and generate an AWS access key and key id.
+
+## AWS Credentials
+
+Setup the following as `env` variables for cloud runner to use:
+
+- `AWS_ACCESS_KEY_ID`
+- `AWS_SECRET_ACCESS_KEY`
+- `AWS_DEFAULT_REGION` (should be the same AWS region as the base stack e.g `eu-west-2`)
+
+If you're using GitHub you can use a GitHub Action:
+
+```yaml
+- name: Configure AWS Credentials
+  uses: aws-actions/configure-aws-credentials@v1
+  with:
+    aws-access-key-id: ${{ secrets.AWS_ACCESS_KEY_ID }}
+    aws-secret-access-key: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
+    aws-region: eu-west-2
+```
+
+_Note:_ _This enables Cloud Runner access AWS._
+
+## Configuration For AWS Cloud Runner Jobs
+
+Refer to [Configuration page](../../api-reference) or the [example below](#example).
+
+### Allowed CPU/Memory Combinations
+
+There are some limitations to the CPU and Memory parameters. AWS will only accept the following
+combinations:
+[AWS Fargate Documentation, Allowed CPU and memory values (Task Definitions)](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_definition_parameters.html#task_size)
+
+#### Summary Of Format
+
+- Values are represented as 1024:1 GB or CPU.
+- Do not include the vCPU or GB suffix.
+- 1 CPU can go to a max of 6 GB of memory. 2 CPU's are required to go higher.
+
+#### Valid CPU and Memory Values
+
+```yaml
+- cloudRunnerMemory: 4096
+- cloudRunnerCpu: 1024
+```
+
+## Example
+
+```yaml
+- uses: game-ci/unity-builder@cloud-runner-develop
+  id: aws-fargate-unity-build
+  with:
+    providerStrategy: aws
+    versioning: None
+    projectPath: `your path here`
+    unityVersion: `unity version here`
+    targetPlatform: ${{ matrix.targetPlatform }}
+    gitPrivateToken: ${{ secrets.GITHUB_TOKEN }}
+    # You may want to export your builds somewhere external so you can access it:
+    containerHookFiles: aws-s3-upload-build
+```
+
+_[Custom Steps](../../advanced-topics/custom-hooks/container-hooks)_
+
+A full workflow example can be seen in builder's
+[Cloud Runner GitHub sourcecode for GitHub Pipeline](https://github.com/game-ci/unity-builder/blob/309d668d637ae3e7ffe90d61612968db92e1e376/.github/workflows/cloud-runner-pipeline.yml#L109).
diff --git a/versioned_docs/version-3/03-github-cloud-runner/03-examples/02-github-examples/03-kubernetes.mdx b/versioned_docs/version-3/03-github-cloud-runner/03-examples/02-github-examples/03-kubernetes.mdx
new file mode 100644
index 00000000..f77ee655
--- /dev/null
+++ b/versioned_docs/version-3/03-github-cloud-runner/03-examples/02-github-examples/03-kubernetes.mdx
@@ -0,0 +1,51 @@
+# Kubernetes
+
+## Requirements
+
+- You must have a Kubernetes cluster setup and ready that supports persistent volumes.
+- Create a kubeconfig and encode it as base64.
+
+## K8s Credentials
+
+Setup the following as `env` variables for the GitHub build step:
+
+- `kubeConfig` (should be encoded as base64)
+
+## Configuration For Kubernetes Cloud Runner Jobs
+
+Refer to [Configuration page](../../api-reference) or the [example below](#example).
+
+### Allowed CPU/Memory Combinations
+
+- `0.25 vCPU` - 0.5 GB, 1 GB, 2 GB
+- `0.5 vCPU` - 1 GB, 2 GB, 3 GB, 4 GB
+- `1 vCPU` - 2 GB, 3 GB, 4 GB, 5 GB, 6 GB, 7 GB, 8 GB
+- `2 vCPU` - Between 4 GB and 16 GB in 1-GB increments
+- `4 vCPU` - Between 8 GB and 30 GB in 1-GB increments
+
+#### Summary Of Format
+
+- Values are represented as 1024:1 GB or CPU.
+
+Do not include the vCPU or GB suffix.
+
+### Example
+
+```yaml
+- uses: game-ci/unity-builder@cloud-runner-develop
+  id: k8s-unity-build
+  with:
+    providerStrategy: k8s
+    versioning: None
+    projectPath: `your path here`
+    unityVersion: `unity version here`
+    targetPlatform: ${{ matrix.targetPlatform }}
+    gitPrivateToken: ${{ secrets.GITHUB_TOKEN }}
+    # You may want to export your builds somewhere external so you can access it:
+    containerHookFiles: aws-s3-upload-build
+```
+
+_[Custom Steps](../../advanced-topics/custom-hooks/container-hooks)_
+
+A full workflow example can be seen in builder's
+[Cloud Runner GitHub sourcecode for AWS Pipeline](https://github.com/game-ci/unity-builder/blob/main/.github/workflows/cloud-runner-k8s-pipeline.yml).
diff --git a/versioned_docs/version-3/03-github-cloud-runner/03-examples/02-github-examples/_category_.yaml b/versioned_docs/version-3/03-github-cloud-runner/03-examples/02-github-examples/_category_.yaml
new file mode 100644
index 00000000..b9807118
--- /dev/null
+++ b/versioned_docs/version-3/03-github-cloud-runner/03-examples/02-github-examples/_category_.yaml
@@ -0,0 +1,5 @@
+---
+position: 2.0
+label: GitHub
+collapsible: true
+collapsed: true
diff --git a/versioned_docs/version-3/03-github-cloud-runner/03-examples/_category_.yaml b/versioned_docs/version-3/03-github-cloud-runner/03-examples/_category_.yaml
new file mode 100644
index 00000000..825e328f
--- /dev/null
+++ b/versioned_docs/version-3/03-github-cloud-runner/03-examples/_category_.yaml
@@ -0,0 +1,5 @@
+---
+position: 2.0
+label: Examples
+collapsible: true
+collapsed: true
diff --git a/versioned_docs/version-3/03-github-cloud-runner/04-api-reference.mdx b/versioned_docs/version-3/03-github-cloud-runner/04-api-reference.mdx
new file mode 100644
index 00000000..67a9ee91
--- /dev/null
+++ b/versioned_docs/version-3/03-github-cloud-runner/04-api-reference.mdx
@@ -0,0 +1,221 @@
+# API Reference
+
+## Configuration
+
+_You can specify input parameters via any of the following methods._
+
+- **GitHub Action `with`** _See "Getting Started" examples._
+- **Command Line** _You can specify input parameters via command line._
+- **Environment Variables** _You can specify input parameters via environment variables._
+- **Configuration Override** _[Advanced Topics / Overrides](advanced-topics/configuration-override)_
+
+## Modes
+
+Cloud Runner can accept a parameter to run a specific mode, by default cli-build is run.
+
+```bash
+cli-build
+```
+
+_runs a cloud runner build_
+
+```bash
+list-resources
+```
+
+_lists active resources_
+
+```bash
+list-worfklow
+```
+
+_lists running workflows_
+
+```bash
+watch
+```
+
+_follows logs of a running workflow_
+
+```bash
+garbage-collect
+```
+
+_runs garbage collection_
+
+```bash
+- cache-push
+- cache-pull
+```
+
+Cache commands to push and pull from the local caching directory. Used in cloud runner workflows.
+Uses `cachePullFrom` and `cachePushTo` parameters.
+
+```bash
+- hash (hash folder contents recursively)
+- print-input (prints all input parameters)
+```
+
+Utility commands
+
+```bash
+- remote-cli-pre-build (sets up a repository, usually before a game-ci build)
+- remote-cli-post-build (pushes to LFS and Library cache)
+```
+
+Commands called during cloud runner workflows before/after a build.
+
+## Common Parameters
+
+### Git syncronization parameters
+
+```bash
+gitPrivateToken (should be a GitHub access token with permission to get repositories)
+```
+
+Used to authenticate remote job's access to repository.
+
+```bash
+- GITHUB_REPOSITORY
+- GITHUB_REF || branch || GitSHA
+```
+
+Used to syncronize the repository to the Cloud Runner job. If parameters are not provided, will
+attempt to read them from current directory's git repo (e.g branch, commit SHA, remote URL).
+
+### Cloud Runner parameters
+
+```bash
+providerStrategy
+```
+
+Specifies the Cloud Provider to use for Cloud Runner jobs. Accepted values: `aws`, `k8s`,
+`local-docker`.
+
+```bash
+- containerCpu
+- containerMemory
+```
+
+Specifies the CPU and Memory resources to be used for cloud containers created by Cloud Runner.
+(See: getting started section for more configuration options per provider.)
+
+```bash
+cloudRunnerBranch
+```
+
+Specifies the release branch of Cloud Runner to use for remote containers. Accepted values: `main`
+(default), `cloud-runner-preview` (stable/development), `cloud-runner-develop` (latest/development)
+
+### Custom commands from files parameters
+
+```bash
+- containerHookFiles
+- commandHookFiles
+- commandHooks
+- postBuildContainerHooks
+- preBuildContainerHooks
+```
+
+Specifies the name of custom hook or step files to include in workflow. (Accepted Format: see
+"[container hooks](advanced-topics/custom-hooks/container-hooks)
+[command hooks](advanced-topics/custom-hooks/command-hooks)")
+
+### Custom commands from yaml parameters
+
+```bash
+customJob
+```
+
+Specifies a custom job to override default build workflow. (Accepted Format: see
+"[advanced topics / custom job](advanced-topics/custom-hooks/custom-job)")
+
+### Configuration Override
+
+```bash
+inputPullCommand
+```
+
+Read parameter from command line ouput, such as a secret manager. Must include a `{0}` to inject the
+name of the parameter to pull. (See:
+[Configuration Override](advanced-topics/configuration-override))
+
+```bash
+pullInputList
+```
+
+List of parameters to apply with `inputPullCommand`. (See:
+[Configuration Override](advanced-topics/configuration-override))
+
+### Aws
+
+```bash
+awsStackName
+```
+
+Name of the persistent shared base stack, used to store artifacts and caching.
+
+### K8s
+
+```bash
+- kubeVolume
+- kubeVolumeSize
+- kubeStorageClass
+```
+
+Override name of persistent volume used, size of volume and storage class used.
+
+### Caching
+
+```bash
+cacheKey
+```
+
+Defaults to branch name. Defines the scope for sharing cache entries.
+
+### Utility
+
+```bash
+- cloudRunnerDebug (Debug logging for Cloud Runner)
+- useLargePackages (Any packages in manifest.json containing phrase "LargePackage" will be
+  redirected to a shared folder for all builds sharing a cache key)
+- useSharedBuilder (Use a shared clone of Game-CI, saves some storage space and can be used if
+  you're using one release branch of Cloud Runner)
+- useCompressionStrategy (Use Lz4 compression for cache and build artifacts. Enabled by default)
+```
+
+### Retained Workspace
+
+```bash
+- maxRetainedWorkspaces
+```
+
+See: [Advanced Topics / Retained Workspaces](advanced-topics/retained-workspace), enables caching
+entire project folder.
+
+### Garbage Collection
+
+```bash
+- garbageMaxAge
+```
+
+## Command Line Only Parameters
+
+```bash
+- populateOverride
+- cachePushFrom
+- cachePushTo
+- artifactName
+- select
+```
+
+## Other Environment Variables
+
+```bash
+- USE_IL2CPP (Set to `false`)
+```
+
+# External Links
+
+All accepted parameters given here with a description:
+[https://github.com/game-ci/unity-builder/blob/cloud-runner-develop/action.yml](https://github.com/game-ci/unity-builder/blob/cloud-runner-develop/action.yml)
diff --git a/versioned_docs/version-3/03-github-cloud-runner/06-advanced-topics/01-caching.mdx b/versioned_docs/version-3/03-github-cloud-runner/06-advanced-topics/01-caching.mdx
new file mode 100644
index 00000000..f6fb9645
--- /dev/null
+++ b/versioned_docs/version-3/03-github-cloud-runner/06-advanced-topics/01-caching.mdx
@@ -0,0 +1,32 @@
+# Caching
+
+Cloud Runner supports two main caching modes:
+
+- Standard Caching
+- Retained Workspace
+
+_You can even mix the two by specifying a "MaxRetainedWorkspaces" parameter. Above the max_
+_concurrent jobs a new job will use standard caching._
+
+## Standard Caching
+
+#### Good For
+
+- Minimum storage use
+- Smaller projects
+
+#### What is cached between builds
+
+- LFS files
+- Unity Library folder
+
+## Retained Workspace
+
+#### Good For
+
+- Minimum storage use
+- Smaller projects
+
+#### What is cached between builds
+
+- Entire Project Folder
diff --git a/versioned_docs/version-3/03-github-cloud-runner/06-advanced-topics/02-retained-workspace.mdx b/versioned_docs/version-3/03-github-cloud-runner/06-advanced-topics/02-retained-workspace.mdx
new file mode 100644
index 00000000..0e1bfbcd
--- /dev/null
+++ b/versioned_docs/version-3/03-github-cloud-runner/06-advanced-topics/02-retained-workspace.mdx
@@ -0,0 +1,8 @@
+# Retained Workspaces
+
+Caches the entire project folder. This option provides the best responsiveness, but also can consume
+lots of storage.
+
+Using API: `maxRetainedWorkspaces`. You can specify a maximum number of retained workspaces, only
+one job can use a retained workspace at one time. Each retained workspace consumes more cloud
+storage.
diff --git a/versioned_docs/version-3/03-github-cloud-runner/06-advanced-topics/03-garbage-collection.mdx b/versioned_docs/version-3/03-github-cloud-runner/06-advanced-topics/03-garbage-collection.mdx
new file mode 100644
index 00000000..9f409254
--- /dev/null
+++ b/versioned_docs/version-3/03-github-cloud-runner/06-advanced-topics/03-garbage-collection.mdx
@@ -0,0 +1,17 @@
+# Garbage Collection
+
+Cloud Runner creates, manages and destroys cloud workloads you request. Resources have to be
+created.
+
+It is possible a resource doesn't get deleted by cloud runner.
+
+You can use garbage collection to verify everything has been cleaned up.
+
+Use the **Mode**: `garbage-collect`.
+
+You can use the following API parameters:
+
+- Max Age
+- Max Size
+- Preview Only
+- Filter
diff --git a/versioned_docs/version-3/03-github-cloud-runner/06-advanced-topics/04-configuration-override.mdx b/versioned_docs/version-3/03-github-cloud-runner/06-advanced-topics/04-configuration-override.mdx
new file mode 100644
index 00000000..94134fc1
--- /dev/null
+++ b/versioned_docs/version-3/03-github-cloud-runner/06-advanced-topics/04-configuration-override.mdx
@@ -0,0 +1,19 @@
+# Configuration Override
+
+When running any unity workload you must provide valid unity credentials. In addition to any other
+credentials this is already quite a lot of input. For this reason, it is common to use the command
+line mode with input override (link here). This enables you to provide a command to pull input, with
+this approach you can create a file to store credentials or pull from a secret manager.
+
+## Example
+
+```bash
+game-ci -m cli --populateOverride true --readInputFromOverrideList UNITY_EMAIL,UNITY_SERIAL,UNITY_PASSWORD --readInputOverrideCommand="gcloud secrets versions access 1 --secret=\"{0}\""
+```
+
+## Required Parameters
+
+- `populateOverride` - Must be true to run the commands.
+- `readInputFromOverrideList` - Comma separated list of parameters to read from override command.
+- `readInputOverrideCommand` - A command line command to run (The command is formatted to replace
+  "{0}" with the parameter parameter name).
diff --git a/versioned_docs/version-3/03-github-cloud-runner/06-advanced-topics/04-custom-hooks/01-custom-job.mdx b/versioned_docs/version-3/03-github-cloud-runner/06-advanced-topics/04-custom-hooks/01-custom-job.mdx
new file mode 100644
index 00000000..ade52d59
--- /dev/null
+++ b/versioned_docs/version-3/03-github-cloud-runner/06-advanced-topics/04-custom-hooks/01-custom-job.mdx
@@ -0,0 +1,4 @@
+# Custom Jobs
+
+You can run a custom job instead of the default build workflow simplfy by specifying the `customJob`
+parameter.
diff --git a/versioned_docs/version-3/03-github-cloud-runner/06-advanced-topics/04-custom-hooks/03-command-hooks.mdx b/versioned_docs/version-3/03-github-cloud-runner/06-advanced-topics/04-custom-hooks/03-command-hooks.mdx
new file mode 100644
index 00000000..ee1f2378
--- /dev/null
+++ b/versioned_docs/version-3/03-github-cloud-runner/06-advanced-topics/04-custom-hooks/03-command-hooks.mdx
@@ -0,0 +1,12 @@
+# Command Hooks
+
+Custom commands can be injected into the standard build workflow via yaml or files.
+
+```yaml
+- name: example hook
+  hook: |
+    step:
+      - before
+    commands: |
+      echo "hello world!"
+```
diff --git a/versioned_docs/version-3/03-github-cloud-runner/06-advanced-topics/04-custom-hooks/04-container-hooks.mdx b/versioned_docs/version-3/03-github-cloud-runner/06-advanced-topics/04-custom-hooks/04-container-hooks.mdx
new file mode 100644
index 00000000..6e0a9adc
--- /dev/null
+++ b/versioned_docs/version-3/03-github-cloud-runner/06-advanced-topics/04-custom-hooks/04-container-hooks.mdx
@@ -0,0 +1,13 @@
+# Container Hooks
+
+Custom docker container steps can be run as part of the standard build workflow. Custom steps can
+also be run standalone.
+
+Custom steps can be specified via the CustomSteps parameter or via Custom Step files.
+
+```yaml
+- name: upload
+  image: amazon/aws-cli
+  commands: |
+    echo "hello world!"
+```
diff --git a/versioned_docs/version-3/03-github-cloud-runner/06-advanced-topics/04-custom-hooks/05-premade-container-jobs.mdx b/versioned_docs/version-3/03-github-cloud-runner/06-advanced-topics/04-custom-hooks/05-premade-container-jobs.mdx
new file mode 100644
index 00000000..a87c9586
--- /dev/null
+++ b/versioned_docs/version-3/03-github-cloud-runner/06-advanced-topics/04-custom-hooks/05-premade-container-jobs.mdx
@@ -0,0 +1,38 @@
+# Premade Container Jobs
+
+## Cache syncronization
+
+### Upload Cache entry to AWS S3
+
+Upload cache results from build to AWS S3.
+
+`aws-s3-upload-cache`
+
+### Download Latest Cache entry from AWS S3
+
+Downloads library and git LFS cache from AWS S3.
+
+`aws-s3-pull-cache`
+
+## Artifacts
+
+## Upload Build Artifact To AWS S3
+
+`aws-s3-upload-build`
+
+Upload build artifact to AWS S3. (Currently only supports lz4 enabled which is default.)
+
+## Upload Project Artifact To AWS S3 (To Do)
+
+Upload project artifact to AWS S3. (Currently only supports lz4 enabled which is default.)
+
+## Artifact entire project folder (To Do)
+
+archive to tar format, compress with lz4 if enabled and store in persistent cache folder. (Can then
+upload.)
+
+## Deploy
+
+## Upload to Steam (To Do)
+
+upload build folder to given steam branch
diff --git a/versioned_docs/version-3/03-github-cloud-runner/06-advanced-topics/04-custom-hooks/_category_.yaml b/versioned_docs/version-3/03-github-cloud-runner/06-advanced-topics/04-custom-hooks/_category_.yaml
new file mode 100644
index 00000000..445f7ab4
--- /dev/null
+++ b/versioned_docs/version-3/03-github-cloud-runner/06-advanced-topics/04-custom-hooks/_category_.yaml
@@ -0,0 +1,5 @@
+---
+position: 4.0
+label: Custom Hooks
+collapsible: true
+collapsed: true
diff --git a/versioned_docs/version-3/03-github-cloud-runner/06-advanced-topics/05-logging.mdx b/versioned_docs/version-3/03-github-cloud-runner/06-advanced-topics/05-logging.mdx
new file mode 100644
index 00000000..99660d31
--- /dev/null
+++ b/versioned_docs/version-3/03-github-cloud-runner/06-advanced-topics/05-logging.mdx
@@ -0,0 +1,13 @@
+# Logging
+
+Logs are streamed from the workload to the GameCI origin unless you use the
+
+## Kubernetes
+
+- Native Kubernetes logging api
+
+## AWS
+
+- Fargate log to Cloud Watch
+- Subscription from Cloud Watch to Kinesis
+- GameCI streams from logs from Kinesis
diff --git a/versioned_docs/version-3/03-github-cloud-runner/06-advanced-topics/06-secrets.mdx b/versioned_docs/version-3/03-github-cloud-runner/06-advanced-topics/06-secrets.mdx
new file mode 100644
index 00000000..17bae040
--- /dev/null
+++ b/versioned_docs/version-3/03-github-cloud-runner/06-advanced-topics/06-secrets.mdx
@@ -0,0 +1,14 @@
+# Secrets
+
+Secrets are transferred to workload containers as secrets via the built-in secrets system the
+provider being used supports.
+
+## Kubernetes
+
+Secrets are created as native Kubernetes secret objects and mounted to job containers as env
+variables.
+
+## AWS
+
+Secrets are created as aws secret manager secrets and mounted to fargate tasks from secrets to env
+variables.
diff --git a/versioned_docs/version-3/03-github-cloud-runner/06-advanced-topics/09-gitlab/01-introduction-gitlab.mdx b/versioned_docs/version-3/03-github-cloud-runner/06-advanced-topics/09-gitlab/01-introduction-gitlab.mdx
new file mode 100644
index 00000000..86b25959
--- /dev/null
+++ b/versioned_docs/version-3/03-github-cloud-runner/06-advanced-topics/09-gitlab/01-introduction-gitlab.mdx
@@ -0,0 +1,3 @@
+# GitLab Introduction
+
+You can use GitLab with Cloud Runner via the Command Line mode.
diff --git a/versioned_docs/version-3/03-github-cloud-runner/06-advanced-topics/09-gitlab/_category_.yaml b/versioned_docs/version-3/03-github-cloud-runner/06-advanced-topics/09-gitlab/_category_.yaml
new file mode 100644
index 00000000..0407bcd5
--- /dev/null
+++ b/versioned_docs/version-3/03-github-cloud-runner/06-advanced-topics/09-gitlab/_category_.yaml
@@ -0,0 +1,5 @@
+---
+position: 9.0
+label: GitLab Integration
+collapsible: true
+collapsed: true
diff --git a/versioned_docs/version-3/03-github-cloud-runner/06-advanced-topics/10-github/01-github-checks.mdx b/versioned_docs/version-3/03-github-cloud-runner/06-advanced-topics/10-github/01-github-checks.mdx
new file mode 100644
index 00000000..94fd90d9
--- /dev/null
+++ b/versioned_docs/version-3/03-github-cloud-runner/06-advanced-topics/10-github/01-github-checks.mdx
@@ -0,0 +1,7 @@
+# GitHub Checks
+
+By enabling the `githubCheck` parameter, the cloud runner job will create a GitHub check for each
+step.
+
+The step will show useful details about the job. This is especially useful in combination with async
+mode, as you can run very long jobs.
diff --git a/versioned_docs/version-3/03-github-cloud-runner/06-advanced-topics/10-github/_category_.yaml b/versioned_docs/version-3/03-github-cloud-runner/06-advanced-topics/10-github/_category_.yaml
new file mode 100644
index 00000000..ecbee03f
--- /dev/null
+++ b/versioned_docs/version-3/03-github-cloud-runner/06-advanced-topics/10-github/_category_.yaml
@@ -0,0 +1,5 @@
+---
+position: 10.0
+label: GitHub Integration
+collapsible: true
+collapsed: true
diff --git a/versioned_docs/version-3/03-github-cloud-runner/06-advanced-topics/_category_.yaml b/versioned_docs/version-3/03-github-cloud-runner/06-advanced-topics/_category_.yaml
new file mode 100644
index 00000000..da411968
--- /dev/null
+++ b/versioned_docs/version-3/03-github-cloud-runner/06-advanced-topics/_category_.yaml
@@ -0,0 +1,5 @@
+---
+position: 5.0
+label: Advanced topics
+collapsible: true
+collapsed: true
diff --git a/versioned_docs/version-3/03-github-cloud-runner/_category_.yaml b/versioned_docs/version-3/03-github-cloud-runner/_category_.yaml
new file mode 100644
index 00000000..cbda169c
--- /dev/null
+++ b/versioned_docs/version-3/03-github-cloud-runner/_category_.yaml
@@ -0,0 +1,5 @@
+---
+position: 3.1
+label: Github (Cloud Runner)
+collapsible: true
+collapsed: true
diff --git a/versioned_docs/version-3/03-github/01-getting-started.mdx b/versioned_docs/version-3/03-github/01-getting-started.mdx
new file mode 100644
index 00000000..718af7d1
--- /dev/null
+++ b/versioned_docs/version-3/03-github/01-getting-started.mdx
@@ -0,0 +1,434 @@
+import Video from '../../../src/components/video/video';
+
+# Getting started
+
+GitHub [Actions for Unity](https://github.com/game-ci/unity-actions) provide the fastest and
+**easiest** way to automatically test and build any Unity project.
+
+There are a few parts to setting up a workflow. Steps may slightly differ depending on each license
+type.
+
+## Mental model
+
+#### Overall steps
+
+1. Understand how [Github Actions](https://docs.github.com/en/actions) work.
+2. Configure a license for Unity.
+3. Set up a workflow for your project.
+4. Result: Merge pull requests with more confidence.
+
+#### Setting up a workflow
+
+Setting up a workflow is easy!
+
+Create a file called `.github/workflows/main.yml` in your repository and configure the following
+steps;
+
+1. Checkout your repository using [Checkout](https://github.com/marketplace/actions/checkout).
+2. Cache Unity Library folder using [Cache](https://github.com/marketplace/actions/cache).
+3. Configure your test job using
+   [Test Runner](https://github.com/marketplace/actions/unity-test-runner).
+4. Configure your build job using [Builder](https://github.com/marketplace/actions/unity-builder).
+5. Deploy your application.
+
+_**Note:** all steps will be explained in the next chapters._
+
+## Support
+
+### First time using GitHub Actions?
+
+Read the official documentation on how to setup a
+[workflow](https://help.github.com/en/actions/automating-your-workflow-with-github-actions/configuring-a-workflow).
+
+Any subsequent steps assume you have read the above.
+
+### Supported Unity versions
+
+Unity Actions are using [game-ci/docker](https://github.com/game-ci/docker/) since `unity-builder`
+version 2. Any version in this [list](/docs/docker/versions) can be used.
+
+## Video Tutorial
+
+<Video url="https://www.youtube-nocookie.com/embed/M2BZr02uai0" />
+
+## Workflow examples
+
+Below are workflow examples displaying various levels of complexity.
+
+It is **recommended** to start from the
+[Simple Example](/docs/github/getting-started#simple-example) and work your way down the page.
+
+### Simple example
+
+This example tests your project then builds it for a single target (WebGL in this case). It will run
+sequentially.
+
+This example assumes that your Unity project is in the root of your repository.
+
+```yaml
+name: Actions 😎
+
+on: [push, pull_request]
+
+jobs:
+  build:
+    name: Build my project ✨
+    runs-on: ubuntu-latest
+    steps:
+      # Checkout
+      - name: Checkout repository
+        uses: actions/checkout@v3
+        with:
+          lfs: true
+
+      # Cache
+      - uses: actions/cache@v3
+        with:
+          path: Library
+          key: Library-${{ hashFiles('Assets/**', 'Packages/**', 'ProjectSettings/**') }}
+          restore-keys: |
+            Library-
+
+      # Test
+      - name: Run tests
+        uses: game-ci/unity-test-runner@v3
+        env:
+          UNITY_LICENSE: ${{ secrets.UNITY_LICENSE }}
+        with:
+          githubToken: ${{ secrets.GITHUB_TOKEN }}
+
+      # Build
+      - name: Build project
+        uses: game-ci/unity-builder@v3
+        env:
+          UNITY_LICENSE: ${{ secrets.UNITY_LICENSE }}
+          UNITY_EMAIL: ${{ secrets.UNITY_EMAIL }}
+          UNITY_PASSWORD: ${{ secrets.UNITY_PASSWORD }}
+        with:
+          targetPlatform: WebGL
+
+      # Output
+      - uses: actions/upload-artifact@v3
+        with:
+          name: Build
+          path: build
+```
+
+### Simple example with Git LFS
+
+If you are using GitHub's git-lfs hosting service to store your large binary assets, you will want
+to cache them to avoid consuming massive amounts of bandwidth. The extra steps in this example try
+to restore your git-lfs assets from a cache before doing a git lfs pull.
+
+```yaml
+name: Actions 😎
+
+on: [push, pull_request]
+
+jobs:
+  build:
+    name: Build my project ✨
+    runs-on: ubuntu-latest
+    steps:
+      # Checkout (without LFS)
+      - name: Checkout repository
+        uses: actions/checkout@v3
+
+      # Git LFS
+      - name: Create LFS file list
+        run: git lfs ls-files -l | cut -d' ' -f1 | sort > .lfs-assets-id
+
+      - name: Restore LFS cache
+        uses: actions/cache@v3
+        id: lfs-cache
+        with:
+          path: .git/lfs
+          key: ${{ runner.os }}-lfs-${{ hashFiles('.lfs-assets-id') }}
+
+      - name: Git LFS Pull
+        run: |
+          git lfs pull
+          git add .
+          git reset --hard
+
+      # Cache
+      - uses: actions/cache@v3
+        with:
+          path: Library
+          key: Library-${{ hashFiles('Assets/**', 'Packages/**', 'ProjectSettings/**') }}
+          restore-keys: |
+            Library-
+
+      # Test
+      - name: Run tests
+        uses: game-ci/unity-test-runner@v3
+        env:
+          UNITY_LICENSE: ${{ secrets.UNITY_LICENSE }}
+        with:
+          githubToken: ${{ secrets.GITHUB_TOKEN }}
+
+      # Build
+      - name: Build project
+        uses: game-ci/unity-builder@v3
+        env:
+          UNITY_LICENSE: ${{ secrets.UNITY_LICENSE }}
+          UNITY_EMAIL: ${{ secrets.UNITY_EMAIL }}
+          UNITY_PASSWORD: ${{ secrets.UNITY_PASSWORD }}
+        with:
+          targetPlatform: WebGL
+
+      # Output
+      - uses: actions/upload-artifact@v3
+        with:
+          name: Build
+          path: build
+```
+
+### Parallel execution of Tests and Builds
+
+This will run tests in parallel with the Build, in this case for Windows 64bit.
+
+This example assumes that your Unity project is in the root of your repository.
+
+```yaml
+name: Actions 😎
+
+on: [push, pull_request]
+
+jobs:
+  test:
+    name: Test my project 🧪
+    runs-on: ubuntu-latest
+    steps:
+      # Checkout
+      - name: Checkout repository
+        uses: actions/checkout@v3
+        with:
+          lfs: true
+
+      # Cache
+      - uses: actions/cache@v3
+        with:
+          path: Library
+          key: Library-${{ hashFiles('Assets/**', 'Packages/**', 'ProjectSettings/**') }}
+          restore-keys: |
+            Library-
+
+      # Test
+      - name: Run tests
+        uses: game-ci/unity-test-runner@v3
+        env:
+          UNITY_LICENSE: ${{ secrets.UNITY_LICENSE }}
+        with:
+          githubToken: ${{ secrets.GITHUB_TOKEN }}
+
+  build:
+    name: Build my project ✨
+    runs-on: ubuntu-latest
+    steps:
+      # Checkout
+      - name: Checkout repository
+        uses: actions/checkout@v3
+        with:
+          lfs: true
+
+      # Cache
+      - uses: actions/cache@v3
+        with:
+          path: Library
+          key: Library-${{ hashFiles('Assets/**', 'Packages/**', 'ProjectSettings/**') }}
+          restore-keys: |
+            Library-
+
+      # Build
+      - name: Build project
+        uses: game-ci/unity-builder@v3
+        env:
+          UNITY_LICENSE: ${{ secrets.UNITY_LICENSE }}
+          UNITY_EMAIL: ${{ secrets.UNITY_EMAIL }}
+          UNITY_PASSWORD: ${{ secrets.UNITY_PASSWORD }}
+        with:
+          targetPlatform: StandaloneWindows64
+          allowDirtyBuild: true
+
+      # Output
+      - uses: actions/upload-artifact@v3
+        with:
+          name: Build
+          path: build
+```
+
+### Advanced IL2CPP example
+
+This example leverages the powerful Github Actions construct called a
+[matrix](https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstrategy)
+to test and build for multiple versions of Unity and several target platforms in parallel.
+
+IL2CPP builds require the base operating system to match the build target.
+
+Below is an example to build for all supported platforms with the IL2CPP scripting backend enabled
+in the project settings.
+
+> **Note: Tests are currently only compatible on Linux hosts.**
+
+```yaml
+name: Actions 😎
+
+on: [push, pull_request]
+
+jobs:
+  buildAndTestForLinuxBasedPlatforms:
+    name: Build for ${{ matrix.targetPlatform }}
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        projectPath:
+          - test-project
+        unityVersion:
+          - 2019.4.1f1
+          - 2020.2.1f1
+        targetPlatform:
+          - StandaloneLinux64 # Build a Linux 64-bit standalone.
+          - iOS # Build an iOS player.
+          - Android # Build an Android player.
+          - WebGL # WebGL.
+    steps:
+      - uses: actions/checkout@v3
+        with:
+          fetch-depth: 0
+          lfs: true
+      - uses: actions/cache@v3
+        with:
+          path: ${{ matrix.projectPath }}/Library
+          key:
+            Library-${{ matrix.projectPath }}-${{ matrix.targetPlatform }}-${{
+            hashFiles(matrix.projectPath) }}
+          restore-keys: |
+            Library-${{ matrix.projectPath }}-${{ matrix.targetPlatform }}-
+            Library-${{ matrix.projectPath }}-
+            Library-
+      - uses: game-ci/unity-test-runner@v3
+        id: testRunner
+        env:
+          UNITY_LICENSE: ${{ secrets.UNITY_LICENSE }}
+        with:
+          projectPath: ${{ matrix.projectPath }}
+          unityVersion: ${{ matrix.unityVersion }}
+          githubToken: ${{ secrets.GITHUB_TOKEN }}
+      - uses: actions/upload-artifact@v3
+        if: always()
+        with:
+          name: Test results (all modes)
+          path: ${{ steps.testRunner.outputs.artifactsPath }}
+      - if: matrix.targetPlatform == 'Android'
+        uses: jlumbroso/free-disk-space@v1.2.0
+      - uses: game-ci/unity-builder@v3
+        env:
+          UNITY_LICENSE: ${{ secrets.UNITY_LICENSE }}
+          UNITY_EMAIL: ${{ secrets.UNITY_EMAIL }}
+          UNITY_PASSWORD: ${{ secrets.UNITY_PASSWORD }}
+        with:
+          projectPath: ${{ matrix.projectPath }}
+          unityVersion: ${{ matrix.unityVersion }}
+          targetPlatform: ${{ matrix.targetPlatform }}
+          customParameters: '-myParameter myValue -myBoolean -ThirdParameter andItsValue'
+      - uses: actions/upload-artifact@v3
+        with:
+          name: Build
+          path: build
+
+  buildForWindowsBasedPlatforms:
+    name: Build for ${{ matrix.targetPlatform }}
+    runs-on: windows-2019
+    strategy:
+      fail-fast: false
+      matrix:
+        projectPath:
+          - test-project
+        unityVersion:
+          - 2019.4.1f1
+          - 2020.2.1f1
+        targetPlatform:
+          - StandaloneWindows # Build a Windows 32-bit standalone.
+          - StandaloneWindows64 # Build a Windows 64-bit standalone.
+          - tvOS # Build an AppleTV player.
+          - WSAPlayer # Build a UWP App.
+
+    steps:
+      - uses: actions/checkout@v3
+        with:
+          fetch-depth: 0
+          lfs: true
+      - uses: actions/cache@v3
+        with:
+          path: ${{ matrix.projectPath }}/Library
+          key:
+            Library-${{ matrix.projectPath }}-${{ matrix.targetPlatform }}-${{
+            hashFiles(matrix.projectPath) }}
+          restore-keys: |
+            Library-${{ matrix.projectPath }}-${{ matrix.targetPlatform }}-
+            Library-${{ matrix.projectPath }}-
+            Library-
+      - uses: game-ci/unity-builder@v3
+        env:
+          UNITY_LICENSE: ${{ secrets.UNITY_LICENSE }}
+          UNITY_EMAIL: ${{ secrets.UNITY_EMAIL }}
+          UNITY_PASSWORD: ${{ secrets.UNITY_PASSWORD }}
+        with:
+          projectPath: ${{ matrix.projectPath }}
+          unityVersion: ${{ matrix.unityVersion }}
+          targetPlatform: ${{ matrix.targetPlatform }}
+          customParameters: '-myParameter myValue -myBoolean -ThirdParameter andItsValue'
+      - uses: actions/upload-artifact@v3
+        with:
+          name: Build
+          path: build
+
+  buildForMacOSBasedPlatforms:
+    name: Build for ${{ matrix.targetPlatform }}
+    runs-on: macos-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        projectPath:
+          - test-project
+        unityVersion:
+          - 2019.4.1f1
+          - 2020.2.1f1
+        targetPlatform:
+          - StandaloneOSX # Build a macOS standalone.
+
+    steps:
+      - uses: actions/checkout@v3
+        with:
+          fetch-depth: 0
+          lfs: true
+
+      - uses: actions/cache@v3
+        with:
+          path: ${{ matrix.projectPath }}/Library
+          key:
+            Library-${{ matrix.projectPath }}-${{ matrix.targetPlatform }}-${{
+            hashFiles(matrix.projectPath) }}
+          restore-keys: |
+            Library-${{ matrix.projectPath }}-${{ matrix.targetPlatform }}-
+            Library-${{ matrix.projectPath }}-
+            Library-
+
+      - uses: game-ci/unity-builder@v3
+        env:
+          UNITY_LICENSE: ${{ secrets.UNITY_LICENSE }}
+          UNITY_EMAIL: ${{ secrets.UNITY_EMAIL }}
+          UNITY_PASSWORD: ${{ secrets.UNITY_PASSWORD }}
+        with:
+          projectPath: ${{ matrix.projectPath }}
+          unityVersion: ${{ matrix.unityVersion }}
+          targetPlatform: ${{ matrix.targetPlatform }}
+          customParameters: '-myParameter myValue -myBoolean -ThirdParameter andItsValue'
+
+      - uses: actions/upload-artifact@v3
+        with:
+          name: Build
+          path: build
+```
diff --git a/versioned_docs/version-3/03-github/02-activation.mdx b/versioned_docs/version-3/03-github/02-activation.mdx
new file mode 100644
index 00000000..f75816d1
--- /dev/null
+++ b/versioned_docs/version-3/03-github/02-activation.mdx
@@ -0,0 +1,154 @@
+# Activation
+
+All actions use a Unity installation, which needs to be activated.
+
+Unity differentiates their methods between `personal` and `professional` licenses.
+
+Depending on whether you are using a free or paid version of Unity, you will need to follow the
+steps for either a [personal license](#personal-license) or a
+[professional license](#professional-license). Alternatively you can provide the url to a
+[License server](#license-server).
+
+## Personal license
+
+Follow these steps if you are using a free version of Unity.
+
+> _**Note:** Do NOT follow the steps for the personal license if you have a professional license._
+
+#### Mental model
+
+1. Request an activation file for usage on GitHub
+2. Use that file to acquire a license
+3. Set the license as a secret
+
+#### About the activation file
+
+You may use the
+[Unity - Request Activation File](https://github.com/marketplace/actions/unity-request-activation-file)
+action with the below instructions.
+
+The activation file uses machine identifiers so you cannot perform this step locally.
+
+Let's go!
+
+#### Acquiring an activation file
+
+Create a file called `.github/workflows/activation.yml` and add the below workflow definition to it:
+
+```yaml
+name: Acquire activation file
+on:
+  workflow_dispatch: {}
+jobs:
+  activation:
+    name: Request manual activation file 🔑
+    runs-on: ubuntu-latest
+    steps:
+      # Request manual activation file
+      - name: Request manual activation file
+        id: getManualLicenseFile
+        uses: game-ci/unity-request-activation-file@v2
+      # Upload artifact (Unity_v20XX.X.XXXX.alf)
+      - name: Expose as artifact
+        uses: actions/upload-artifact@v2
+        with:
+          name: ${{ steps.getManualLicenseFile.outputs.filePath }}
+          path: ${{ steps.getManualLicenseFile.outputs.filePath }}
+```
+
+Commit and push your workflow definition.
+
+#### Converting into a license
+
+:::caution
+
+**Unity no longer supports manual activation of Personal licenses**
+
+When activating your Personal Unity license, you may encounter an issue where only the "Unity Pro or
+Plus" option is available, preventing the activation of a Personal license. Here is a workaround to
+resolve this:
+
+1. Visit [license.unity3d.com](https://license.unity3d.com/manual) and upload the
+   `Unity_v20XX.X.XXXX.alf` file.
+2. On the "Activate your license" page, if the "Personal" option is not available, right-click on
+   the page and choose "Inspect" to open the browser's developer tools.
+3. Find the line of HTML that looks like this:
+   `<div class="option option-personal clear" style="display: none;">`.
+4. Delete `display: none;` from the `style` attribute to make the "Personal" option visible.
+5. Now you should be able to select the "Personal" option and proceed with the activation.
+
+You can discuss this issue or find additional assistance in the
+[related Discord conversation](https://discord.com/channels/710946343828455455/1138586951604248666)
+or [GitHub ticket](https://github.com/game-ci/documentation/issues/408).
+
+_For future reference, activating a license from the command line as documented on
+[Unity's Manual Page](https://docs.unity3d.com/Manual/ManagingYourUnityLicense.html) might be an
+alternative solution._
+
+:::
+
+Follow these (one-time) steps for simple activation.
+
+1. [Manually run](https://docs.github.com/en/actions/managing-workflow-runs/manually-running-a-workflow)
+   the above workflow.
+2. Download the manual activation file that now appeared as an artifact and extract the
+   `Unity_v20XX.X.XXXX.alf` file from the zip.
+3. Visit [license.unity3d.com](https://license.unity3d.com/manual) and upload the
+   `Unity_v20XX.X.XXXX.alf` file.
+4. You should now receive your license file (Unity_v20XX.x.ulf) as a download. It's ok if the
+   numbers don't match your Unity version exactly.
+5. Open `Github` > `<Your repository>` > `Settings` > `Secrets`.
+6. Create the following secrets;
+   - `UNITY_LICENSE` - _(Copy the contents of your license file into here)_
+   - `UNITY_EMAIL` - _(Add the email address that you use to login to Unity)_
+   - `UNITY_PASSWORD` - _(Add the password that you use to login to Unity)_
+
+**GameCI does not acquire nor store your Unity email or password. They are required for reactivating
+the license during build and test steps.**
+
+> _**Note:** When changing Unity version, you may need to repeat the same process._
+
+## Professional license
+
+1. Subscribe to Unity Plus or Unity Pro, and get your Serial Key from the
+   [Unity Subscriptions page](https://id.unity.com/en/subscriptions)
+2. Open `Github` > `<Your repository>` > `Settings` > `Secrets`
+3. Create the following secrets;
+   - `UNITY_SERIAL` - _(Add the serial key from step 1 that looks like
+     `XX-XXXX-XXXX-XXXX-XXXX-XXXX`)_
+   - `UNITY_EMAIL` - _(Add the email address that you use to login to Unity)_
+   - `UNITY_PASSWORD` - _(Add the password that you use to login to Unity)_
+
+**GameCI does not acquire nor store your Unity email or password. They are required for reactivating
+the license during build and test steps.**
+
+> _**Note:** Do NOT follow the steps for the personal license if you have a professional license._
+
+## License Server
+
+If you host your own Unity license server you can provide its url using `unityLicensingServer`. A
+floating license will be acquired before the build, and returned after.
+
+Example of use:
+
+```yaml
+- uses: game-ci/unity-builder@v3
+  with:
+    targetPlatform: WebGL
+    unityLicensingServer: [url to your license server]
+```
+
+## Optional steps
+
+- Verify your license using [Activate](https://github.com/marketplace/actions/unity-activate).
+- When using a pro license also use
+  [Return License](https://github.com/marketplace/actions/unity-return-license) to free up the
+  license allocation after usage.
+
+> _**Note:** Test runner and Builder already include these steps._
+
+## Next steps
+
+The license can now be used in test and build steps.
+
+You are now ready to start configuring these.
diff --git a/versioned_docs/version-3/03-github/03-test-runner.mdx b/versioned_docs/version-3/03-github/03-test-runner.mdx
new file mode 100644
index 00000000..197ae5c0
--- /dev/null
+++ b/versioned_docs/version-3/03-github/03-test-runner.mdx
@@ -0,0 +1,528 @@
+---
+toc_max_heading_level: 4
+---
+
+# Test runner
+
+Running your test suite in an automated workflow helps increase certainty when merging.
+
+Use [Unity - Test runner](https://github.com/marketplace/actions/unity-test-runner) to run your
+Unity tests.
+
+_Optional_ to include test coverage, use
+[Unity - Code Coverage](https://docs.unity3d.com/Packages/com.unity.testtools.codecoverage@1.2/manual/index.html)
+
+## Basic setup
+
+By default, the test runner will run both `playmode` and `editmode` tests.
+
+Create or edit the file called `.github/workflows/main.yml` and add a job to it.
+
+#### Personal license
+
+Personal licenses require a one-time manual activation step.
+
+Make sure you
+[acquire and activate](https://github.com/marketplace/actions/unity-request-activation-file) your
+license file and add it as a secret.
+
+Then, define the test step as follows:
+
+```yaml
+- uses: game-ci/unity-test-runner@v3
+  env:
+    UNITY_LICENSE: ${{ secrets.UNITY_LICENSE }}
+  with:
+    projectPath: path/to/your/project
+    githubToken: ${{ secrets.GITHUB_TOKEN }}
+```
+
+#### Professional license
+
+Make sure you have set up these variables in the activation step.
+
+- `UNITY_EMAIL` (should contain the email address for your Unity account)
+- `UNITY_PASSWORD` (the password that you use to login to Unity)
+- `UNITY_SERIAL` (the serial provided by Unity)
+
+Define the test step as follows:
+
+```yaml
+- uses: game-ci/unity-test-runner@v3
+  env:
+    UNITY_EMAIL: ${{ secrets.UNITY_EMAIL }}
+    UNITY_PASSWORD: ${{ secrets.UNITY_PASSWORD }}
+    UNITY_SERIAL: ${{ secrets.UNITY_SERIAL }}
+  with:
+    projectPath: path/to/your/project
+    githubToken: ${{ secrets.GITHUB_TOKEN }}
+```
+
+## License Server
+
+If you host your own Unity license server you can provide its url using `unityLicensingServer`. A
+floating license will be acquired before the tests run, and returned after.
+
+Example of use:
+
+```yaml
+- uses: game-ci/unity-test-runner@v3
+  with:
+    projectPath: path/to/your/project
+    unityLicensingServer: [url to your license server]
+```
+
+That is all you need to test your project.
+
+## Testing Unity packages
+
+The test runner offers basic support for testing Unity packages, with [a few caveats](#caveats).
+
+### Additional setup
+
+After performing [Basic setup](#basic-setup), three extra steps are required for testing Unity
+packages.
+
+#### Setting packageMode
+
+To indicate that the test runner is being run for a Unity package rather than a Unity project, set
+the [`packageMode`](#packagemode) configuration option to `true`.
+
+```yaml
+- uses: game-ci/unity-test-runner@v3
+  with:
+    packageMode: true
+```
+
+#### Passing a unityVersion
+
+Make sure that you explicitly pass the [`unityVersion`](#unityversion) argument, as it's necessary
+for the test runner to test Unity packages.
+
+```yaml
+- uses: game-ci/unity-test-runner@v3
+  with:
+    unityVersion: [your desired Unity version]
+```
+
+See the [GitHub Issue](https://github.com/game-ci/unity-test-runner/issues/227) for more details on
+why this is necessary.
+
+#### Choosing a package directory
+
+Make sure that the directory of the package being tested is **not** the same as the repository's
+root directory. This condition will cause the test runner to hang and fail.
+
+Currently, the only known workarounds for this failure are these two options:
+
+1. Restructure your repository to place the package being tested in a subdirectory of the
+   repository's root directory.
+2. Somehow temporarily move the package being tested to a subdirectory of the repository's root
+   directory within the GitHub Workflow where you're using the test runner.
+
+Whichever workaround you choose, make sure that the [`projectPath`](#projectpath) corresponds to
+wherever the package being tested is located at the time the test runner is called in your GitHub
+Workflow.
+
+See the [GitHub Issue](https://github.com/game-ci/unity-test-runner/issues/223) for more details and
+potential workarounds.
+
+### Caveats
+
+- As stated above, the action will fail if the directory of the package being tested is the same as
+  the root directory of the repository (this issue is being tracked
+  [here](https://github.com/game-ci/unity-test-runner/issues/223)).
+- As stated above, excluding `unityVersion` or passing a `unityVersion` configuration of `auto` when
+  testing a Unity package will cause the test runner to fail. The Unity version must be manually set
+  in the configuration options (this issue is being tracked
+  [here](https://github.com/game-ci/unity-test-runner/issues/227)).
+- The test runner can only test packages on Linux runners - Windows runners are currently not
+  supported (this issue is being tracked
+  [here](https://github.com/game-ci/unity-test-runner/issues/224))
+- Packages with dependencies outside of the Unity Registry have not been tested an may or may not
+  work with the test runner (this issue is being tracked
+  [here](https://github.com/game-ci/unity-test-runner/issues/225)).
+- There is currently no caching set up for the testing of Unity packages (this issue is being
+  tracked [here](https://github.com/game-ci/unity-test-runner/issues/226)).
+- If using the [`customImage`](#customImage) parameter to use a custom Docker image to test the
+  package, that image must have [`jq`](https://jqlang.github.io/jq/) installed, or else the test
+  runner will error. It is used to add the package being tested to a temporary Unity project's
+  package manifest at runtime.
+
+## Viewing test results
+
+The test results can be viewed from a
+[GitHub Status Check](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/about-status-checks).
+
+To get this functionality, simply provide the
+[GitHub Token](https://docs.github.com/en/actions/reference/authentication-in-a-workflow#about-the-github_token-secret)
+in order to view the tests results from
+[a check run](https://docs.github.com/en/rest/guides/getting-started-with-the-checks-api#about-check-runs).
+
+```yaml
+- uses: game-ci/unity-test-runner@v3
+  with:
+    githubToken: ${{ secrets.GITHUB_TOKEN }}
+```
+
+If you choose not to provide the `githubToken`, you may still upload the artifacts in order to
+access them.
+
+## Storing test results
+
+To be able to access the test results, they need to be uploaded as artifacts.
+
+To do this, it is recommended to use the official Github Actions
+[upload artifact action](https://github.com/marketplace/actions/upload-a-build-artifact).
+
+By default, Test Runner outputs its results to a folder named `artifacts`.
+
+```yaml
+- uses: actions/upload-artifact@v2
+  if: always()
+  with:
+    name: Test results
+    path: artifacts
+```
+
+Test results can now be downloaded as `Artifacts` in the `Actions` tab.
+
+#### Specifying artifacts folder
+
+You can specify a different `artifactsPath` in the test runner and reference this path using the
+`id` of the test step.
+
+```yaml
+- uses: game-ci/unity-test-runner@v3
+  id: myTestStep
+```
+
+```yaml
+- uses: actions/upload-artifact@v2
+  if: always()
+  with:
+    name: Test results
+    path: ${{ steps.myTestStep.outputs.artifactsPath }}
+```
+
+### Getting coverage results
+
+The results for the test code coverage are stored in the folder `CodeCoverage` and the path can be
+read by the step's `outputs.coveragePath`. These coverage options can be configured as part of the
+test and by default will create an XML and HTML web page reports.
+
+```yaml
+- uses: actions/upload-artifact@v2
+  if: always()
+  with:
+    name: Coverage results
+    path: ${{ steps.myTestStep.outputs.coveragePath }}
+```
+
+The coverage results will be generated for whatever tests were selected to run. If both `editmode`
+and `playmode` are selected by using `all`, then the results will have the combined coverage of both
+test modes.
+
+_Note_ Coverage results are generated with root permission so to move or edit the output in later
+steps you may need to use elevated permissions such as `sudo`.
+
+## Caching
+
+In order to make test runs (and builds) faster, you can cache Library files from previous runs.
+
+To do so, simply add Github Actions' official
+[cache action](https://github.com/marketplace/actions/cache) before any unity steps.
+
+```yaml
+- uses: actions/cache@v2
+  with:
+    path: path/to/your/project/Library
+    key: Library-MyProjectName-TargetPlatform
+    restore-keys: |
+      Library-MyProjectName-
+      Library-
+```
+
+This simple addition could speed up your test runs by more than 50%.
+
+Note that caching in this manner only applies to testing Unity **Projects**, not Unity **Packages**
+(see [Caveats](#caveats)).
+
+## Configuration options
+
+Below options can be specified under `with:` for the `unity-test-runner` action.
+
+#### unityVersion
+
+Version of Unity to use for testing the project. Use "auto" to get from your
+ProjectSettings/ProjectVersion.txt. ⚠️ If testing a Unity Package, this field is required and cannot
+be set to "auto".
+
+_**required:** `false`_ _**default:** `auto`_
+
+#### customImage
+
+Specific docker image that should be used for testing the project. If packageMode is true, this
+image must have [`jq`](https://jqlang.github.io/jq/) installed.
+
+```yaml
+- uses: game-ci/unity-test-runner@v3
+  with:
+    customImage: 'unityci/editor:2020.1.14f1-base-0'
+```
+
+_**required:** `false`_ _**default:** `""`_
+
+#### projectPath
+
+Specify the path to your Unity project or package to be tested. The path should be relative to the
+root of your project.
+
+_**required:** `false`_ _**default:** `<your project root>`_
+
+#### customParameters
+
+Custom parameters to configure the test runner.
+
+For example, you may refer to the
+[Unity Test Framework command line arguments](https://docs.unity3d.com/Packages/com.unity.test-framework@2.0/manual/reference-command-line.html)
+for options that could help with configuring your tests.
+
+Parameters must start with a hyphen (`-`) and may be followed by a value (without hyphen).
+
+Parameters without a value will be considered booleans (with a value of true).
+
+```yaml
+- uses: game-ci/unity-test-runner@v3
+  with:
+    customParameters: -profile SomeProfile -someBoolean -someValue exampleValue
+```
+
+_**required:** `false`_ _**default:** `""`_
+
+#### testMode
+
+The type of tests to be run by the test runner.
+
+Options are: `All`, `PlayMode`, `EditMode`, and `Standalone`.
+
+Note: `All` only runs `PlayMode` and `EditMode`. You must explicitly specify `Standalone` for it to
+run.
+
+_**required:** `false`_ _**default:** `All`_
+
+#### artifactsPath
+
+Path where the test results should be stored.
+
+In this folder a folder will be created for every test mode.
+
+_**required:** `false`_ _**default:** `artifacts`_
+
+#### coverageOptions
+
+Options for configuring code coverage, this configures the `-coverageOptions` parameter described
+unity's CodeCoverage documentation:
+[Using Code Coverage in batchmode](https://docs.unity3d.com/Packages/com.unity.testtools.codecoverage@1.2/manual/CoverageBatchmode.html).
+
+By default, this parameter is configured to generate an HTML report with additional metrics. This
+should be fine for most projects, but the webpage report can be quite large for projects with
+hundreds or thousands of large files.
+
+You can add arguments for `assemblyFilters` to specify an assembly to filter files that results are
+generated for. This is commonly used to ignore test files or external libraries. See the
+[Using Code Coverage in batchmode](https://docs.unity3d.com/Packages/com.unity.testtools.codecoverage@1.2/manual/CoverageBatchmode.html).
+For example, you can add the argument `assemblyFilters:+my.assembly.*` to only include files in the
+assemblies that match `+my.assembly.*`, the `*` is a wildcard. This will require making an assembly
+definition to manage scripts, see Unity's documentation on
+[Assembly definitions](https://docs.unity3d.com/2022.2/Documentation/Manual/ScriptCompilationAssemblyDefinitionFiles.html)
+for how to create and manage assembly definitions.
+
+To get coverage when testing a package, make sure you pass assemblies from the package you want
+covered to the `assemblyFilters` option.
+
+_**required:** `false`_ _**default:**
+`generateAdditionalMetrics;generateHtmlReport;generateBadgeReport`_
+
+#### useHostNetwork
+
+Initializes Docker using the host network.
+
+This is useful if Unity needs to access a local server that was started as part of your workflow.
+
+Options are: `true`, `false`
+
+_**required:** `false`_ _**default:** `false`_
+
+#### sshAgent
+
+SSH Agent path to forward to the container.
+
+This is useful if your manifest has a dependency on a private GitHub repo.
+
+_**required:** `false`_ _**default:** ``_
+
+#### sshPublicKeysDirectoryPath
+
+SSH directory path to mount in the container on `~/.ssh`. Must be used with `sshAgent`.
+
+It is recommended to have only public keys in this directory, and rely on `sshAgent` to manage
+private keys.
+
+This is useful if your manifest has a dependency on multiple private GitHub repos and you need to
+use multiple SSH deploy keys.
+
+_**required:** `false`_ _**default:** ``_
+
+#### gitPrivateToken
+
+GitHub Private Access Token (PAT) to pull from GitHub.
+
+This is useful if your manifest has a dependency on a private GitHub repo.
+
+_**required:** `false`_ _**default:** ``_
+
+#### githubToken
+
+Token to authorize access to the GitHub REST API. If provided, a check run will be created with the
+test results.
+
+It is recommended to use `githubToken: ${{ secrets.GITHUB_TOKEN }}`, but creating the check from
+[a fork of your repo](https://docs.github.com/en/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)
+may require using a
+[Personal Access Token](https://docs.github.com/en/github/authenticating-to-github/creating-a-personal-access-token#creating-a-token).
+
+Reference the [GitHub Checks API docs](https://docs.github.com/en/rest/reference/checks) for details
+on
+[creating CI tests with the Checks API](https://docs.github.com/en/developers/apps/creating-ci-tests-with-the-checks-api).
+
+_**required:** `false`_ _**default:** ``_
+
+#### checkName
+
+Name for the check run that is created when a github token is provided.
+
+It may be useful to customize the check name if, for example, you have a job matrix with multiple
+unity versions.
+
+_**required:** `false`_ _**default:** `Test Results`_
+
+#### packageMode
+
+Whether the tests are being run for a Unity package instead of a Unity project.
+
+If true, the action can only be run on Linux runners, and any custom docker image passed to this
+action must have [`jq`](https://jqlang.github.io/jq/) installed.
+
+NOTE: may not work properly for packages with dependencies outside of the Unity Registry.
+
+See [Testing Unity packages](#testing-unity-packages) for more information.
+
+_**required:** `false`_ _**default:** `false`_
+
+## Complete example
+
+A complete workflow that tests all modes separately could look like this:
+
+```yaml
+name: Test project
+
+on: [push, pull_request]
+
+jobs:
+  testAllModes:
+    name: Test in ${{ matrix.testMode }}
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        projectPath:
+          - test-project
+        testMode:
+          - playmode
+          - editmode
+          - standalone
+    steps:
+      - uses: actions/checkout@v2
+        with:
+          lfs: true
+      - uses: actions/cache@v2
+        with:
+          path: ${{ matrix.projectPath }}/Library
+          key: Library-${{ matrix.projectPath }}
+          restore-keys: |
+            Library-
+      - uses: game-ci/unity-test-runner@v3
+        id: tests
+        env:
+          UNITY_LICENSE: ${{ secrets.UNITY_LICENSE }}
+        with:
+          projectPath: ${{ matrix.projectPath }}
+          testMode: ${{ matrix.testMode }}
+          artifactsPath: ${{ matrix.testMode }}-artifacts
+          githubToken: ${{ secrets.GITHUB_TOKEN }}
+          checkName: ${{ matrix.testMode }} Test Results
+          coverageOptions: 'generateAdditionalMetrics;generateHtmlReport;generateBadgeReport;assemblyFilters:+my.assembly.*'
+      - uses: actions/upload-artifact@v2
+        if: always()
+        with:
+          name: Test results for ${{ matrix.testMode }}
+          path: ${{ steps.tests.outputs.artifactsPath }}
+      - uses: actions/upload-artifact@v2
+        if: always()
+        with:
+          name: Coverage results for ${{ matrix.testMode }}
+          path: ${{ steps.tests.outputs.coveragePath }}
+```
+
+## Complete Example (Testing a Package)
+
+A complete workflow that tests all modes separately (for a package rather than a project) could look
+like this:
+
+```yaml
+name: Test package
+
+on: [push, pull_request]
+
+jobs:
+  testAllModes:
+    name: Test in ${{ matrix.testMode }}
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        projectPath:
+          - test-package
+        unityVersion: '2020.3.0f1' # some version must be included for package testing
+        testMode:
+          - playmode
+          - editmode
+    steps:
+      - uses: actions/checkout@v2
+        with:
+          lfs: true
+      - uses: game-ci/unity-test-runner@v3
+        id: tests
+        env:
+          UNITY_LICENSE: ${{ secrets.UNITY_LICENSE }}
+        with:
+          packageMode: true
+          projectPath: ${{ matrix.projectPath }}
+          unityVersion: ${{ matrix.unityVersion }}
+          testMode: ${{ matrix.testMode }}
+          artifactsPath: ${{ matrix.testMode }}-artifacts
+          githubToken: ${{ secrets.GITHUB_TOKEN }}
+          checkName: ${{ matrix.testMode }} Test Results
+          coverageOptions: 'generateAdditionalMetrics;generateHtmlReport;generateBadgeReport;assemblyFilters:+my.assembly.*'
+      - uses: actions/upload-artifact@v2
+        if: always()
+        with:
+          name: Test results for ${{ matrix.testMode }}
+          path: ${{ steps.tests.outputs.artifactsPath }}
+      - uses: actions/upload-artifact@v2
+        if: always()
+        with:
+          name: Coverage results for ${{ matrix.testMode }}
+          path: ${{ steps.tests.outputs.coveragePath }}
+```
diff --git a/versioned_docs/version-3/03-github/04-builder.mdx b/versioned_docs/version-3/03-github/04-builder.mdx
new file mode 100644
index 00000000..82468b79
--- /dev/null
+++ b/versioned_docs/version-3/03-github/04-builder.mdx
@@ -0,0 +1,630 @@
+---
+toc_max_heading_level: 4
+---
+
+# Builder
+
+Building the project as part of a workflow may help to create mind-space and focus on the project
+itself.
+
+Use [Unity - Builder](https://github.com/marketplace/actions/unity-builder) to automatically build
+Unity projects for different platforms.
+
+## Basic setup
+
+#### Credentials
+
+Make sure you have set up these variables in the [activation step](/docs/github/activation):
+
+- `UNITY_EMAIL` (the email address for your Unity account)
+- `UNITY_PASSWORD` (the password that you use to login to Unity)
+
+NOTE: Issues have been observed when using a `UNITY_PASSWORD` with special characters. It is
+recommended to use a password without any special characters (mixed-case alphanumeric characters
+only).
+
+**GameCI does not acquire nor store your Unity email or password. They are required for reactivating
+the license during build and test steps.**
+
+#### Workflow file setup
+
+Create or edit the file called `.github/workflows/main.yml` and add a job to it.
+
+#### Personal license
+
+Personal licenses require a one-time manual activation step.
+
+Make sure you [acquire and activate](/docs/github/activation) your license file, and add it as a
+secret.
+
+Then, define the build step as follows:
+
+```yaml
+- uses: game-ci/unity-builder@v3
+  env:
+    UNITY_LICENSE: ${{ secrets.UNITY_LICENSE }}
+    UNITY_EMAIL: ${{ secrets.UNITY_EMAIL }}
+    UNITY_PASSWORD: ${{ secrets.UNITY_PASSWORD }}
+  with:
+    targetPlatform: WebGL
+```
+
+#### Professional license
+
+Make sure you have set up these variables in the activation step:
+
+- `UNITY_EMAIL` (should contain the email address for your Unity account)
+- `UNITY_PASSWORD` (the password that you use to login to Unity)
+- `UNITY_SERIAL` (the serial provided by Unity)
+
+Then, define the build step as follows:
+
+```yaml
+- uses: game-ci/unity-builder@v3
+  env:
+    UNITY_EMAIL: ${{ secrets.UNITY_EMAIL }}
+    UNITY_PASSWORD: ${{ secrets.UNITY_PASSWORD }}
+    UNITY_SERIAL: ${{ secrets.UNITY_SERIAL }}
+  with:
+    targetPlatform: WebGL
+```
+
+## License Server
+
+If you host your own Unity license server internally you can provide its url using
+`unityLicensingServer`. A floating license will be acquired before the build, and returned after.
+
+Example of use:
+
+```yaml
+- uses: game-ci/unity-builder@v3
+  with:
+    targetPlatform: WebGL
+    unityLicensingServer: [url to your license server]
+```
+
+That is all you need to build your project.
+
+By default, the enabled scenes from the project's settings will be built.
+
+## Storing the build
+
+To be able to access your built files, they need to be uploaded as artifacts. To do this it is
+recommended to use Github Actions official
+[upload artifact action](https://github.com/marketplace/actions/upload-artifact) after any build
+action.
+
+By default, Builder outputs it's builds to a folder named `build`.
+
+Example:
+
+```yaml
+- uses: actions/upload-artifact@v2
+  with:
+    name: Build
+    path: build
+```
+
+Builds can now be downloaded as Artifacts in the Actions tab.
+
+## Caching
+
+In order to make builds run faster, you can cache Library files from previous builds. To do so
+simply add Github Actions official [cache action](https://github.com/marketplace/actions/cache)
+before any unity steps.
+
+Example:
+
+```yaml
+- uses: actions/cache@v2
+  with:
+    path: path/to/your/project/Library
+    key: Library-MyProjectName-TargetPlatform
+    restore-keys: |
+      Library-MyProjectName-
+      Library-
+```
+
+This simple addition could speed up your build by more than 50%.
+
+## Configuration options
+
+Below options can be specified under `with:` for the `unity-builder` action.
+
+#### targetPlatform
+
+Platform that the build should target.
+
+Must be one of the [allowed values](https://docs.unity3d.com/ScriptReference/BuildTarget.html)
+listed in the Unity scripting manual.
+
+_**required:** `true`_
+
+#### unityVersion
+
+Version of Unity to use for building the project. Use "auto" to get from your
+ProjectSettings/ProjectVersion.txt
+
+_**required:** `false`_ _**default:** `auto`_
+
+#### customImage
+
+Specific docker image that should be used for building the project.
+
+```yaml
+- uses: game-ci/unity-builder@v3
+  with:
+    customImage: 'unityci/editor:2020.1.14f1-base-0'
+```
+
+_**required:** `false`_ _**default:** `""`_
+
+#### projectPath
+
+Specify the path to your Unity project to be built. The path should be relative to the root of your
+project.
+
+_**required:** `false`_ _**default:** `<your project root>`_
+
+#### buildName
+
+Name of the build. Also the folder in which the build will be stored within `buildsPath`.
+
+_**required:** `false`_ _**default:** `<build_target>`_
+
+#### buildsPath
+
+Path where the builds should be stored.
+
+In this folder a folder will be created for every targetPlatform.
+
+_**required:** `false`_ _**default:** `build`_
+
+#### buildMethod
+
+Custom command to run your build.
+
+There are two conditions for a custom buildMethod:
+
+- Must reference a valid path to a `static` method.
+- The class must reside in the `Assets/Editor` directory (or in an Editor Assembly).
+
+Example:
+
+```yaml
+- uses: game-ci/unity-builder@v3
+  with:
+    buildMethod: EditorNamespace.BuilderClassName.StaticBuildMethod
+```
+
+To get started with a modified version of the default Unity Builder build script, you can copy
+[BuildScript.cs](https://github.com/game-ci/documentation/blob/main/example/BuildScript.cs) to your
+`Assets/Editor/UnityBuilderAction` directory and reference it:
+
+```yaml
+- uses: game-ci/unity-builder@v3
+  with:
+    buildMethod: UnityBuilderAction.BuildScript.Build
+```
+
+If you need to pass custom parameters to this build method, see `customParameters` below.
+
+_**required:** `false`_ _**default:** Built-in script that will run a build out of the box._
+
+#### customParameters
+
+Custom parameters to configure the build.
+
+Parameters must start with a hyphen (`-`) and may be followed by a value (without hyphen).
+
+Parameters without a value will be considered booleans (with a value of true).
+
+```yaml
+- uses: game-ci/unity-builder@v3
+  with:
+    customParameters: -profile SomeProfile -someBoolean -someValue exampleValue
+```
+
+There are 2 main use cases:
+
+- To pass your own custom parameters to be used with `buildMethod` above. Note that environment
+  variables set in the workflow file will not be available in the environment running Unity, so use
+  this mechanism instead.
+- To pass [Unity Build Options](https://docs.unity3d.com/ScriptReference/BuildOptions.html) (for
+  example, `customParameters: -standaloneBuildSubtarget Server` will do server builds)
+
+_**required:** `false`_ _**default:** `""`_
+
+#### versioning
+
+Configure a specific versioning strategy
+
+```yaml
+- uses: game-ci/unity-builder@v3
+  with:
+    versioning: Semantic
+```
+
+Find the available strategies below:
+
+##### Semantic
+
+Versioning out of the box! **(recommended)**
+
+> Compatible with **all platforms**. Does **not** modify your repository. Requires **zero
+> configuration**.
+
+How it works:
+
+> Generates a version based on [semantic versioning](https://semver.org/). Follows
+> `<major>.<minor>.<patch>` for example `0.17.2`. The latest tag dictates `<major>.<minor>`
+> (defaults to 0.0 for no tag). The number of commits (since the last tag, if any) is used for
+> `<patch>`. To increment major or minor version, manually add a tag to a commit that follows the
+> `<major>.<minor>` versioning convention. Optionally, the version number can have a `v` prefix, for
+> example `v0.17`.
+
+No configuration required.
+
+##### Tag
+
+Generates the version based on the git tag of the latest commit (HEAD). For example `0.17.2` will
+generate the version `0.17.2`. A leading "v" is stripped, so a version of `v1.3.3` will generate a
+version of `1.3.3`. **(advanced users)**
+
+> Compatible with **all platforms**. Does **not** modify your repository.
+
+##### Custom
+
+Allows specifying a custom version in the `version` field. **(advanced users)**
+
+> This strategy is useful when your project or pipeline has some kind of orchestration that
+> determines the versions.
+
+##### None
+
+No version will be set by Builder. **(not recommended)**
+
+> Not recommended unless you generate a new version in a pre-commit hook. Manually setting versions
+> is error-prone.
+
+#### androidVersionCode
+
+Configure the android `versionCode`.
+
+When not specified, the version code is generated from the version using the
+`major * 1000000 + minor * 1000 + patch` scheme;
+
+#### androidExportType
+
+Set this flag to `androidPackage` to build an apk, `androidAppBundle` for an aab, or
+`androidStudioProject` to build an Android Studio Project.
+
+```yaml
+- uses: game-ci/unity-builder@v3
+  with:
+    androidExportType: 'androidAppBundle'
+    androidKeystoreName: user.keystore
+    androidKeystoreBase64: ${{ secrets.ANDROID_KEYSTORE_BASE64 }}
+    androidKeystorePass: ${{ secrets.ANDROID_KEYSTORE_PASS }}
+    androidKeyaliasName: ${{ secrets.ANDROID_KEYALIAS_NAME }}
+    androidKeyaliasPass: ${{ secrets.ANDROID_KEYALIAS_PASS }}
+```
+
+You should also set all the Android Keystore options (see below). Refer to
+[this section](/docs/github/deployment/android#3-generate-an-upload-key-and-keystore) for keystore
+setup.
+
+_**required:** `false`_ _**default:** `androidPackage`_
+
+#### androidKeystoreName
+
+Configure the android `keystoreName`. Must be provided if configuring the below keystore options.
+
+For this to take effect, you must enable `Custom Keystore` in your
+[Android Player settings](https://docs.unity3d.com/Manual/class-PlayerSettingsAndroid.html). The
+default build script overrides the other keystore settings with these keystore options.
+
+_**required:** `false`_ _**default:** `""`_
+
+#### androidKeystoreBase64
+
+Configure the base64 contents of the android keystore file. You should get this with
+`base64 $androidKeystoreName`
+
+The contents will be decoded from base64 using
+`echo $androidKeystoreBase64 | base64 --decode > $projectPath/$androidKeystoreName`
+
+It is recommended to use
+[GitHub Secrets](https://docs.github.com/en/actions/reference/encrypted-secrets).
+
+_**required:** `false`_ _**default:** `""`_
+
+#### androidKeystorePass
+
+Configure the android `keystorePass`. Recommended to use GitHub Secrets.
+
+_**required:** `false`_ _**default:** `""`_
+
+#### androidKeyaliasName
+
+Configure the android `keyaliasName`. Recommended to use GitHub Secrets.
+
+_**required:** `false`_ _**default:** `""`_
+
+#### androidKeyaliasPass
+
+Configure the android `keyaliasPass`. Recommended to use GitHub Secrets.
+
+_**required:** `false`_ _**default:** `""`_
+
+#### androidTargetSdkVersion
+
+Configure the android target API level. If used, must be one of
+[Unity's AndroidSdkVersions](https://docs.unity3d.com/ScriptReference/AndroidSdkVersions.html).
+
+_**required:** `false`_ _**default:** `""`_
+
+#### androidSymbolType
+
+Export android symbols alongside the build. Can be set to `none`, `public`, or `debugging`.
+
+_**required:** `false`_ _**default:** `"none"`_
+
+#### sshAgent
+
+SSH Agent path to forward to the container.
+
+This is useful if your manifest has a dependency on a private GitHub repo.
+
+_**required:** `false`_ _**default:** `""`_
+
+#### sshPublicKeysDirectoryPath
+
+SSH directory path to mount in the container on `~/.ssh`. Must be used with `sshAgent`.
+
+It is recommended to have only public keys in this directory, and rely on `sshAgent` to manage
+private keys.
+
+This is useful if your manifest has a dependency on multiple private GitHub repos and you need to
+use multiple SSH deploy keys.
+
+_**required:** `false`_ _**default:** ``_
+
+#### gitPrivateToken
+
+Github private token to pull from github.
+
+This is useful if your manifest has a dependency on a private GitHub repo.
+
+_**required:** `false`_ _**default:** `""`_
+
+#### chownFilesTo
+
+User and optionally group (user or user:group or uid:gid) to give ownership of the resulting build
+artifacts.
+
+_**required:** `false`_ _**default:** `""`_
+
+#### allowDirtyBuild
+
+Allows the branch of the build to be dirty, and still generate the build.
+
+```yaml
+- uses: game-ci/unity-builder@v3
+  with:
+    allowDirtyBuild: true
+```
+
+Note that it is generally bad practice to modify your branch in a CI Pipeline. However there are
+exceptions where this might be needed. (use with care).
+
+_**required:** `false`_ _**default:** `false`_
+
+#### unityLicensingServer
+
+Sets the url to a unity license server for acquiring floating licenses.
+
+_**required:** `false`_ _**default:** `""`_
+
+#### cacheUnityInstallationOnMac
+
+Enables caching the Unity Hub and Editor installation for MacOS runners. This can significantly
+reduce project build times if you have enough available cache on Github Actions.
+
+_**required:** `false`_ _**default:** `false`_
+
+#### unityHubVersionOnMac
+
+Allows pinning the Unity Hub version used on MacOS runners. Should be of format `Major.Minor.Patch`,
+ie `3.4.0`. An empty string represents the latest available version on homebrew.
+
+_**required:** `false`_ _**default:** `""`_
+
+#### dockerWorkspacePath
+
+Allows customizing the build path within the container in case there are hardcoded paths generated
+during the build. For example building an IOS XCode project on Linux and moving to a new path on
+MacOS occasionally leads to broken paths requiring this override to ensure the paths match.
+
+Paths should be of format `/path/to/build`, ie `/tmp/build`. On Windows, leave off the drive letter
+specification. For example `C:\build` becomes `/build`. There should be no trailing slash in the
+path and the path should be absolute. The path will automatically be created within the container if
+it does not exist. It is recommended to use a path that doesn't already exist within the container
+to avoid any conflicts.
+
+_**required:** `false`_ _**default:** `"/github/workspace"`_
+
+## Outputs
+
+Below are outputs that can be accessed by using `${{ steps.myBuildStep.outputs.outputName }}`, where
+`myBuildStep` is the id of the Builder step, and `outputName` is the name of the output.
+
+#### buildVersion
+
+Returns the version that was generated by Builder, following the strategy configured for
+`versioning`.
+
+```yaml
+- uses: game-ci/unity-builder@v3
+  id: myBuildStep
+- run: echo 'Project Version: ${{ steps.myBuildStep.outputs.buildVersion }}'
+```
+
+#### androidVersionCode
+
+Returns the version code that was generated by Builder for Android builds.
+
+```yaml
+- uses: game-ci/unity-builder@v3
+  id: myBuildStep
+- run: echo 'Android Version Code: ${{ steps.myBuildStep.outputs.androidVersionCode }}'
+```
+
+## Private Github repositories
+
+If you use private git repository in your packages/manifest.json, you need to create SSH pub/private
+keys for your project and then add to the `webfactory/ssh-agent`
+
+- Generate public,private key for github's SSH using
+  [this instruction](https://docs.github.com/en/github/authenticating-to-github/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#generating-a-new-ssh-key)
+  and make sure that you you use `git@github.com:USER/PROJECT.git` instead of email for `-C`
+  parameter because we're going to use it as deploy key for a single project and
+  `webfactory/ssh-agent` going to use that for checking which repository this key is related to .
+- Add the public_key to Deploy settings of your private git repository
+  (https://github.com/USER/PROJECT/settings/keys)
+- Add private_key to Github secrets of the project that you want to build
+  (https://github.com/USER/PROJECT/settings/secrets/actions) (key name should be SSH_PRIVATE_KEY )
+- Add github to ssh known hosts :
+
+```yaml
+name: 'Add GitHub to the SSH known hosts file'
+run: |
+  mkdir -p -m 0700 /home/runner/.ssh
+  curl --silent https://api.github.com/meta | jq --raw-output '"github.com "+.ssh_keys[]' >> /home/runner/.ssh/known_hosts
+  chmod 600 /home/runner/.ssh/known_hosts
+```
+
+- Finally, add `webfactory/ssh-agent` to your Github action :
+
+```yaml
+name: Accessing private repos
+runs-on: ubuntu-latest
+steps:
+  - uses: actions/checkout@v2
+  - uses: webfactory/ssh-agent@v0.8.0
+    with:
+      ssh-private-key: ${{ secrets.SSH_PRIVATE_KEY }}
+  - uses: game-ci/unity-builder@v3
+    with:
+      sshAgent: ${{ env.SSH_AUTH_SOCK }}
+```
+
+### Multiple private Github repositories
+
+[GitHub Deploy Keys](https://docs.github.com/en/authentication/connecting-to-github-with-ssh/managing-deploy-keys#deploy-keys)
+are SSH keys that can only be set up on repository level. If you have multiple private repositories
+in your packages/manifest.json, you will need to add a Github Deploy Key for each one, and use the
+`webfactory/ssh-agent` action to manage them and use the right SSH key for each repository.
+
+In order for `webfactory/ssh-agent` to work inside the container, you will need to upload the public
+keys, SSH config and set the git url mirroring configurations in the container. You can do that by
+using `sshPublicKeysDirectoryPath` and setting the `GIT_CONFIG_EXTENSIONS` environment variable:
+
+```yaml
+- uses: webfactory/ssh-agent@v0.8.0
+  with:
+  ssh-private-key: |
+    ${{ secrets.FIRST_KEY }}
+    ${{ secrets.NEXT_KEY }}
+    ${{ secrets.ANOTHER_KEY }}
+
+- name: Prepare SSH config for unity builder
+  run: |
+    mkdir $HOME/.ssh_docker
+    cp $HOME/.ssh/config $HOME/.ssh_docker/
+    cp $HOME/.ssh/key* $HOME/.ssh_docker/
+    cp $HOME/.ssh/known_hosts $HOME/.ssh_docker/
+    sed -i 's/\/home\/runner/\/root/g' $HOME/.ssh_docker/config
+    sudo chown -R root:root $HOME/.ssh_docker
+    GIT_CONFIG_EXTENSIONS=$(git config --list | grep '^url\.')
+    {
+      echo 'GIT_CONFIG_EXTENSIONS<<EOF'
+      echo "$GIT_CONFIG_EXTENSIONS"
+      echo EOF
+    } >> "$GITHUB_ENV"
+  shell: bash
+
+- uses: game-ci/unity-builder@v3
+  with:
+    sshAgent: ${{ env.SSH_AUTH_SOCK }}
+    sshPublicKeysDirectoryPath: ${{ env.HOME }}/.ssh_docker
+```
+
+## UPM authentication using .upmconfig.toml
+
+Unity requires an .upmconfig.toml to exist in the home directory to authenticate and download
+packages from private UPM registries. To create this file, first create the
+`/home/runner/work/_temp/_github_home` directory, and then create the .upmconfig.toml file inside
+that directory. This action must be done before running the game-ci/unity-builder@v2 action.
+
+```yaml
+- name: Create .upmconfig.toml UPM authentication file
+  run: |
+    mkdir /home/runner/work/_temp/_github_home
+    cd /home/runner/work/_temp/_github_home
+    echo "[npmAuth.\"https://upm.example.com\"]" >> .upmconfig.toml
+    echo "alwaysAuth = true" >> .upmconfig.toml
+    echo "token = \"${{ secrets.NPM_TOKEN }}\"" >> .upmconfig.toml
+```
+
+## Complete example
+
+A complete workflow that builds every available platform could look like this:
+
+```yaml
+name: Build project
+
+on: [push, pull_request]
+
+jobs:
+  buildForAllSupportedPlatforms:
+    name: Build for ${{ matrix.targetPlatform }}
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        targetPlatform:
+          - StandaloneOSX # Build a macOS standalone (Intel 64-bit).
+          - StandaloneWindows # Build a Windows standalone.
+          - StandaloneWindows64 # Build a Windows 64-bit standalone.
+          - StandaloneLinux64 # Build a Linux 64-bit standalone.
+          - iOS # Build an iOS player.
+          - Android # Build an Android .apk standalone app.
+          - WebGL # WebGL.
+    steps:
+      - uses: actions/checkout@v3
+        with:
+          fetch-depth: 0
+          lfs: true
+      - uses: actions/cache@v3
+        with:
+          path: Library
+          key: Library-${{ matrix.targetPlatform }}
+          restore-keys: Library-
+      - if: matrix.targetPlatform == 'Android'
+        uses: jlumbroso/free-disk-space@v1.3.0
+      - uses: game-ci/unity-builder@v3
+        env:
+          UNITY_LICENSE: ${{ secrets.UNITY_LICENSE }}
+        with:
+          targetPlatform: ${{ matrix.targetPlatform }}
+      - uses: actions/upload-artifact@v3
+        with:
+          name: Build-${{ matrix.targetPlatform }}
+          path: build/${{ matrix.targetPlatform }}
+```
+
+## Next steps
+
+You can find more workflow examples in
+[Getting Started](/docs/github/getting-started#workflow-examples).
diff --git a/versioned_docs/version-3/03-github/05-returning-a-license.mdx b/versioned_docs/version-3/03-github/05-returning-a-license.mdx
new file mode 100644
index 00000000..08a7b671
--- /dev/null
+++ b/versioned_docs/version-3/03-github/05-returning-a-license.mdx
@@ -0,0 +1,20 @@
+# Returning a license
+
+Manually returning a license is **usually never necessary**, unless when running into an
+_unrecoverable error_ while having a license active.
+
+Also, Unity only allows returning professional licenses.
+
+## Basic setup
+
+You may use [Unity - Return license](https://github.com/marketplace/actions/unity-return-license) to
+return your license and free up a spot towards the maximum number of active licenses.
+
+Add this step to your workflow:
+
+```yaml
+# Return License
+- name: Return license
+  uses: game-ci/unity-return-license@v2
+  if: always()
+```
diff --git a/versioned_docs/version-3/03-github/06-deployment/_category_.yaml b/versioned_docs/version-3/03-github/06-deployment/_category_.yaml
new file mode 100644
index 00000000..f74a60fd
--- /dev/null
+++ b/versioned_docs/version-3/03-github/06-deployment/_category_.yaml
@@ -0,0 +1,5 @@
+---
+position: 6.0
+label: Deployment
+collapsible: true
+collapsed: true
diff --git a/versioned_docs/version-3/03-github/06-deployment/android.mdx b/versioned_docs/version-3/03-github/06-deployment/android.mdx
new file mode 100644
index 00000000..88297d77
--- /dev/null
+++ b/versioned_docs/version-3/03-github/06-deployment/android.mdx
@@ -0,0 +1,252 @@
+# Deploy to Google Play
+
+This guide is intended to help with automating Android builds to upload to the Play Store. If you
+just need to produce an APK, the [unity-builder](https://game.ci/docs/github/builder) action will do
+that. However, if you intend to distribute your game on the Play Store, either for public
+distribution or a beta track, this guide is for you.
+
+### 1. Install Fastlane
+
+[Fastlane](https://docs.fastlane.tools/getting-started/ios/setup/) is a tool that can facilitate
+building and submitting your Android apps to Google, and is the easiest way to deploy your Unity
+project to Android for Play Store distribution.
+
+To configure Fastlane for your GitHub Actions workflow runners, you will need to locally set up a
+`Gemfile` and `Fastfile` within your project. A `Gemfile` specifies what Ruby dependencies are
+needed to set up and run Fastlane (which is written in Ruby), and a `Fastfile` will be how you
+configure your Android deployment settings. We will set up the `Gemfile` now, and the `Fastfile` in
+a later step.
+
+You will need your local machine to have
+[Ruby](https://www.ruby-lang.org/en/documentation/installation/) installed, as well as Bundler. If
+you have Ruby installed but are unsure if you have Bundler, you can run the following to install it:
+
+```bash
+gem install bundler
+```
+
+From there, create a file called `Gemfile` in the root of your git repository with following
+content:
+
+```ruby title="Gemfile"
+source "https://rubygems.org"
+gem "fastlane"
+```
+
+Then run `bundle install`. This will create an additional `Gemfile.lock` file in the root of your
+project.
+
+Commit both `Gemfile` and `Gemfile.lock` to your repo.
+
+### 2. Create a Google Play Service Account
+
+To programmatically access the Google Play Console, you will need a dedicated Google Play service
+account with API access.
+
+Follow the
+["Setup" section of the Fastlane Supply documentation](https://docs.fastlane.tools/actions/supply/)
+to create a service account.
+
+After the last step, it will tell you to test the connection to the Google Play Store, and then add
+your JSON file path to your Appfile. You can do the first step if you would like (you may need to
+run `bundle exec fastlane` instead of just `fastlane`), but don't worry about the Appfile, as we
+will be be creating that in the next step.
+
+Instead, create a Repository Secret in your GitHub repository by going to Settings -> Secrets and
+clicking the "New repository secret" button in the top-right. It should be titled
+`GOOGLE_PLAY_KEY_FILE` and its value should be the plaintext contents of the downloaded JSON file.
+
+### 3. Generate an upload key and keystore
+
+Distributing an app via the Google Play Store requires uploading an unsigned Android App Bundle
+(AAB) file and letting Google codesign your app for you using Play App Signing. In order to do this,
+you need to create an upload signing key, which you will then sign your app with.
+
+In Unity, while Android is your selected build platform, open Player Settings. Under "Publishing
+Settings", click the "Keystore Manager" button to open the keystore manager. Click the "Keystore"
+dropdown, and then "Create New" > "Anywhere" to create a new keystore file. You can select any file
+location, just note where it is.
+
+Fill out all the fields in this form. Both of the password and password confirmation fields (so,
+four password fields total) should contain the same password. Click "Add key" when you're done. In
+Player Settings, confirm that the "Custom Keystore" checkbox is checked, and the correct keystore
+path, keystore password, alias name, and alias password are set. Be sure to commit and push these
+changes to your git repository.
+
+If you would rather use Android Studio to generate an upload key and keystore, you can follow
+[Google's guide](https://developer.android.com/studio/publish/app-signing#generate-key) and then
+manually select that keystore within the Unity Player Settings. It doesn't matter as long as you end
+up with a valid `.keystore` file and Unity is configured to use that custom keystore.
+
+Be sure to keep your `.keystore` file and password handy, as we will be using them in future steps.
+We recommend that you **not** check your `.keystore` file into git, as this can reduce security. If
+your workflow requires developers to be able to manually build the project, we recommend adding the
+`.keystore` file to your `.gitignore` (if you want to keep it in your project directory) and finding
+an alternate way to transfer it between developers, such as a shared password manager that supports
+file uploads.
+
+Next, you will need to add the keystore information to your GitHub repository.
+
+Begin by base64-encoding the contents of your `.keystore` file. On a Linux or MacOS command-line
+prompt, you can use the `base64` command to do so: `base64 user.keystore` (assuming you're in the
+correct working directory and your keystore file is named `user.keystore`). In Windows PowerShell,
+the following command will generate the same results:
+`[convert]::ToBase64String((Get-Content -path "user.keystore" -Encoding byte))`
+
+Add four Repository Secrets in your GitHub repository by going to Settings -> Secrets and clicking
+the "New repository secret" button in the top-right. `ANDROID_KEYSTORE_BASE64` should contain the
+base64'd version of your keystore file's contents, and `ANDROID_KEYSTORE_PASS`,
+`ANDROID_KEYALIAS_NAME`, and `ANDROID_KEYALIAS_PASS` should contain your keystore's password, alias
+name, and alias password respectively. If you followed the instructions above, the keystore password
+and alias password will be the same.
+
+### 4. Manually upload a build to Google Play
+
+In order to automate submission to the Google Play store, Google requires you to have already
+manually uploaded a version of your app to the Google Play Console. You also need to get your app
+out of the "Draft" status if you want to deploy anything but draft releases.
+
+To begin, build your game in Unity. Ensure that the "Build App Bundle (Google Play)" checkbox is
+checked in the Build Settings, and that the keystore from the previous step is selected in the
+Publishing Settings section of the Player Settings. If both of these are correct, your build should
+produce an `.aab` file that has been signed with your upload key.
+
+In the Google Play Console, select "Internal Testing" from the left-side menu (or an alternate track
+if you want to do a public production or beta released). Click "Create new release", and drag in an
+AAB you've manually built in Unity (or an existing GitHub Actions workflow). Fill out the rest of
+the required fields, then click Save.
+
+Before you can programmatically deploy any release that is not a "Draft" release, you'll need to
+manually submit your app for review at least once to get it out of "Draft" status. Depending on
+where you are in the game production lifecycle, you may not want to this during initial setup, but
+be aware this is something you will need to do before you can use GameCI to release new live updates
+to a production build.
+
+### 5. Set up Fastlane
+
+At this point, your Google Play Console app listing should be ready to accept programmatic uploads,
+but you still need to configure Fastlane. Within your project directory, create a directory called
+`fastlane`, and then create two files within that directory, `Appfile` and `Fastfile`.
+
+```ruby title="fastlane/Appfile"
+for_platform :android do
+  package_name(ENV["ANDROID_PACKAGE_NAME"])
+  json_key_file(ENV["GOOGLE_PLAY_KEY_FILE_PATH"])
+end
+```
+
+```ruby title="fastlane/Fastfile"
+platform :android do
+  desc "Upload a new Android version to the production Google Play Store"
+  lane :production do
+    upload_to_play_store(track: 'production', release_status: 'completed', aab: "#{ENV['ANDROID_BUILD_FILE_PATH']}")
+  end
+
+  desc "Upload a new Android internal version to Google Play"
+  lane :internal do
+    upload_to_play_store(track: 'internal', release_status: 'completed', aab: "#{ENV['ANDROID_BUILD_FILE_PATH']}")
+  end
+end
+```
+
+If you would like to upload to other tracks (namely, `alpha` or `beta`), you can create additional
+lanes that look the same as the `:production` and `:internal` lanes except for the name and `track`
+parameter. Additionally, if you want to create draft releases (which will be necessary until you've
+manually pushed at least one build through the manual submission process), you will want to switch
+`release_status` from `completed` to `draft`.
+
+### 6. Add jobs to your GitHub workflow
+
+The following workflow establishes two jobs. The first builds your game into an AAB file, and the
+second uploads that generated bundle to the Play Store.
+
+```yaml title=".github/workflows/main.yml"
+jobs:
+  buildForAndroidPlatform:
+    name: Build For Android Platform
+    runs-on: ubuntu-latest
+    steps:
+      - uses: jlumbroso/free-disk-space@v1.2.0
+      - uses: actions/checkout@v3
+      - uses: actions/cache@v3
+        with:
+          path: Library
+          key: Library-Android
+      - uses: game-ci/unity-builder@v3
+        with:
+          targetPlatform: Android
+          androidExportType: androidAppBundle
+          androidKeystoreName: user # This file won't exist, but this property needs to exist.
+          androidKeystoreBase64: ${{ secrets.ANDROID_KEYSTORE_BASE64 }}
+          androidKeystorePass: ${{ secrets.ANDROID_KEYSTORE_PASS }}
+          androidKeyaliasName: ${{ secrets.ANDROID_KEYALIAS_NAME }}
+          androidKeyaliasPass: ${{ secrets.ANDROID_KEYALIAS_PASS }}
+          androidTargetSdkVersion: AndroidApiLevel31
+      - uses: actions/upload-artifact@v3
+        with:
+          name: build-Android
+          path: build/Android
+
+  releaseToGooglePlay:
+    name: Release to the Google Play Store
+    runs-on: ubuntu-latest
+    needs: buildForAndroidPlatform
+    env:
+      GOOGLE_PLAY_KEY_FILE: ${{ secrets.GOOGLE_PLAY_KEY_FILE }}
+      GOOGLE_PLAY_KEY_FILE_PATH:
+        ${{ format('{0}/fastlane/google-fastlane.json', github.workspace) }}
+      ANDROID_BUILD_FILE_PATH: ${{ format('{0}/build/Android/Android.aab', github.workspace) }}
+      ANDROID_PACKAGE_NAME: ${{ secrets.ANDROID_PACKAGE_NAME }}
+    steps:
+      - name: Checkout Repository
+        uses: actions/checkout@v3
+      - name: Download Android Artifact
+        uses: actions/download-artifact@v2
+        with:
+          name: build-Android
+          path: build/Android
+      - name: Add Authentication
+        run: echo "$GOOGLE_PLAY_KEY_FILE" > $GOOGLE_PLAY_KEY_FILE_PATH
+      - name: Set up Fastlane
+        uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: 2.7.2
+          bundler-cache: true
+      - name: Upload to Google Play Internal
+        uses: maierj/fastlane-action@v2.0.1
+        with:
+          lane: 'android internal' # Change to upload to a different lane
+      - name: Cleanup to avoid storage limit
+        if: always()
+        uses: geekyeggo/delete-artifact@v1
+        with:
+          name: build-Android
+```
+
+### 7. Add secrets to your Github repo
+
+On your project's GitHub repo page, add a number of Repository Secrets by going to Settings ->
+Secrets and clicking the "New repository secret" button in the top-right.
+
+- **ANDROID_KEYSTORE_BASE64** : Base64 of your keystore, generated in step 3
+- **ANDROID_KEYSTORE_PASS**: Password for your keystore
+- **ANDROID_KEYALIAS_NAME**: Name of the alias in your keystore
+- **ANDROID_KEYALIAS_PASS**: Password for the alias in your keystore
+- **GOOGLE_PLAY_KEY_FILE**: The contents of the Google Account Service .json file from step 2
+- **ANDROID_PACKAGE_NAME**: Your application package name (e.g com.company.application)
+
+If you get build failures around the keystore being invalid, _please_ confirm that your keystore
+base64, alias, and two passwords are correct, as that is a common source of failure. If you want to
+double-check your keystore has been correctly encoded as valid base64, you can locally recreate your
+keystore by manually running:
+
+```bash
+cat [keystore file] | base64 --decode > user.keystore
+```
+
+swapping in the name of a text file containing the base64 value. This will create a new keystore
+that you can attempt to manually build from in Unity. On Windows, this would be:
+
+```powershell
+[Text.Encoding]::Utf8.GetString([Convert]::FromBase64String('base 64 value')) | Out-File -FilePath .\user.keystore
+```
diff --git a/versioned_docs/version-3/03-github/06-deployment/ios.mdx b/versioned_docs/version-3/03-github/06-deployment/ios.mdx
new file mode 100644
index 00000000..b791026a
--- /dev/null
+++ b/versioned_docs/version-3/03-github/06-deployment/ios.mdx
@@ -0,0 +1,523 @@
+# Deploy to the App Store
+
+This guide is intended to help with automating iOS builds and uploads to the App Store. This guide
+assumes that you already have experience with
+[using Xcode for distribution](https://developer.apple.com/documentation/xcode/preparing-your-app-for-distribution).
+It is important to be familiar with the manual process, as automating this process can be
+complicated.
+
+> -- **Note:** Make sure you do all these steps carefully.
+>
+> -- **Note:** If you use GitHub Actions and fastlane to generate your certificates, you will not
+> need a Mac environment, but a Mac is still recommended for debugging any issues with this
+> workflow.
+
+### Conceptual overview
+
+This guide walks you through two separate processes: setting up codesigning for your game, and then
+building it.
+
+When you build your Unity project for iOS, Unity will produce an Xcode project that needs to be
+built using Xcode on a Mac. In order to upload your app to the App Store, TestFlight, or a
+third-party beta distribution service, you will first need to build it in Xcode and then code-sign
+it.
+
+We will be using a tool called [fastlane](https://docs.fastlane.tools/getting-started/ios/setup/) to
+facilitate building, codesigning, and uploading your iOS build.
+
+`fastlane` will manage building your game in Xcode and uploading it to Apple. The
+[fastlane match](https://docs.fastlane.tools/actions/match/) tool will generate and manage your
+code-signing identities and certificates, communicating with Apple via API and then storing your
+codesigning identities and certificates securely in a private git repo.
+
+### 1. Install fastlane
+
+To configure fastlane for your GitHub Actions workflow runners, you will need to locally set up a
+`Gemfile` and `Fastfile` within your project. A `Gemfile` specifies what Ruby dependencies are
+needed to set up and run fastlane (which is written in Ruby), and a `Fastfile` will be how you
+configure your iOS build settings. We will set up the `Gemfile` now, and the `Fastfile` in a later
+step.
+
+You will need your local machine to have
+[Ruby](https://www.ruby-lang.org/en/documentation/installation/) installed, as well as Bundler. If
+you have Ruby installed but are unsure if you have Bundler, you can run the following to install it:
+
+```bash
+gem install bundler
+```
+
+From there, create a file called `Gemfile` in the root of your git repository with following
+content:
+
+```ruby title="Gemfile"
+source "https://rubygems.org"
+gem "fastlane"
+gem 'fastlane-plugin-github_action', git: "https://github.com/joshdholtz/fastlane-plugin-github_action" # The published gem is missing necessary changes, so we need to link directly to the git repo
+```
+
+If you prefer to manually generate certificates using Match from the command-line on a local Mac
+instead of handling everything through GitHub Actions, you can omit the last
+`fastlane-plugin-github-action` line.
+
+Run `bundle install`. This will create an additional `Gemfile.lock` file in the root of your
+project.
+
+Commit both `Gemfile` and `Gemfile.lock` to your repo.
+
+> -- **Note:** Depending on your local OS you might need to run
+> `bundle lock --add-platform x86_64-linux` and `bundle lock --add-platform x86_64-darwin-19`
+> commands in order to add the required platforms to `Gemfile.lock` file. Be sure to commit the
+> `Gemfile.lock` after running these commands.
+
+### 2. Generate an App Store Connect API Key
+
+In order for fastlane match to fetch and validate your codesigning certificates, it needs to
+authenticate you with Apple. All Apple IDs now require two-factor authentication to be enabled,
+which means you need to manually enter a 2FA code when logging in. This is fine if you're running
+match locally on your own machine, but is a problem on an automated CI system.
+
+To work around this, you will need to generate an App Store Connect API key, which match can use to
+authenticate you with Apple without manual 2FA input while running on CI.
+
+While not required, it is recommended you use a separate Apple ID just for CI purposes. Create one
+if you haven't already.
+
+Next, go to https://appstoreconnect.apple.com/access/users and log in. Go to the "Keys" tab and
+click the plus sign (+) to generate a new set of keys. Enter a name and select "Developer" access.
+Once it's been generated, click the "Download API key" link, which will download a file. Note you
+can only download this once.
+
+Create three new Repository Secrets in your project GitHub repo by going to Settings -> Secrets and
+clicking the "New repository secret" button in the top-right. Use the following names and values:
+
+- **APPSTORE_KEY_ID** should contain the "Key ID" from the table row
+- **APPSTORE_ISSUER_ID** is your issuer ID from the top of the page
+- **APPSTORE_P8** is the entire contents of the `.p8` file you downloaded, starting with
+  `-----BEGIN PRIVATE KEY-----` and ending with `-----END PRIVATE KEY-----`
+
+### 3. Prepare to use fastlane match
+
+The Match setup we are configuring uses a common workflow that is likely to be a good fit for many
+GameCI users. However, there are a number of different ways you can set up Match, and we recommend
+reading the Match [documentation](https://docs.fastlane.tools/actions/match/) and
+[codesigning guide](https://codesigning.guide) in their entirety.
+
+First, create a private GitHub repository to store your certificates.
+
+If your Apple Developer account is messy and has lots of invalid, expired, or Xcode-managed profiles
+and certificates, you may **optionally** want to use Match to initially clean out your old developer
+portal by running `bundle exec fastlane match development` and
+`bundle exec fastlane match production` on a local Mac. **This will delete Apple codesigning
+identities and certificates and may break any existing workflows. It is NOT recommended if your
+project shares an Apple Developer account with other projects or teams at your company.**
+
+### 4. Manage codesigning with GitHub Actions
+
+This section will configure GitHub Actions to manually generate your code-signing identities and
+certificates and store them in your private git repo. If you prefer to manually manage your
+certificates from the command-line, skip this section.
+
+Within your project directory, create a directory called `fastlane`, and then create a file in that
+directory called `Fastfile`.
+
+```ruby title="fastlane/Fastfile"
+
+org, repo = (ENV["GITHUB_REPOSITORY"]||"").split("/")
+match_org, match_repo = (ENV["MATCH_REPOSITORY"]||"").split("/")
+
+platform :ios do
+  lane :init_ci do
+    setup_ci
+    github_action(
+      api_token: ENV["GH_PAT"],
+      org: org,
+      repo: repo,
+      match_org: match_org,
+      match_repo: match_repo,
+      writable_deploy_key: true
+    )
+  end
+
+  desc "Sync codesigning certificates"
+  lane :sync_certificates do
+    app_store_connect_api_key(
+      key_id: ENV["APPSTORE_KEY_ID"],
+      issuer_id: ENV["APPSTORE_ISSUER_ID"],
+      key_content: ENV['APPSTORE_P8']
+    )
+
+    match(
+      type: "appstore",
+      storage_mode: "git",
+      git_url: "git@github.com:#{match_org}/#{match_repo}.git",
+      app_identifier: ENV["IOS_BUNDLE_ID"]
+    )
+  end
+
+end
+```
+
+When fastlane initially sets up your repo and certificates, it will generate a deploy token that
+allows programmatic write access to your Match repo, and store that token as a Repository Secret in
+your project repo. In order for our script to do that, you will need to first generate a GitHub
+Personal Access Token. Go to https://github.com/settings/tokens, click "Generate new token". It
+needs all "repo" permissions. Give it a suitable name, as well as choosing if you want your token to
+expire. After doing this and clicking "Generate token", GitHub will show you your token.
+
+In your project repo, add a Repository Secrets by going to Settings -> Secrets and clicking the "New
+repository secret" button in the top-right. Call it `GH_PAT`, and set the value to the personal
+access token you just generated.
+
+Create two more Repository Secrets. One should be called `MATCH_REPOSITORY` and contain the private
+GitHub repository you've created to use with fastlane match, in the format
+`organization/repository`. The second should be called `MATCH_PASSWORD`, and contain a password to
+encrypt the Match repo. It's recommended you use a team password manager or similar shared secure
+keystore to both generate and store this password.
+
+Next, create the following two GitHub Actions workflows.
+
+```yaml title=".github/workflows/ios_setup.yml"
+name: iOS One-Time Setup
+
+on: workflow_dispatch
+
+jobs:
+  setup:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+      - uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: 2.6
+          bundler-cache: true
+
+      - name: Build iOS
+        shell: bash
+        run: |
+          bundle exec fastlane ios init_ci
+        env:
+          APPSTORE_ISSUER_ID: ${{ secrets.APPSTORE_ISSUER_ID }}
+          APPSTORE_KEY_ID: ${{ secrets.APPSTORE_KEY_ID }}
+          APPSTORE_P8: ${{ secrets.APPSTORE_P8 }}
+
+          GH_PAT: ${{ secrets.GH_PAT }}
+          GITHUB_REPOSITORY: ${{ env.GITHUB_REPOSITORY }}
+          MATCH_REPOSITORY: ${{ secrets.MATCH_REPOSITORY }}
+```
+
+```yaml title=".github/workflows/generate_certs.yml"
+name: Generate iOS Certs
+
+on:
+  workflow_run:
+    workflows: ['iOS One-Time Setup']
+    types:
+      - completed
+  workflow_dispatch:
+
+jobs:
+  generate_certs:
+    runs-on: macos-latest
+    steps:
+      - uses: actions/checkout@v2
+      - uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: 2.6
+          bundler-cache: true
+
+      - name: Build iOS
+        shell: bash
+        run: |
+          eval "$(ssh-agent -s)"
+          ssh-add - <<< "${MATCH_DEPLOY_KEY}"
+          bundle exec fastlane ios sync_certificates
+        env:
+          APPSTORE_ISSUER_ID: ${{ secrets.APPSTORE_ISSUER_ID }}
+          APPSTORE_KEY_ID: ${{ secrets.APPSTORE_KEY_ID }}
+          APPSTORE_P8: ${{ secrets.APPSTORE_P8 }}
+
+          IOS_BUNDLE_ID: ${{ secrets.IOS_BUNDLE_ID }}
+
+          GH_PAT: ${{ secrets.GH_PAT }}
+          GITHUB_REPOSITORY: ${{ env.GITHUB_REPOSITORY }}
+          MATCH_REPOSITORY: ${{ secrets.MATCH_REPOSITORY }}
+          MATCH_DEPLOY_KEY: ${{ secrets.MATCH_DEPLOY_KEY }}
+          MATCH_PASSWORD: ${{ secrets.MATCH_PASSWORD }}
+```
+
+The first workflow will set up your Match repository. It creates a deploy key in that repo, and
+stores it in your main repo, so that future GitHub Actions are capable of programmatically pushing
+changes to that git repo.
+
+The second one fetches your certificates with Apple, and stores any updates in your private Match
+git repo. This will run automatically after you run the first workflow, but it also can be manually
+re-run when your initial certificates expire a year or two after generation.
+
+Go to the "Actions" tab in your GitHub repository, and manually run the "iOS One-Time Setup" action
+by selecting it from the list on the left, clicking the "Run Workflow" button, and then clicking the
+next "Run Workflow" button after confirming the branch is correct. This will run both of those two
+workflows, configuring your Match git repository and then generating certificates with Apple.
+
+> -- **Note:** If `Generate iOS Certs` causes an `Unknown platform` issue, go into the
+> `Gemfile.lock` file and under `PLATFORMS` delete any lines that are not `x86_64-darwin-19` or
+> `x86_64-linux`. Don't forget to commit and push the file before running the action again.
+
+### 4b. Manage codesigning manually on your Mac
+
+If you followed the previous set of instructions in step 4, skip to the next section. If you would
+prefer to manually manage your certificates from the command-line instead of using Match via GitHub
+Actions, do the following.
+
+From the command-line on your Mac, run the following to generate new Development and Distribution
+certificates. It will ask you for the Apple ID and password of your new shared Apple ID, the URL of
+the git repository you have just created, and a password to encrypt the contents of the git repo.
+You will need to use this password later; it's recommended you use a team-wide password manager or
+similar shared secure keystore to both generate and store this password.
+
+```bash
+bundle exec fastlane match development
+bundle exec fastlane match appstore
+```
+
+### 5. Configure fastlane to build
+
+At this point, you will have a private git repository that contains new valid codesigning identities
+and certificates. From here, you need to configure fastlane to know how to build your Xcode project.
+Create a new file within the `fastlane` folder called `Appfile`, and either create or replace the
+contents of the `Fastfile` you may have created in a previous step.
+
+```ruby title="fastlane/Appfile"
+for_platform :ios do
+  app_identifier(ENV['IOS_BUNDLE_ID'])
+
+  apple_dev_portal_id(ENV['APPLE_DEVELOPER_EMAIL'])
+  itunes_connect_id(ENV['APPLE_CONNECT_EMAIL'])
+
+  team_id(ENV['APPLE_TEAM_ID'])
+  itc_team_id(ENV['APPLE_TEAM_ID'])
+end
+```
+
+```ruby title="fastlane/Fastfile"
+org, repo = (ENV["GITHUB_REPOSITORY"]||"").split("/")
+match_org, match_repo = (ENV["MATCH_REPOSITORY"]||"").split("/")
+
+platform :ios do
+  lane :init_ci do
+    github_action(
+      api_token: ENV["GH_PAT"],
+      org: org,
+      repo: repo,
+      match_org: match_org,
+      match_repo: match_repo,
+      writable_deploy_key: true
+    )
+  end
+
+  desc "Sync codesigning certificates"
+  lane :sync_certificates do
+    app_store_connect_api_key(
+      key_id: ENV["APPSTORE_KEY_ID"],
+      issuer_id: ENV["APPSTORE_ISSUER_ID"],
+      key_content: ENV['APPSTORE_P8']
+    )
+
+    match(
+      type: "appstore",
+      storage_mode: "git",
+      git_url: "git@github.com:#{match_org}/#{match_repo}.git",
+      app_identifier: ENV["IOS_BUNDLE_ID"]
+    )
+  end
+
+  desc "Deliver a new Release build to the App Store"
+  lane :release do
+    build
+    upload_to_app_store
+  end
+
+  desc "Deliver a new Beta build to Apple TestFlight"
+  lane :beta do
+    # Missing Export Compliance can also be set through Deliverfile
+    update_info_plist(
+      xcodeproj: "#{ENV['IOS_BUILD_PATH']}/iOS/Unity-iPhone.xcodeproj",
+      plist_path: 'Info.plist',
+      block: proc do |plist|
+        plist['ITSAppUsesNonExemptEncryption'] = false
+      end
+    )
+    build
+    upload_to_testflight(skip_waiting_for_build_processing: true)
+  end
+
+  desc "Create .ipa"
+  lane :build do
+    setup_ci
+
+    sync_certificates
+
+    # Unity has specific requirements around codesigning that we have to handle
+    # See https://github.com/fastlane/fastlane/discussions/17458 for context
+    update_code_signing_settings(
+      use_automatic_signing: true,
+      path: "#{ENV['IOS_BUILD_PATH']}/iOS/Unity-iPhone.xcodeproj"
+    )
+
+    update_code_signing_settings(
+      use_automatic_signing: false,
+      team_id: ENV["sigh_#{ENV['IOS_BUNDLE_ID']}_appstore_team-id"],
+      code_sign_identity: 'iPhone Distribution',
+      targets: 'Unity-iPhone',
+      path: "#{ENV['IOS_BUILD_PATH']}/iOS/Unity-iPhone.xcodeproj",
+      profile_name: ENV["sigh_#{ENV['IOS_BUNDLE_ID']}_appstore_profile-name"],
+      profile_uuid: ENV["sigh_#{ENV['IOS_BUNDLE_ID']}_appstore"]
+    )
+
+    build_app( #alias: gym
+      project: "#{ENV['IOS_BUILD_PATH']}/iOS/Unity-iPhone.xcodeproj",
+      scheme: 'Unity-iPhone',
+      xcargs: '-allowProvisioningUpdates'
+    )
+  end
+
+end
+```
+
+> -- **Note:** If you add libraries that need `Podfile` (e.g. Firebase) to your project, add this
+> line to the beginning of your build step (the block of code starting with `lane :build do`):
+
+```ruby
+    cocoapods(
+      clean_install: true,
+      podfile: "#{ENV['IOS_BUILD_PATH']}/iOS/"
+    )
+```
+
+This will install pods and generate the `xcworkspace` for you.
+
+Then change the [`build_app`](http://docs.fastlane.tools/actions/build_app/#build_app) (alias:
+[`gym`](https://docs.fastlane.tools/actions/gym/)) step at the end of this build phase to use the
+new `xcworkspace` instead of the old `xcodeproj`:
+
+```ruby
+    build_app( #alias: gym
+      workspace: "#{ENV['IOS_BUILD_PATH']}/iOS/Unity-iPhone.xcworkspace",
+      scheme: 'Unity-iPhone',
+      xcargs: '-allowProvisioningUpdates'
+    )
+```
+
+### 6. Add jobs to your GitHub Actions workflow
+
+Building for iOS is a two-step build process. When Unity builds your project for iOS, it generates
+an Xcode project, which then must be built and code-signed in Xcode via fastlane.
+
+This workflow builds your app and submits it to Apple for App Store release. If you want to submit
+your app for TestFlight distribution, you can create a job that is identical except it runs
+`bundle exec fastlane ios beta` instead of `bundle exec fastlane ios release` during the "Fix File
+Permissions and Run fastlane" step. You can build your iOS app without uploading it (e.g. to confirm
+it builds successfully, or as a preparation step before uploading to an alternative distribution
+service) by instead running `bundle exec fastlane ios build`.
+
+Please note that Apple will aggressively rate-limit you if you try to upload builds too frequently.
+We recommend you configure any workflow that submits to the App Store or TestFlight to be manually
+triggered, or otherwise make sure it won't automatically run more than a few times a day.
+
+```yaml title=".github/workflows/main.yml"
+jobs:
+  buildForiOSPlatform:
+    name: Build for iOS
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+
+      - uses: actions/cache@v2
+        with:
+          path: Library
+          key: Library-iOS
+
+      - uses: game-ci/unity-builder@v3
+        with:
+          targetPlatform: iOS
+
+      - uses: actions/upload-artifact@v2
+        with:
+          name: build-iOS
+          path: build/iOS
+
+  releaseToAppStore:
+    name: Release to the App Store
+    runs-on: macos-latest
+    needs: buildForiOSPlatform
+    steps:
+      - name: Checkout Repository
+        uses: actions/checkout@v2
+
+      - name: Download iOS Artifact
+        uses: actions/download-artifact@v2
+        with:
+          name: build-iOS
+          path: build/iOS
+
+      - name: Fix File Permissions and Run fastlane
+        env:
+          APPLE_CONNECT_EMAIL: ${{ secrets.APPLE_CONNECT_EMAIL }}
+          APPLE_DEVELOPER_EMAIL: ${{ secrets.APPLE_DEVELOPER_EMAIL }}
+          APPLE_TEAM_ID: ${{ secrets.APPLE_TEAM_ID }}
+
+          MATCH_REPOSITORY: ${{ secrets.MATCH_REPOSITORY }}
+          MATCH_DEPLOY_KEY: ${{ secrets.MATCH_DEPLOY_KEY }}
+          MATCH_PASSWORD: ${{ secrets.MATCH_PASSWORD }}
+
+          APPSTORE_ISSUER_ID: ${{ secrets.APPSTORE_ISSUER_ID }}
+          APPSTORE_KEY_ID: ${{ secrets.APPSTORE_KEY_ID }}
+          APPSTORE_P8: ${{ secrets.APPSTORE_P8 }}
+
+          IOS_BUILD_PATH: ${{ format('{0}/build/iOS', github.workspace) }}
+          IOS_BUNDLE_ID: com.company.application # Change it to match your Unity bundle id
+          PROJECT_NAME: Your Project Name # Change it to match your project's name
+        run: |
+          eval "$(ssh-agent -s)"
+          ssh-add - <<< "${MATCH_DEPLOY_KEY}"
+          find $IOS_BUILD_PATH -type f -name "**.sh" -exec chmod +x {} \;
+          bundle install
+          bundle exec fastlane ios release
+
+      - name: Cleanup to avoid storage limit
+        if: always()
+        uses: geekyeggo/delete-artifact@v1
+        with:
+          name: build-iOS
+```
+
+### 7. Add secrets to your GitHub repo
+
+On your project's GitHub repo page, add a number of Repository Secrets by going to Settings ->
+Secrets and clicking the "New repository secret" button in the top-right.
+
+- **APPLE_CONNECT_EMAIL**: Apple Connect email (if using our recommendation to create a single
+  shared developer Apple ID for fastlane match, this will be the same as `APPLE_DEVELOPER_EMAIL`)
+- **APPLE_DEVELOPER_EMAIL**: Your Apple ID
+- **APPLE_TEAM_ID**: Team Id from your
+  [Apple Developer Account - Membership Details](https://developer.apple.com/account/#/membership/)
+
+### 8. Confirming your Unity and App Store Connect settings
+
+At this point, if you have previously set up your app for manual iOS builds and TestFlight/App Store
+distribution, your GitHub Actions workflow will likely complete successfully. If that is not the
+case, there are a few more steps to finish setup.
+
+In Unity, you will need to ensure that your
+[application icon(s)](https://docs.unity3d.com/Manual/class-PlayerSettingsiOS.html#icon) are set, as
+applications without the correct icons will generate an error while uploading to TestFlight.
+Additionally, set your Bundle Identifier and Signing Team ID in the
+[iOS Player settings - Identification settings](https://docs.unity3d.com/Manual/class-PlayerSettingsiOS.html#Identification).
+The bundle identifier needs to be the same as you have set for the `IOS_BUNDLE_ID` repository
+secret. If you don't know your Signing Team ID, you can find it by going to
+https://developer.apple.com/account/#!/membership while logged in, and it will be the "Team ID"
+listed.
+
+In order to upload a build to Apple, an entry for your app needs to exist in your team's
+[App Store Connect](https://appstoreconnect.apple.com/). From the App Store Connect homepage, select
+"My Apps", and create or confirm the existence of an App with the same bundle identifier you are
+using in your Unity build settings and the `IOS_BUNDLE_ID` GitHub repository secret.
diff --git a/versioned_docs/version-3/03-github/06-deployment/steam.mdx b/versioned_docs/version-3/03-github/06-deployment/steam.mdx
new file mode 100644
index 00000000..a5a95049
--- /dev/null
+++ b/versioned_docs/version-3/03-github/06-deployment/steam.mdx
@@ -0,0 +1,156 @@
+# Deploy to Steam
+
+This page assumes you are registered as a [partner](https://partner.steamgames.com/) with Steam and
+that you are familiar with
+[using SteamPipe to upload your builds to Steam](https://partner.steamgames.com/doc/sdk/uploading).
+
+### 1. Create a Steam Build Account
+
+Create a specialised builder account that only has access to `Edit App Metadata` and
+`Publish App Changes To Steam`.
+
+See [the docs](https://partner.steamgames.com/doc/sdk/uploading#Build_Account).
+
+### 2. Add jobs to main.yml
+
+```yaml title=".github/workflows/main.yml"
+jobs:
+  buildForWindowsAndLinux:
+    name: Build for ${{ matrix.targetPlatform }}
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        targetPlatform:
+          - StandaloneWindows64 # Build a Windows 64-bit standalone.
+          - StandaloneLinux64 # Build a Linux 64-bit standalone.
+    outputs:
+      buildVersion: ${{ steps.build.outputs.buildVersion }}
+    steps:
+      - uses: actions/checkout@v3
+        with:
+          fetch-depth: 0
+          lfs: true
+      - uses: actions/cache@v3
+        with:
+          path: Library
+          key:
+            Library-${{ matrix.targetPlatform }}-${{ hashFiles('Assets/**', 'Packages/**',
+            'ProjectSettings/**') }}
+          restore-keys: |
+            Library-${{ matrix.targetPlatform }}-
+            Library-
+      - uses: game-ci/unity-builder@v3
+        id: build
+        env:
+          UNITY_LICENSE: ${{ secrets.UNITY_LICENSE }}
+        with:
+          targetPlatform: ${{ matrix.targetPlatform }}
+          versioning: Semantic
+      - uses: actions/upload-artifact@v3
+        with:
+          name: Build-${{ matrix.targetPlatform }}
+          path: build/${{ matrix.targetPlatform }}
+  deployToSteam:
+    needs: [buildForWindowsAndLinux]
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout Repository
+        uses: actions/checkout@v3
+        with:
+          fetch-depth: 0
+      - name: Download StandaloneWindows64 Artifact
+        uses: actions/download-artifact@v3
+        with:
+          name: Build-StandaloneWindows64
+          path: build/StandaloneWindows64
+      - name: Download StandaloneLinux64 Artifact
+        uses: actions/download-artifact@v3
+        with:
+          name: Build-StandaloneLinux64
+          path: build/StandaloneLinux64
+      - uses: game-ci/steam-deploy@v3
+        with:
+          username: ${{ secrets.STEAM_USERNAME }}
+          configVdf: ${{ secrets.STEAM_CONFIG_VDF}}
+          appId: ${{ secrets.STEAM_APP_ID }}
+          buildDescription: v${{ needs.buildForWindowsAndLinux.outputs.buildVersion }}
+          rootPath: build
+          depot1Path: StandaloneWindows64
+          depot2Path: StandaloneLinux64
+          releaseBranch: prerelease
+```
+
+### 3. Add GitHub Secrets
+
+- **STEAM_USERNAME**: The username of the Steam Build Account that you created in step 1.
+- **STEAM_CONFIG_VDF**: See the step "Setup Steam Authentication" below.
+- **STEAM_APP_ID**: The identifier of your app on steam. You can find it on your
+  [dashboard](https://partner.steamgames.com/dashboard).
+
+### 4. Setup Steam Authentication
+
+Deploying to Steam requires using Multi-Factor Authentication (MFA) through Steam Guard. This means
+that simply using username and password isn't enough to authenticate with Steam. However, it is
+possible to go through the MFA process only once by following these steps:
+
+1. Install [Valve's offical steamcmd](https://partner.steamgames.com/doc/sdk/uploading#1) on your
+   local machine. All following steps will also be done on your local machine.
+1. Try to login with `steamcmd +login <username> <password> +quit`, which may prompt for the MFA
+   code. If so, type in the MFA code that was emailed to your builder account's email address.
+1. Validate that the MFA process is complete by running `steamcmd +login <username> +quit` again. It
+   should not ask for the MFA code again.
+1. The folder from which you run `steamcmd` will now contain an updated `config/config.vdf` file.
+   Use `cat config/config.vdf | base64 > config_base64.txt` on _Linux_ to encode the file, if you
+   are a on _Windows_ device, use
+   `certutil -encode -f .\config\config.vdf tmp.b64 && findstr /v /c:- tmp.b64 > config_base64.txt`.
+   Copy the contents of `config_base64.txt` to a GitHub Secret `STEAM_CONFIG_VDF`.
+1. `If:` when running the action you recieve another MFA code via email, run
+   `steamcmd +set_steam_guard_code <code>` on your local machine and repeat the `config.vdf`
+   encoding and replace secret `STEAM_CONFIG_VDF` with its contents.
+
+If your builder account uses MFA through the Steam Guard App, the `steam-deploy` app can use a TOTP
+instead of the above configuration. Generating a TOTP is outside the scope of this guide, as it is
+simpler to follow the above steps.
+
+### 5. Additional Configuration
+
+You can configure these to better match your use case.
+
+#### totp
+
+Deploys to Steam using a TOTP. If this is passed, `configVdf` is not required.
+
+#### buildDescription
+
+The identifier for this specific build, which helps you identify it in steam.
+
+It is recommended to use the semantic version of the build for this.
+
+#### rootPath
+
+The root path to your builds. This is the base of which depots will search your files.
+
+#### depot[X]Path
+
+Where X is any number between 1 and 9 (inclusive both).
+
+The relative path following your root path for the files to be included in this depot.
+
+If your appId is 125000 then the depots 125001 ... 125009 will be assumed.
+
+#### firstDepotIdOverride
+
+You can use this to override the ID of the first depot in case the IDs do not start as described in
+depot[X]Path (e.g. for DLCs).
+
+If your firstDepotId is 125000 then, regardless of the used appId, the depots 125000 ... 125008 will
+be assumed.
+
+#### releaseBranch
+
+The branch within steam that this build will be automatically put live on.
+
+Note that the `default` branch
+[has been observed to not work](https://github.com/game-ci/steam-deploy/issues/19) as a release
+branch, presumably because it is potentially dangerous.
diff --git a/versioned_docs/version-3/03-github/_category_.yaml b/versioned_docs/version-3/03-github/_category_.yaml
new file mode 100644
index 00000000..0ac25ea3
--- /dev/null
+++ b/versioned_docs/version-3/03-github/_category_.yaml
@@ -0,0 +1,5 @@
+---
+position: 3.0
+label: GitHub (Default)
+collapsible: true
+collapsed: true
diff --git a/versioned_docs/version-3/05-gitlab/01-getting-started.mdx b/versioned_docs/version-3/05-gitlab/01-getting-started.mdx
new file mode 100644
index 00000000..7277fda5
--- /dev/null
+++ b/versioned_docs/version-3/05-gitlab/01-getting-started.mdx
@@ -0,0 +1,76 @@
+import Video from '../../../src/components/video/video';
+
+# Getting started
+
+This guide will demonstrate how to setup build and test automation for your Unity project hosted on
+gitlab using gitlab-ci.
+
+## Overall steps
+
+1. Understand how [gitlab-ci](https://docs.gitlab.com/ce/ci/) works.
+2. Configure a license for Unity.
+3. Add build scripts and integrations in your Unity project
+4. Set up a gitlab-ci pipeline for your project.
+5. Result: Accept merge requests with more confidence.
+
+## First time using Gitlab CI?
+
+Read the official documentation about
+[Getting started with GitLab CI/CD](https://docs.gitlab.com/ce/ci/quick_start/).
+
+Any subsequent steps assume you have read the above.
+
+## Supported versions
+
+The [unity3d-gitlab-ci-example project](https://gitlab.com/game-ci/unity3d-gitlab-ci-example/) is
+based on [unity3d](https://github.com/game-ci/docker/) docker images from
+[game-ci](https://github.com/game-ci). Any version in the
+[docker hub `unityci/editor` tags list](https://hub.docker.com/r/unityci/editor/tags) can be used to
+test and build projects.
+
+It's generally considered good practice to use the same Unity version for your CI/CD setup as you do
+to develop your project.
+
+## Video tutorial
+
+<Video url="https://www.youtube-nocookie.com/embed/k0NcedDzEqA" />
+
+## Setting up gitlab-ci for your Unity project
+
+### I don't have a Unity project yet
+
+1. Fork
+   [the unity3d-gitlab-ci-example project](https://gitlab.com/game-ci/unity3d-gitlab-ci-example/)
+1. Clone the fork you just created locally
+1. Continue to activation instructions
+
+### I already have my own Unity project
+
+1. Clone
+   [the unity3d-gitlab-ci-example project](https://gitlab.com/game-ci/unity3d-gitlab-ci-example/)
+1. Copy
+   [`.gitlab-ci.yml`](https://gitlab.com/game-ci/unity3d-gitlab-ci-example/-/blob/main/.gitlab-ci.yml)
+   to the root of your repository,
+   [`Assets/Scripts/Editor/BuildCommand.cs`](https://gitlab.com/game-ci/unity3d-gitlab-ci-example/-/blob/main/Assets/Scripts/Editor/BuildCommand.cs)
+   and [`ci` folder](https://gitlab.com/game-ci/unity3d-gitlab-ci-example/-/blob/main/ci) to your
+   project:
+
+Assuming you've cloned the example project in the parent folder of your project, and your Unity
+project is at the root of your repository, execute these commands from the root folder of your
+project:
+
+```bash
+mkdir -p Assets/Scripts/Editor/
+cp ../unity3d-gitlab-ci-example/.gitlab-ci.yml ./
+cp -r ../unity3d-gitlab-ci-example/ci ./
+cp ../unity3d-gitlab-ci-example/Assets/Scripts/Editor/BuildCommand.cs ./Assets/Scripts/Editor/
+```
+
+1. Open and edit the
+   [`.gitlab-ci.yml`](https://gitlab.com/game-ci/unity3d-gitlab-ci-example/-/blob/main/.gitlab-ci.yml)
+   you copied to your project and update
+   [the variables](https://gitlab.com/game-ci/unity3d-gitlab-ci-example/-/blob/main/.gitlab-ci.yml#L7-13)
+   with the versions you need. Your Unity project version can be found in
+   `ProjectSettings/ProjectVersion.txt`.
+1. If your Unity project is not at the root of your repository, also update UNITY_DIR variable.
+1. Continue to activation instructions
diff --git a/versioned_docs/version-3/05-gitlab/02-activation.mdx b/versioned_docs/version-3/05-gitlab/02-activation.mdx
new file mode 100644
index 00000000..4ed4521f
--- /dev/null
+++ b/versioned_docs/version-3/05-gitlab/02-activation.mdx
@@ -0,0 +1,193 @@
+# Activation
+
+There are a few methods available, if you're using gitlab-ci, the easiest method in the current
+documentation is using gitlab-ci.
+
+:::caution Known issue with Unity activation on gitlab-ci: empty license file
+
+If you are having troubles with Unity activation with gitlab-ci, there is currently an issue with
+recent Unity versions preventing us to retrieve a license file with actual content.
+
+For more details see the
+[following issue: get-activation-file succeeding but giving a 0kb file. Unity Version 2021.2.7f1](https://gitlab.com/game-ci/unity3d-gitlab-ci-example/-/issues/171)
+and
+[the workaround](https://gitlab.com/game-ci/unity3d-gitlab-ci-example/-/issues/171#note_974622879).
+
+Don't hesitate to contribute and implement a fix 💝
+
+:::
+
+:::info Having issues with activation?
+
+Have a look at the [troubleshooting / common issues][common-issues] page.
+
+:::
+
+## Unity Personal
+
+### a. Using gitlab-ci
+
+Once you've added all required files to your project (mainly
+[`.gitlab-ci.yml`](https://gitlab.com/game-ci/unity3d-gitlab-ci-example/-/blob/main/.gitlab-ci.yml)),
+there should be a manual step that can be triggered for activation.
+
+1. Visit your project's settings > CI/CD > Variables and add `UNITY_USERNAME` and `UNITY_PASSWORD`
+   with your credentials. Make sure to use your Unity3d _email address_ for `UNITY_USERNAME`.
+1. Push your first commit to your project and visit CI/CD Pipelines.
+1. Locate your latest job, there should be a `play` button, click on it and click
+   `get-activation-file`
+1. Wait for the job to run and follow instructions in the console
+
+:::caution
+
+**Unity no longer supports manual activation of Personal licenses**
+
+When activating your Personal Unity license, you may encounter an issue where only the "Unity Pro or
+Plus" option is available, preventing the activation of a Personal license. Here is a workaround to
+resolve this:
+
+1. Visit [license.unity3d.com](https://license.unity3d.com/manual) and upload the
+   `Unity_v20XX.X.XXXX.alf` file.
+2. On the "Activate your license" page, if the "Personal" option is not available, right-click on
+   the page and choose "Inspect" to open the browser's developer tools.
+3. Find the line of HTML that looks like this:
+   `<div class="option option-personal clear" style="display: none;">`.
+4. Delete `display: none;` from the `style` attribute to make the "Personal" option visible.
+5. Now you should be able to select the "Personal" option and proceed with the activation.
+
+You can discuss this issue or find additional assistance in the
+[related Discord conversation](https://discord.com/channels/710946343828455455/1138586951604248666)
+or [GitHub ticket](https://github.com/game-ci/documentation/issues/408).
+
+_For future reference, activating a license from the command line as documented on
+[Unity's Manual Page](https://docs.unity3d.com/Manual/ManagingYourUnityLicense.html) might be an
+alternative solution._
+
+:::
+
+### b. Locally
+
+All you need is [docker](https://www.docker.com/) installed on your machine.
+
+1. Clone [this project](https://gitlab.com/game-ci/unity3d-gitlab-ci-example)
+2. Pull the docker image and run bash inside, passing Unity username and password to env
+
+   _hint: you should write this to a shell script and execute the shell script so you don't have
+   your credentials stored in your bash history_. Also make sure you use your Unity3d _email
+   address_ for `UNITY_USERNAME` env var.
+
+   ```bash
+   UNITY_VERSION=2020.1.11f1
+   IMAGE=unityci/editor # https://hub.docker.com/r/unityci/editor
+   IMAGE_VERSION=0.12 # https://github.com/game-ci/docker/releases
+   DOCKER_IMAGE=$IMAGE:$UNITY_VERSION-base-$IMAGE_VERSION
+
+   docker run -it --rm \
+   -e "UNITY_USERNAME=username@example.com" \
+   -e "UNITY_PASSWORD=example_password" \
+   -e "TEST_PLATFORM=linux" \
+   -e "WORKDIR=/root/project" \
+   -v "$(pwd):/root/project" \
+   $DOCKER_IMAGE \
+   bash
+   ```
+
+   If your password contains a `!`, you can escape it like this (`example_pass!word`):
+
+   ```bash
+   ...
+   -e "UNITY_PASSWORD=example_pass"'!'"word" \
+   ...
+   ```
+
+3. In Unity docker container's bash, run once like this, it will try to activate
+
+   ```bash
+   xvfb-run --auto-servernum --server-args='-screen 0 640x480x24' \
+   unity-editor \
+   -logFile /dev/stdout \
+   -batchmode \
+   -nographics \
+   -username "$UNITY_USERNAME" -password "$UNITY_PASSWORD"
+   ```
+
+4. Wait for output that looks like this:
+
+   ```
+   LICENSE SYSTEM [2017723 8:6:38] Posting <?xml version="1.0" encoding="UTF-8"?><root><SystemInfo><IsoCode>en</IsoCode><UserName>[...]
+   ```
+
+   If you get the following error:
+
+   > Can't activate Unity: No sufficient permissions while processing request HTTP error code 401
+
+   Make sure your credentials are valid. You may try to disable 2FA in your account and try again.
+   Once done, you should enable 2FA again for security reasons. See
+   [#11](https://gitlab.com/game-ci/unity3d-gitlab-ci-example/issues/11) for more details.
+
+5. Copy xml content and save as `unity3d.alf`
+6. Open https://license.unity3d.com/manual and answer questions
+7. Upload `unity3d.alf` for manual activation
+8. Download `Unity_v2018.x.ulf` (`Unity_v2019.x.ulf` for 2019 versions)
+9. Copy the content of `Unity_v2018.x.ulf` license file to your CI's environment variable
+   `UNITY_LICENSE`. _Note: if you are doing this on Windows, chances are the
+   [line endings will be wrong as explained here](https://gitlab.com/game-ci/unity3d-gitlab-ci-example/issues/5#note_95831816).
+   Luckily for you,
+   [`.gitlab-ci.yml`](https://github.com/game-ci/unity3d-ci-example/blob/main/.gitlab-ci.yml) of the
+   example project solves this by removing `\r` character from the ENV variable so you'll be
+   alright_
+   [`.gitlab-ci.yml`](https://gitlab.com/game-ci/unity3d-gitlab-ci-example/-/blob/main/.gitlab-ci.yml)
+   will then place the `UNITY_LICENSE` to the right place before running tests or creating the
+   builds.
+
+## Unity Plus/Pro
+
+1. Clone [this project](https://gitlab.com/game-ci/unity3d-gitlab-ci-example)
+2. Pull the docker image and run bash inside, passing Unity username and password to env
+
+   _hint: you should write this to a shell script and execute the shell script so you don't have
+   your credentials stored in your bash history_. Also make sure you use your Unity3d _email
+   address_ for `UNITY_USERNAME` env var.
+
+   ```bash
+   UNITY_VERSION=2020.1.11f1
+   IMAGE=unityci/editor # https://hub.docker.com/r/unityci/editor
+   IMAGE_VERSION=0.12 # https://github.com/game-ci/docker/releases
+   DOCKER_IMAGE=$IMAGE:$UNITY_VERSION-base-$IMAGE_VERSION
+
+   docker run -it --rm \
+   -e "UNITY_USERNAME=username@example.com" \
+   -e "UNITY_PASSWORD=example_password" \
+   -e "UNITY_SERIAL=AN-EXAM-PLE-SERIA-LKEY-1234" \
+   -e "TEST_PLATFORM=linux" \
+   -e "WORKDIR=/root/project" \
+   -v "$(pwd):/root/project" \
+   $DOCKER_IMAGE \
+   bash
+   ```
+
+3. In Unity docker container's bash, run once like this, it will try to activate
+
+   ```bash
+   xvfb-run --auto-servernum --server-args='-screen 0 640x480x24' \
+   unity-editor \
+   -logFile /dev/stdout \
+   -batchmode \
+   -nographics \
+   -username "$UNITY_USERNAME" -password "$UNITY_PASSWORD" -serial "$UNITY_SERIAL"
+   ```
+
+4. Wait for the command to finish without errors
+5. Obtain the contents of the license file by running
+   `cat /root/.local/share/unity3d/Unity/Unity_lic.ulf`
+6. Copy the content to your CI's environment variable `UNITY_LICENSE`. _Note: if you are doing this
+   on windows, chances are the
+   [line endings will be wrong as explained here](https://gitlab.com/game-ci/unity3d-gitlab-ci-example/issues/5#note_95831816).
+   Luckily for you,
+   [`.gitlab-ci.yml`](https://gitlab.com/game-ci/unity3d-gitlab-ci-example/-/blob/main/.gitlab-ci.yml)
+   solves this by removing `\r` character from the env variable so you'll be alright_
+   [`.gitlab-ci.yml`](https://gitlab.com/game-ci/unity3d-gitlab-ci-example/-/blob/main/.gitlab-ci.yml)
+   will then place the `UNITY_LICENSE` to the right place before running tests or creating the
+   builds.
+
+[common-issues]: /docs/troubleshooting/common-issues
diff --git a/versioned_docs/version-3/05-gitlab/03-example-project.mdx b/versioned_docs/version-3/05-gitlab/03-example-project.mdx
new file mode 100644
index 00000000..3b7c3db5
--- /dev/null
+++ b/versioned_docs/version-3/05-gitlab/03-example-project.mdx
@@ -0,0 +1,50 @@
+# Example Project
+
+## About
+
+[The `unity3d-gitlab-ci-example` project](https://gitlab.com/game-ci/unity3d-gitlab-ci-example/)
+uses an updated version of the
+[Unity's Creator Kit: RPG free asset](https://assetstore.unity.com/packages/templates/tutorials/creator-kit-rpg-149309)
+which is not affiliated with this project at all. Feel free to explore it, dialogs are a bit
+different ;)
+
+The example project is a Proof of Concept to **run unity3d tests and builds inside a CI** using
+**[game-ci/docker unity editor docker images](https://github.com/game-ci/docker)**. It currently
+creates builds for Windows, Linux, macOS, webgl, Linux IL2cpp, Android and iOS Xcode project. The
+webgl build is published by the CI to [gitlab-pages](https://about.gitlab.com/features/pages/).
+**You can try the built project on
+[the published gitlab-pages](https://game-ci.gitlab.io/unity3d-gitlab-ci-example/)**.
+
+## Git remotes
+
+[The `unity3d-gitlab-ci-example` project](https://gitlab.com/game-ci/unity3d-gitlab-ci-example/) is
+hosted on multiple remotes to provide examples for
+[Gitlab-CI](https://about.gitlab.com/product/continuous-integration/),
+[Travis CI](https://travis-ci.org/) and [CircleCI](https://circleci.com/)
+
+- [github](https://github.com/game-ci/unity3d-ci-example)
+- [gitlab](https://gitlab.com/game-ci/unity3d-gitlab-ci-example)
+
+## How to run scripts locally
+
+You can execute the local scripts and specify the path of your Unity executable using
+`UNITY_EXECUTABLE`. You may try this in your project before you setup the whole CI, so you confirm
+it works with your current unity version 👍.
+
+## Test
+
+[`./local_test.sh`](https://gitlab.com/game-ci/unity3d-gitlab-ci-example/-/blob/main/local_test.sh)
+
+```bash
+UNITY_EXECUTABLE="/Applications/Unity/Hub/Editor/2019.3.7f1/Unity.app/Contents/MacOS/Unity" \
+  ./local_test.sh
+```
+
+## Build
+
+[`./local_build.sh`](https://gitlab.com/game-ci/unity3d-gitlab-ci-example/-/blob/main/local_build.sh)
+
+```bash
+UNITY_EXECUTABLE="/Applications/Unity/Hub/Editor/2019.3.7f1/Unity.app/Contents/MacOS/Unity" \
+  ./local_build.sh
+```
diff --git a/versioned_docs/version-3/05-gitlab/04-custom-build-options.mdx b/versioned_docs/version-3/05-gitlab/04-custom-build-options.mdx
new file mode 100644
index 00000000..82e66314
--- /dev/null
+++ b/versioned_docs/version-3/05-gitlab/04-custom-build-options.mdx
@@ -0,0 +1,46 @@
+# Custom build options
+
+First, you need to understand how build options are passed to the build.
+
+## Build command
+
+See
+[Assets/Scripts/Editor/BuildCommand.cs](https://gitlab.com/game-ci/unity3d-gitlab-ci-example/-/blob/main/Assets/Scripts/Editor/BuildCommand.cs).
+
+This is the script used during `Unity` command line execution. It is passed to the
+[`-executeMethod <ClassName.MethodName>` command line parameter](https://docs.unity3d.com/Manual/CommandLineArguments.html)
+like this:
+
+```bash
+unity-editor \
+  # ...
+  -executeMethod BuildCommand.PerformBuild \
+  # ...
+```
+
+You need to have this file in your project in order to build your project in the CI.
+
+### Workflow file
+
+See
+[.gitlab-ci.yml](https://gitlab.com/game-ci/unity3d-gitlab-ci-example/-/blob/main/.gitlab-ci.yml).
+
+You can add `BuildOptions` per target by adding environment variable `BuildOptions`.
+
+```yaml
+build-ios-xcode:
+  <<: *build
+  image: $IMAGE:$UNITY_VERSION-ios-$IMAGE_VERSION
+  variables:
+    BUILD_TARGET: iOS
+    BuildOptions: AcceptExternalModificationsToPlayer
+```
+
+If you would like to use several `BuildOptions`, you have to separate all values by `,`:
+
+```yaml
+BuildOptions: AcceptExternalModificationsToPlayer,CompressTextures,ConnectToHost
+```
+
+See [Unity3d `BuildOptions` reference](https://docs.unity3d.com/ScriptReference/BuildOptions.html)
+for allowed values.
diff --git a/versioned_docs/version-3/05-gitlab/05-tests.mdx b/versioned_docs/version-3/05-gitlab/05-tests.mdx
new file mode 100644
index 00000000..849e9769
--- /dev/null
+++ b/versioned_docs/version-3/05-gitlab/05-tests.mdx
@@ -0,0 +1,19 @@
+# Tests
+
+## Unity Tests
+
+Unity supports two kinds of tests (`editmode` and `playmode`). The example project supports both.
+More information and documentation concerning Unity tests can be found here:  
+[Unity Test Framework](https://docs.unity3d.com/Packages/com.unity.test-framework@1.1/manual/index.html)
+
+## Example Project Test files
+
+Tests can be found here:
+
+- [`editmode` tests in `Assets/Scripts/Editor/EditModeTests`](https://gitlab.com/game-ci/unity3d-gitlab-ci-example/-/blob/main/Assets/Scripts/Editor/EditModeTests)
+- [`playmode` tests in `Assets/Tests/`](https://gitlab.com/game-ci/unity3d-gitlab-ci-example/-/blob/main/Assets/Tests/)
+
+## Code coverage support
+
+This was implemented here in the example project:  
+[unity3d-gitlab-ci-example!42](https://gitlab.com/game-ci/unity3d-gitlab-ci-example/-/merge_requests/42)
diff --git a/versioned_docs/version-3/05-gitlab/06-deployment/_category_.yaml b/versioned_docs/version-3/05-gitlab/06-deployment/_category_.yaml
new file mode 100644
index 00000000..f74a60fd
--- /dev/null
+++ b/versioned_docs/version-3/05-gitlab/06-deployment/_category_.yaml
@@ -0,0 +1,5 @@
+---
+position: 6.0
+label: Deployment
+collapsible: true
+collapsed: true
diff --git a/versioned_docs/version-3/05-gitlab/06-deployment/android.mdx b/versioned_docs/version-3/05-gitlab/06-deployment/android.mdx
new file mode 100644
index 00000000..7c697057
--- /dev/null
+++ b/versioned_docs/version-3/05-gitlab/06-deployment/android.mdx
@@ -0,0 +1,91 @@
+# Android
+
+Before `2018.4.8f1` for 2018 versions and before `2019.2.4f1` for 2019 versions, you will need a
+specific Unity license (because that is not the same docker image). Add the content of your specific
+Unity license in your CI's environment variable : `UNITY_LICENSE_CONTENT_ANDROID`. _This is not
+required anymore now that images share a base image
+[See related change](https://gitlab.com/game-ci/unity3d/merge_requests/63)_
+
+By default the apk is not signed and the build will use the Unity's default debug key. For _security
+reasons_, **you should not add your keystore to git**.
+
+## Encode your keystore
+
+Encode your keystore file as base64 using openssl:
+
+```bash
+openssl base64 -A -in yourKeystore.keystore
+```
+
+Copy the result to your CI's environment variable `ANDROID_KEYSTORE_BASE64`
+
+Add following environment variables:
+
+- `KEYSTORE_PASS`: Keystore pass
+- `KEY_ALIAS_NAME`: Keystore alias name to use (if not set, the program will use the alias name set
+  in Project's PlayerSettings)
+- `KEY_ALIAS_PASS`: Keystore alias pass to use
+
+Note about _keystore security_, if you would like to use another solution for storage, see
+[Where to Store Android KeyStore File in CI/CD Cycle?](https://android.jlelse.eu/where-to-store-android-keystore-file-in-ci-cd-cycle-2365f4e02e57).
+
+### Android app bundle
+
+`BUILD_APP_BUNDLE` env var is defined in `gitlab-ci.yml`. Set it to `true` to build an `.aab` file.
+Note: to build an android app bundle, you need an image with **Android NDK**.
+
+See [related issue gableroux/unity3d#61](https://gitlab.com/game-ci/unity3d/issues/61)
+
+### Bundle version code
+
+The bundle version code must be increment for each deployed build.
+
+To simplify the process, the `BUNDLE_VERSION_CODE` env var is used and set as bundle version code.
+
+Currently, for gitlab, `BUNDLE_VERSION_CODE = $CI_PIPELINE_IID`.
+[Documentation](https://docs.gitlab.com/ee/ci/variables/predefined_variables.html)  
+If you use another CI solution, set a CI env var incrementing for each pipeline.
+
+### Fastlane supply (deployement)
+
+Follow [setup instructions](https://docs.fastlane.tools/actions/supply/) to get a google play
+console token, then, add the content to env var `GPC_TOKEN`.
+
+Uncomment the `#deploy-android` job in gitlab-ci.yml and replace `com.youcompany.yourgame` by your
+package name.
+
+You can change the track `internal` to `alpha`, `beta` or `production` (Note: if you are using the
+`internal` track you will also have to mark your release as a draft in the `fastlane supply` command
+using `--release_status draft`).
+
+**Gemfile**
+
+You will also need to add a Gemfile to your project to install the `fastlane` gem. Something like
+the following:
+
+```
+source "https://rubygems.org"
+
+gem "fastlane"
+```
+
+and then copy the file to the current directory prior to installing the gem. eg
+`cp $CI_PROJECT_DIR/Gemfile .`.
+
+That is the simplest way with command line but you can also make `fastlane/Fastfile` and
+`fastlane/Appfile`, with the following command after building a temporary gradle project (export
+gradle project option in Unity build settings):
+
+```bash
+fastlane init
+```
+
+Then run the following command:
+
+```bash
+fastlane supply init
+```
+
+and update all metadata, images, changelogs, etc... These will be uploaded to the store everytime.
+Refer to [fastlane supply documentation](https://docs.fastlane.tools/actions/supply/) for more
+details.
diff --git a/versioned_docs/version-3/05-gitlab/06-deployment/ios.mdx b/versioned_docs/version-3/05-gitlab/06-deployment/ios.mdx
new file mode 100644
index 00000000..41154bc0
--- /dev/null
+++ b/versioned_docs/version-3/05-gitlab/06-deployment/ios.mdx
@@ -0,0 +1,144 @@
+# iOS
+
+## Setup (only one time per mac)
+
+Install the latest Xcode command line tools :
+
+```bash
+xcode-select --install
+```
+
+Install fastlane using:
+
+```bash
+# Using RubyGems
+sudo gem install fastlane -NV
+
+# Alternatively using Homebrew
+brew install fastlane
+```
+
+## Unity Settings
+
+1. Switch target to iOS
+1. In `PlayerSettings -> Other Settings`
+   1. Fill the field `Signing Team ID`
+   1. Ensure `Automatically Sign` is unchecked
+   1. iOS Provisioning Profile
+      1. `ProfileID`: `match AppStore your_bundle_identifier` _Replace `your_bundle_identifier` by
+         yours_
+      1. `ProfileType`: `Distribution`
+
+## XCode project
+
+Make a first iOS build using your mac from Unity, that will create an xcode project.  
+Ensure you target the same path as the CI.  
+Ex: if you let `BUILD_NAME: ExampleProjectName` in `.gitlab-ci.yml`, your xcode project must be at
+the root of the following path: `.\Builds\iOS\ExampleProjectName\`
+
+## App on portal
+
+Make sure that you have setup your app on the Apple Developer Portal and the App Store Connect or
+use [fastlane produce](https://docs.fastlane.tools/actions/produce/) to create it.
+
+## Fastlane initialization
+
+Open the terminal at the same path then run `fastlane init`, follow instructions to generate Appfile
+and default Fastfile.
+
+## Provisioning profile
+
+Run `fastlane match init`, follow instructions, select `appstore` provisioning profile type.
+([Documentation](https://docs.fastlane.tools/actions/match/))
+
+## Make lane
+
+Copy the following instructions on your `fastlane/Fastfile`:
+
+```ruby
+default_platform(:ios)
+
+platform :ios do
+  desc "Push a new beta build to TestFlight"
+  lane :beta do
+    sync_code_signing(type:"appstore", readonly: is_ci)
+    increment_build_number({
+        build_number: latest_testflight_build_number + 1
+    })
+    build_app(scheme:"Unity-iPhone")
+    upload_to_testflight(groups:["Team"])
+  end
+end
+```
+
+Note about `upload_to_testflight`: Change "Team" to your internal tester or remove
+`(groups:["Team"])` if you want set manually who can test the build
+
+### Related documentation
+
+- [sync_code_signing (alias for match)](https://docs.fastlane.tools/actions/sync_code_signing/)
+- [increment_build_number](https://docs.fastlane.tools/actions/increment_build_number/)
+- [build_app (alias for gym)](https://docs.fastlane.tools/actions/build_app/)
+- [upload_to_testflight (alias for pilot)](https://docs.fastlane.tools/actions/testflight/)
+
+## Run tests locally
+
+Run the following command to test the build and the deployement localy:
+
+```bash
+fastlane ios beta
+```
+
+If the build and upload are ok, you have to force add some file to your git using command below
+
+```bash
+git add -f pathToTheFileToAdd
+```
+
+you have to add the following files:
+
+- `Gemfile`
+- `Gemfile.lock` (if here)
+- `fastlane/Appfile`
+- `fastlane/Fastfile`
+- `fastlane/Matchfile`
+
+## Gitlab-runner - register your mac
+
+To automate your build with gitlab, you need to setup your mac as a gitlab runner.  
+Installation:
+
+```bash
+sudo curl --output /usr/local/bin/gitlab-runner https://gitlab-runner-downloads.s3.amazonaws.com/latest/binaries/gitlab-runner-darwin-amd64
+```
+
+Give permission to execute :
+
+```bash
+sudo chmod +x /usr/local/bin/gitlab-runner
+```
+
+- [Source (if you would like to check)](https://docs.gitlab.com/runner/install/osx.html)
+
+Go to your project gitlab page, then go to `settings` -> `CI/CD` -> `Runners` -> `Specitic Runners`
+-> `Set up a specific Runner manually` -> take note of the token
+
+[Follow these instructions](https://docs.gitlab.com/runner/register/index.html) to register your mac
+as a gitlab-runner for your specific project.  
+Follow **macOS** instructions **without** sudo command for registration.
+
+- Tags: set `mac,ios`
+- Executor: set `shell`
+
+Then, to install/launch the runner:
+
+```bash
+cd ~
+gitlab-runner install
+gitlab-runner start
+```
+
+Runner is installed and will be run after a system reboot.
+
+Now, you can uncomment the job `build-and-deploy-ios` in `.gitlab-ci.yml` to make the app build and
+deployement work.
diff --git a/versioned_docs/version-3/05-gitlab/_category_.yaml b/versioned_docs/version-3/05-gitlab/_category_.yaml
new file mode 100644
index 00000000..b242cd28
--- /dev/null
+++ b/versioned_docs/version-3/05-gitlab/_category_.yaml
@@ -0,0 +1,5 @@
+---
+position: 4.0
+label: GitLab
+collapsible: true
+collapsed: true
diff --git a/versioned_docs/version-3/08-docker/01-docker-images.mdx b/versioned_docs/version-3/08-docker/01-docker-images.mdx
new file mode 100644
index 00000000..fb0718d2
--- /dev/null
+++ b/versioned_docs/version-3/08-docker/01-docker-images.mdx
@@ -0,0 +1,84 @@
+# GameCI Docker images for Unity
+
+All projects for Unity in GameCI use [`game-ci/docker`](https://github.com/game-ci/docker/) docker
+images which are specialised for CI and command-line use. These images are published on
+[docker hub as `unityci/editor`](https://hub.docker.com/r/unityci/editor/tags?page=1&ordering=last_updated).
+
+They are established empirically by the community and come forth from the
+[`gableroux/unity3d`](https://gitlab.com/game-ci/unity3d/) project. It was previously published on
+[docker hub as `gableroux/unity3d`](https://hub.docker.com/r/gableroux/unity3d/). **There won't be
+any new versions releases for `gableroux/unity3d` as it is now deprecated in favor of
+[`game-ci/docker`](https://github.com/game-ci/docker/).**
+
+Images for newly released Unity editor versions are added almost immediately to
+[`game-ci/docker`](https://github.com/game-ci/docker/) . This process is automated, please allow a
+few hours.
+
+## Features
+
+- All editor versions
+- Git + LFS
+- ECS compatible
+- Cross-version license activations
+
+## Limitations
+
+#### Older versions of Unity
+
+There will be limited support for older versions of Unity.
+
+This is because for older versions, many factors regarding the preparation of stable docker images
+can not be determined programmatically.
+
+Due to that:
+
+- Android builds for 2019.2 or lower will require you to roll your own images. This process will
+  require you to manually specify NDK/SDK locations.
+
+#### Limited IL2CPP support
+
+Currently images are only available with Ubuntu or Windows as the base operating system.
+
+Some platforms require their respective operating systems in order to generate IL2CPP builds.
+
+That's why:
+
+- IL2CPP for MacOS is not supported
+
+We are looking to include MacOS as a base image "in the future", which is mostly dependent on
+contributions from the community.
+
+If you are looking to generate IL2CPP builds for MacOS, you can do so via
+[Github Actions](/docs/github/getting-started#il2cpp-example) without a docker container.
+
+#### Concurrent builds on Windows and MacOS
+
+Windows and MacOS will each consume an additional license seat if they are needed for a target
+platform. This is not an issue for free licenses, but for paid licenses, you will need to be mindful
+of starting too many parallel jobs as activation will fail. Below are some examples of number of
+consumed seats for a build:
+
+You are building for 1 target on a Linux based platform, 1 target for a Windows based platform, and
+1 target for a MacOS based platform:
+
+- Number of seats consumed for the Linux build instances: 1
+- Number of seats consumed for the Windows build instances: 1
+- Number of seats consumed for the MacOS build instances: 1
+
+Total concurrently consumed seats: **3**
+
+You are building for 3 targets on a Linux based platform, 3 targets for a Windows based platform,
+and 1 target for a MacOS based platform:
+
+- Number of seats consumed for the Linux build instances: 1
+- Number of seats consumed for the Windows build instances: 1
+- Number of seats consumed for the MacOS build instances: 1
+
+Total concurrently consumed seats: **3**
+
+Notice it doesn't matter how many targets you build on each platform, the cost is always one
+concurrent license seat. This does not preclude you from doing builds sequentially, for example if
+you only have 1 seat available for your CI pipeline, you could build all Linux targets first, then
+build all Windows targets, and finally build the 1 MacOS target after that. More license seats would
+allow you to parallelize more platforms. In this example, having 3 seats means being able to build
+all targets simultaneously.
diff --git a/versioned_docs/version-3/08-docker/02-windows-docker-images.mdx b/versioned_docs/version-3/08-docker/02-windows-docker-images.mdx
new file mode 100644
index 00000000..c101f674
--- /dev/null
+++ b/versioned_docs/version-3/08-docker/02-windows-docker-images.mdx
@@ -0,0 +1,271 @@
+# Windows docker images
+
+Windows images are used for some features available only in windows. The main reason is usually
+building an IL2CPP version of the application.
+
+To build applications effectively in terms of build time, the very base image is a .NET framework
+4.8. It's cached on GitHub actions runners and we truly need .NET. The base Windows image can be
+found in
+[https://github.com/game-ci/docker](https://github.com/game-ci/docker/blob/main/images/windows/base/Dockerfile).
+
+## Features
+
+- Git
+- Choco package manager
+
+## Limitations
+
+### Microsoft does not allow redistribution of Visual Studio build tools
+
+Microsoft does not permit publishing images with VS Build tools which are needed for IL2CPP builds
+[`discussion`](https://github.com/microsoft/Windows-Containers/issues/102#issuecomment-827170844).
+
+You will encounter exceptions in the Unity log similar to
+`error: Could not set up a toolchain for Architecture x64. Make sure you have the right build tools installed for il2cpp builds.`
+
+<details>
+  <summary>Expand this section for a full log example.</summary>
+
+```
+error: Could not set up a toolchain for Architecture x64. Make sure you have the right build tools
+installed for il2cpp builds. Details: IL2CPP C++ code builder is unable to build C++ code. In order
+to build C++ code for Windows Desktop, you must have one of these installed: * Visual Studio 2022 or
+newer with C++ compilers and Windows 10 SDK (recommended) * Visual Studio 2019 with C++ compilers and
+Windows 10 SDK * Visual Studio 2017 with C++ compilers and Windows 10 SDK * Visual Studio 2015 with
+C++ compilers and Windows 10 SDK Visual Studio 2017 (or newer) is detected using `vswhere.exe` as well
+as VSCOMNTOOLS environment variables. Visual Studio 2015 is detected by looking at "SOFTWARE\Microsoft\VisualStudio\14.0_Config\InstallDir"
+in the registry as well as VSCOMNTOOLS environment variables. Windows 10 SDK is detected by looking
+at "SOFTWARE\Wow6432Node\Microsoft\Microsoft SDKs\Windows\v10.0\InstallationFolder" in the registry.
+Unable to detect any compatible Visual Studio installation! * Found Visual Studio 2022 installation
+without C++ tool components Windows 10 SDK is not installed. You can install from here: https://developer.microsoft.com/en-us/windows/downloads/windows-10-sdk/
+```
+
+</details>
+
+There are two options to avoid this obstacle:
+
+1. (_Recommended_) Inject/mount Microsoft Visual Studio with VC++ and Windows 10 SDK from the host
+   system into the container during runtime.
+2. Build a custom image and push it to a docker registry.
+
+#### Option 1. Injecting VC++ from the host system into the container
+
+> These instructions have been validated with Visual Studio 2022 and Unity 2021 LTS.
+
+_Install Visual Studio Build Tools_
+
+The recommended way to install the correct dependencies on the host is with
+[Chocolatey](https://chocolatey.org/). This works with Windows 10/11, Windows Server, and Windows
+Server Core.
+
+```powershell
+choco install visualstudio2022-workload-vctools --no-progress -y
+```
+
+There is a way to install the same dependencies from the graphical
+[Visual Studio Installer](https://visualstudio.microsoft.com/downloads/), but the workload component
+options in the installer frequently change.
+
+_The following directories need to be bind-mounted into the container_
+
+- C:\Program Files (x86)\Windows Kits
+- C:\Program Files (x86)\Microsoft Visual Studio
+- C:\Program Files\Microsoft Visual Studio
+- C:\ProgramData\Microsoft\VisualStudio
+
+> Please confirm all of the above directories exist in your installation. Some may be missing and
+> things might still work OK without them. Omit the missing directories in the following steps.
+
+_Docker run example_
+
+```powershell
+docker run `
+  -v "C:\Program Files (x86)\Windows Kits:C:\Program Files (x86)\Windows Kits" `
+  -v "C:\Program Files (x86)\Microsoft Visual Studio:C:\Program Files (x86)\Microsoft Visual Studio" `
+  -v "C:\Program Files\Microsoft Visual Studio:C:\Program Files\Microsoft Visual Studio"
+  -v "C:\ProgramData\Microsoft\VisualStudio:C:\ProgramData\Microsoft\VisualStudio" `
+  unityci/editor:windows-$env:UNITY_VERSION-windows-il2cpp-$env:UNITY_IMAGE_VERSION
+```
+
+_Gitlab runner config.toml example_
+
+```toml
+#...
+volumes = [
+  "C:\\Program Files (x86)\\Windows Kits:C:\\Program Files (x86)\\Windows Kits",
+  "C:\\Program Files\\Microsoft Visual Studio:C:\\Program Files\\Microsoft Visual Studio",
+  "C:\\Program Files (x86)\\Microsoft Visual Studio:C:\\Program Files (x86)\\Microsoft Visual Studio",
+  "C:\\ProgramData\\Microsoft\\VisualStudio:C:\\ProgramData\\Microsoft\\VisualStudio"
+]
+#...
+```
+
+#### Option 2. Building a custom image
+
+```dockerfile
+ARG UNITY_VERSION=''
+ARG UNITY_IMAGE_VERSION='1'
+
+FROM unityci/editor:windows-${UNITY_VERSION}-windows-il2cpp-${UNITY_IMAGE_VERSION}
+
+RUN choco install visualstudio2022-workload-vctools --no-progress -y
+```
+
+### Licenses are not valid between containers runs
+
+This behaviour is different to Ubuntu containers where it's possible to use a single license for
+even a few different runners.
+
+In Windows, it's necessary to acquire a license every time and return it after a building process.
+License files for every run are identical apart from the last four symbols of the machine hash code.
+This restriction has not been solved yet
+
+#### Scripting example
+
+The simplest way is to write a couple of scripts (copied from
+[`Unity3d docs`](https://docs.unity3d.com/Manual/ManagingYourUnityLicense.html)) and wrap it to the
+try-finally block
+
+**Note**: Path to Unity3d is
+`C:\Program Files\Unity\Hub\Editor\{UNITY_EDITOR_VERSION}\Editor\Unity.exe`
+
+```powershell
+try {
+  build.ps1
+} finally {
+  return-license.ps1
+}
+```
+
+#### GitLab example
+
+```
+unity-windows-il2cpp-build:
+  variables:
+    UPM_CACHE_ROOT: $CI_PROJECT_DIR/.upm
+    UNITY_IMAGE_VERSION: "1"
+    UNITY_MODULE: "il2cpp"
+    UNITY_IMAGE_PREFIX: "unityci/editor"
+    # Do not use quotes around this argument
+    UNITY_EXECUTABLE: C:\Program Files\Unity\Hub\Editor\$UNITY_VERSION\Editor\Unity.exe
+    BUILD_COMMAND: "BuildCommand.PerformBuild"
+    BUILD_TARGET: "Win64"
+    BUILD_NAME: "example"
+    BUILD_PATH: "dist/"
+  image: $UNITY_IMAGE_PREFIX:windows-$UNITY_VERSION-$UNITY_MODULE-$UNITY_IMAGE_VERSION
+  tags:
+    - Docker-Windows
+  cache:
+    - key: "$UNITY_VERSION-$BUILD_TARGET-Library"
+      paths:
+        - $CI_PROJECT_DIR/Library/
+    - key: "unity3d"
+      paths:
+        - $UPM_CACHE_ROOT
+  artifacts:
+    expire_in: "1 day"
+    paths:
+      - dist
+  needs:
+    - get-unity-version
+  script:
+    - |
+      try {
+        & $env:UNITY_EXECUTABLE `
+        -projectPath $env:CI_PROJECT_DIR `
+        -quit `
+        -batchmode `
+        -nographics `
+        -buildTarget $env:BUILD_TARGET `
+        -executeMethod $env:BUILD_COMMAND `
+        -logFile - `
+        -username $env:UNITY_USERNAME `
+        -password $env:UNITY_PASSWORD `
+        -serial $env:UNITY_SERIAL `
+        | Out-Host
+      }
+      finally {
+        & $env:UNITY_EXECUTABLE `
+        -quit `
+        -batchmode `
+        -nographics `
+        -logFile - `
+        -username $env:UNITY_USERNAME `
+        -password $env:UNITY_PASSWORD `
+        -returnlicense `
+        | Out-Host
+      }
+```
+
+## Troubleshooting: GitLab
+
+### Gitlab doesn't have (or has few) shared docker-windows runners
+
+There is no other option right now, but
+[use a private runner](https://docs.gitlab.com/runner/install/). Please, set the `docker-windows`
+type of the runner
+
+Default docker-for-windows settings are very resource-mean. It uses a single core and 1Gb of RAM.
+That's why the custom configuration is highly recommended
+
+**config.toml**
+
+```toml
+#...
+[runners.docker]
+  cpus = "12"
+  memory = "13g"
+  hostname = "dockerImage"
+#...
+```
+
+**Note:** `hostname` doesn't influence the performance, but one day can help with license
+association to a machine
+
+### Default shell for GitLab Runner is PowerShell Core
+
+GitLab Runner changed the default docker-windows executor shell in v14 to PowerShell Core which is a
+newer version of PowerShell than is distributed with base windows container images.
+
+There are two workarounds:
+
+1. (_Recommended_) Manually specify the shell in the config to be the pre-v14 default.
+2. Build a custom image including PowerShell Core and push it to a docker registry.
+
+_Option 1: Change it in the `config.toml`_
+
+```toml
+[[runners]]
+  shell = "powershell"
+```
+
+_Option 2: Install PowerShell Core_
+
+```dockerfile
+ARG UNITY_VERSION=''
+ARG UNITY_IMAGE_VERSION='1'
+
+FROM unityci/editor:windows-${UNITY_VERSION}-windows-il2cpp-${UNITY_IMAGE_VERSION}
+
+RUN choco install pwsh --no-progress -y
+```
+
+Then push it to a docker registry. Installing `pwsh` during a pipeline doesn't help.
+
+### Git-ssh dependency package checkout fails
+
+The base image `windowsservercore` is too old and has some outdated packages. One of them, `OpenSSH`
+has [a bug](https://github.com/PowerShell/Win32-OpenSSH/issues/1263) that breaks the remote
+repository signature check.
+
+The best option here is to replace it with something more recent
+
+```powershell
+# Manually remove an old ssh-agent service
+sc.exe delete ssh-agent
+choco install openssh -params '"/SSHAgentFeature"' --no-progress -y
+$env:GIT_SSH="C:\Program Files\OpenSSH-Win64\ssh.exe"
+```
+
+**Note:** `ssh-add` must be used from a different location,
+`C:\Program Files\OpenSSH-Win64\ssh-add.exe`
diff --git a/versioned_docs/version-3/08-docker/03-customize-docker-images.mdx b/versioned_docs/version-3/08-docker/03-customize-docker-images.mdx
new file mode 100644
index 00000000..6a7819ab
--- /dev/null
+++ b/versioned_docs/version-3/08-docker/03-customize-docker-images.mdx
@@ -0,0 +1,143 @@
+# Customize GameCI Unity Docker images
+
+Sometimes, you will want to add tools to the existing unity docker images for specific needs. For
+example, in some projects, you might need Blender installed for unity to allow building a project
+with blender assets. Sometimes, you'll need some specific command lines or runtime that are used by
+unity in a _postprocess_ step. This documentation will guide you into building your own images on
+top of the existing ones to add your desired tools.
+
+## Example: Add Ruby to existing images
+
+In the following example, we will be adding `Ruby` on top of the existing docker images (all unity
+components) for the `2021.1.16f1` unity version and GameCI's `0.15.0` version and publish them.
+
+### Build script
+
+`build.sh`
+
+```bash
+#!/usr/bin/env bash
+
+set -ex
+
+UNITY_VERSION=2021.1.16f1
+GAME_CI_VERSION=0.15.0 # https://github.com/game-ci/docker/releases
+MY_USERNAME=gableroux
+
+# don't hesitate to remove unused components from this list
+declare -a components=("android" "ios" "linux-il2cpp" "mac-mono" "webgl" "windows-mono")
+
+for component in "${components[@]}"
+do
+  GAME_CI_UNITY_EDITOR_IMAGE=unityci/editor:ubuntu-${UNITY_VERSION}-${component}-${GAME_CI_VERSION}
+  IMAGE_TO_PUBLISH=${MY_USERNAME}/editor:ubuntu-${UNITY_VERSION}-${component}-${GAME_CI_VERSION}
+  docker build --build-arg GAME_CI_UNITY_EDITOR_IMAGE=${GAME_CI_UNITY_EDITOR_IMAGE} . -t ${IMAGE_TO_PUBLISH}
+# uncomment the following to publish the built images to docker hub
+#  docker push ${IMAGE_TO_PUBLISH}
+done
+```
+
+### Dockerfile
+
+`Dockerfile`
+
+```dockerfile
+# initially inspired from https://github.com/drecom/docker-ubuntu-ruby/blob/master/Dockerfile
+ARG RUBY_PATH=/usr/local/
+ARG RUBY_VERSION=2.6.0
+ARG GAME_CI_UNITY_EDITOR_IMAGE
+
+# build ruby
+FROM ubuntu:18.04 AS rubybuild
+
+RUN apt-get update \
+&&  apt-get upgrade -y --force-yes \
+&&  apt-get install -y --force-yes \
+    libssl-dev \
+    libreadline-dev \
+    zlib1g-dev \
+    wget \
+    curl \
+    git \
+    build-essential \
+&&  apt-get clean \
+&&  rm -rf /var/cache/apt/archives/* /var/lib/apt/lists/*
+
+ARG RUBY_PATH
+ARG RUBY_VERSION
+RUN git clone git://github.com/rbenv/ruby-build.git $RUBY_PATH/plugins/ruby-build \
+&&  $RUBY_PATH/plugins/ruby-build/install.sh
+RUN ruby-build $RUBY_VERSION $RUBY_PATH
+
+# inject ruby and additional dependencies in game-ci's unity editor image
+FROM $GAME_CI_UNITY_EDITOR_IMAGE
+
+ARG RUBY_PATH
+ENV PATH $RUBY_PATH/bin:$PATH
+RUN apt-get update && \
+    apt-get install -y \
+        git \
+        curl \
+        gcc \
+        make \
+        libssl-dev \
+        zlib1g-dev \
+        libsqlite3-dev
+COPY --from=rubybuild $RUBY_PATH $RUBY_PATH
+```
+
+### Usage example
+
+Locally, invoke the `build.sh` script (example on a unix system):
+
+```bash
+chmod +x build.sh
+./build.sh
+```
+
+As a result, you will now have your own docker image with desired tools available during build time.
+To confirm `ruby` is correctly installed, we can invoke the command within the image we just built:
+
+```bash
+docker run --rm -it gableroux/editor:ubuntu-2021.1.16f1-android-0.15.0 ruby --version
+ruby 2.6.0p0 (2018-12-25 revision 66547) [x86_64-linux]
+```
+
+If you are using
+[github-actions unity-builder](https://github.com/marketplace/actions/unity-builder) you can then
+customize the docker image used during build using
+[the customimage parameter](https://game.ci/docs/github/builder#customimage)
+
+For more information on how to publish to docker hub, you may refer to
+[docker's documentation](https://docs.docker.com/docker-hub/repos/)
+
+## Example : Include Blender
+
+To include blender in the image used to build your unity project, you can define a custom Dockerfile
+based on unityci/editor and install blender on top of it.
+
+### Dockerfile
+
+```dockerfile
+ARG GAMECI_IMAGE=unityci/editor:2021.3.1f1-windows-mono-1.0.1
+FROM $GAMECI_IMAGE
+
+ARG BLENDER_SHORT_VERSION=3.4
+ARG BLENDER_FULL_VERSION=3.4.1
+
+RUN echo "BLENDER_SHORT_VERSION: $BLENDER_SHORT_VERSION"
+RUN echo "BLENDER_FULL_VERSION: $BLENDER_FULL_VERSION"
+RUN apt-get update && \
+    apt-get install -y wget && \
+    wget https://download.blender.org/release/Blender$BLENDER_SHORT_VERSION/blender-$BLENDER_FULL_VERSION-linux-x64.tar.xz && \
+    tar -xf blender-$BLENDER_FULL_VERSION-linux-x64.tar.xz && \
+    rm blender-$BLENDER_FULL_VERSION-linux-x64.tar.xz
+
+ENV PATH="$PATH:/blender-$BLENDER_FULL_VERSION-linux-x64"
+
+```
+
+### Usage
+
+You can build this image and upload it to your own Dockedhub registry to reference it in your Unity
+pipeline afterward.
diff --git a/versioned_docs/version-3/08-docker/04-versions.mdx b/versioned_docs/version-3/08-docker/04-versions.mdx
new file mode 100644
index 00000000..0c8b1405
--- /dev/null
+++ b/versioned_docs/version-3/08-docker/04-versions.mdx
@@ -0,0 +1 @@
+# Versions
diff --git a/versioned_docs/version-3/08-docker/_category_.yaml b/versioned_docs/version-3/08-docker/_category_.yaml
new file mode 100644
index 00000000..69639fb5
--- /dev/null
+++ b/versioned_docs/version-3/08-docker/_category_.yaml
@@ -0,0 +1,5 @@
+---
+position: 8.0
+label: Docker
+collapsible: true
+collapsed: true
diff --git a/versioned_docs/version-3/09-troubleshooting/_category_.yaml b/versioned_docs/version-3/09-troubleshooting/_category_.yaml
new file mode 100644
index 00000000..a62b1200
--- /dev/null
+++ b/versioned_docs/version-3/09-troubleshooting/_category_.yaml
@@ -0,0 +1,5 @@
+---
+position: 9.0
+label: Troubleshooting
+collapsible: true
+collapsed: true
diff --git a/versioned_docs/version-3/09-troubleshooting/common-issues.mdx b/versioned_docs/version-3/09-troubleshooting/common-issues.mdx
new file mode 100644
index 00000000..b50b0613
--- /dev/null
+++ b/versioned_docs/version-3/09-troubleshooting/common-issues.mdx
@@ -0,0 +1,319 @@
+# Common issues
+
+Below you'll find a collection of answers to commonly reported problems.
+
+## Unity Activation
+
+If you are having troubles with activation, you are not alone, this is a common problem, and it is
+not the easiest thing to solve. Here are some tips:
+
+- Try removing special characters from your password, sometimes they cause problems with command
+  lines. _This is not a security advice_
+- Your username should be an email
+- Confirm you are able to connect on Unity's website using your credentials
+
+:::caution
+
+**Unity no longer supports manual activation of Personal licenses**
+
+When activating your Personal Unity license, you may encounter an issue where only the "Unity Pro or
+Plus" option is available, preventing the activation of a Personal license. Here is a workaround to
+resolve this:
+
+1. Visit [license.unity3d.com](https://license.unity3d.com/manual) and upload the
+   `Unity_v20XX.X.XXXX.alf` file.
+2. On the "Activate your license" page, if the "Personal" option is not available, right-click on
+   the page and choose "Inspect" to open the browser's developer tools.
+3. Find the line of HTML that looks like this:
+   `<div class="option option-personal clear" style="display: none;">`.
+4. Delete `display: none;` from the `style` attribute to make the "Personal" option visible.
+5. Now you should be able to select the "Personal" option and proceed with the activation.
+
+You can discuss this issue or find additional assistance in the
+[related Discord conversation](https://discord.com/channels/710946343828455455/1138586951604248666)
+or [GitHub ticket](https://github.com/game-ci/documentation/issues/408).
+
+_For future reference, activating a license from the command line as documented on
+[Unity's Manual Page](https://docs.unity3d.com/Manual/ManagingYourUnityLicense.html) might be an
+alternative solution._
+
+:::
+
+:::caution Known issue with Unity activation on gitlab-ci: empty license file
+
+If you are having troubles with Unity activation with gitlab-ci, there is currently an issue with
+recent Unity versions preventing us to retrieve a license file with actual content.
+
+For more details see the
+[following issue: get-activation-file succeeding but giving a 0kb file. Unity Version 2021.2.7f1](https://gitlab.com/game-ci/unity3d-gitlab-ci-example/-/issues/171)
+and
+[the workaround](https://gitlab.com/game-ci/unity3d-gitlab-ci-example/-/issues/171#note_974622879).
+
+Don't hesitate to contribute and implement a fix 💝
+
+:::
+
+### I cannot activate because
+
+#### 'Non-whitespace before first tag. Line: 0 Column: 1 Char: 㼼' during manual activation
+
+When activating a license on [license.unity3d.com](https://license.unity3d.com/), you may encounter
+the following error message:
+
+> Non-whitespace before first tag. Line: 0 Column: 1 Char: 㼼
+
+Here's Unity's workaround:
+
+> Unfortunately, this is a known issue our end. The relevant team are in the process of working on a
+> fix as we speak, in the meantime there is a workaround. Try renaming the `alf` file with a command
+> to convert characters on it with a `iconv` command.
+
+##### Solution
+
+```bash
+version=v2020.1.12f1 # update this according to your version and file name
+iconv -f UTF-8 -t utf-16BE Unity_${version}.alf > Unity_${version}.utf16be.alf
+```
+
+#### I use my Google account to login to Unity, how do I get my username and password?
+
+If you are using google account you can have some issue with activating unity. You just need to go
+on the unity website, settings, security and change your password. Then use your Google email and
+your new password, and it will work just fine ;)
+
+[Source](https://gitlab.com/game-ci/unity3d-gitlab-ci-example/-/issues/149)
+
+#### The digital signature is invalid.
+
+##### Error
+
+```plaintext
+Error: Code 400 while processing request (status: Cannot save ULF license file: Validation failed. The digital signature is invalid.)
+```
+
+##### Solution
+
+Depending on the CI/CD system, storing _multi-line_ file content into an environment variable can
+break the encoding. You can store the license as a base64 encoded string. Then during the pipeline
+execution, you decode it and write it to the right location afterward. For example, here is a fixed
+confirmed to be working on OneDev CI:
+
+```bash
+/bin/echo $UNITY_LICENSE > /opt/project/Unity_v2022.x.base64 \
+  && base64 -d /opt/project/Unity_v2022.x.base64 > /opt/project/Unity_v2022.x.ulf
+```
+
+Reference:
+[game-ci/documentation #300 Unity personal activation fails on OneDev CI](https://github.com/game-ci/documentation/issues/300)
+
+## My workflow isn't working because
+
+### I get `manifest for unityci/editor:2021.3.0f1-android-0 not found: manifest unknown: manifest unknown`
+
+This means the docker image trying to download from docker hub is not found.
+
+#### Solution
+
+To know which docker images are available, you can visit the list of [all supported Unity versions
+here][unity-docker-versions].
+
+In this particular case, it is also important to look for the last part of the docker image which is
+the version for GameCI. `-0` means it is the latest `v0.x.x` version of the docker images. `v0.x.x`
+and `v1.x.x` are out of date as we moved to Version 2 as shown on
+[github.com/game-ci/docker/releases](https://github.com/game-ci/docker/releases). We are not
+publishing images for `v0.x.x` or `v1.x.x` anymore.
+
+The correct image should be `unityci/editor:2021.3.0f1-android-2`.
+
+You can also test this locally:
+
+```bash
+# wrong
+docker pull unityci/editor:2021.3.0f1-android-0
+# Error response from daemon: manifest for unityci/editor:2021.3.0f1-android-0 not found: manifest unknown: manifest unknown
+
+# right
+docker pull unityci/editor:2021.3.0f1-android-2
+# 2021.3.0f1-android-2: Pulling from unityci/editor
+# [...]
+```
+
+#### Github Actions
+
+You need to make sure you are using Github Actions v3, check for the version of your actions in your
+`.github/workflows/*.yml` files.
+
+```diff
+- uses: game-ci/unity-builder@v2
++ uses: game-ci/unity-builder@v3
+```
+
+#### Gitlab CI
+
+Set the `IMAGE_VERSION` to 2 in
+[`.gitlab-ci.yml`](https://gitlab.com/game-ci/unity3d-gitlab-ci-example/-/blob/main/.gitlab-ci.yml#L12)
+
+### Scripts have compiler errors.
+
+#### Error
+
+```plaintext
+Scripts have compiler errors.
+(Filename: ./Runtime/Utilities/Argv.cpp Line: 361)
+
+Aborting batchmode due to failure:
+Scripts have compiler errors.
+```
+
+#### Solution
+
+Likely you have a missing script or assembly.
+
+Make sure your branch is clean and all files are indeed present:
+
+- No accidentally ignored files (i.e. ignored `.tmp` might match text mesh pro);
+- No tracked files that you expected to be ignored;
+- All packages listed;
+- No pre-build steps that change your project differently from how that happens locally;
+
+A good way to verify this, is to (locally) clone the Unity project in a new folder and run the build
+from there.
+
+### Branch is dirty
+
+#### Error
+
+```plaintext
+Branch is dirty. Refusing to base semantic version on uncommitted changes
+```
+
+This usually happens with GitHub actions when using unity-builder. A dirty branch means that you
+have uncommitted changes in your project. When you see this error in the logs of your pipeline, that
+means some files of your project are being modified after the build. This is not desirable as it
+could lead to unexpected results.
+
+#### Solution
+
+There are multiple options to solve this.
+
+1. Ignore the dirty branch and continue the build. We have a parameter for that:
+   [`allowDirtyBuild`](/docs/github/builder#allowdirtybuild) but ⚠️ it is not recommended.
+2. Find the files that are being modified and fix the source of the problem. **This is the
+   recommended solution**.
+
+   The log should list the files that are considered modified on the now dirty branch. First, double
+   check that these are not temporary files created by the runners themselves (see the
+   [Preparing the Project](/docs/getting-started/#preparing-the-project) section regarding
+   `.gitignore`). If the files are instead project related, locate the modified files and figure out
+   why they are being modified. Sometimes, it's because a `.meta` file gets modified by unity when
+   you open the project. If this is the case you can try this:
+
+   1. Clone your project in a new folder
+   2. Open your project with unity
+   3. Build your project
+   4. Run `git status` and see if files were modified. If so, commit them.
+
+   You can also try to download the modified files from the pipeline by exposing them as artifact
+   and looking at the diff yourself.
+
+   Something else you can try is moving and committing the file(s) to see if it makes a difference.
+
+### Gradle error
+
+#### Error
+
+```plaintext
+Error: 3.690 [ERROR] [org.gradle.launcher.daemon.server.DaemonStateCoordinator] Command execution: started DaemonCommandExecution[command = Build{id=69dbd5b3-10f2-488e-8640-977da68733f9, currentDir=/github/workspace/Temp/gradleOut/launcher}, connection = DefaultDaemonConnection: socket connection from /127.0.0.1:33657 to /127.0.0.1:43866] after 0.0 minutes of idle
+```
+
+#### Solution
+
+There are 2 possible solutions:
+
+- Remove emojis from all environment variables (and thus workflow files), or
+- Upgrade your project and workflow to use Unity editor version 2020.2 or later.
+
+### No space left on device
+
+#### Error
+
+Example when downloading an android docker image:
+
+```plaintext
+docker: failed to register layer: ApplyLayer exit status 1 stdout:  stderr: write /opt/unity/Editor/Data/PlaybackEngines/AndroidPlayer/NDK/toolchains/llvm/prebuilt/linux-x86_64/lib64/clang/9.0.8/lib/linux/x86_64/libFuzzer.a: no space left on device.
+```
+
+or when it's downloading a docker image for the windows target platform:
+
+```plaintext
+[...]
+6fad6f1176e0: Verifying Checksum
+6fad6f1176e0: Download complete
+docker: failed to register layer: write /opt/unity/Editor/Data/Resources/PackageManager/BuiltInPackages/com.unity.visualeffectgraph/Documentation~/Images/EventContexts.png: no space left on device.
+```
+
+#### Explanation
+
+When executing multiple jobs sequentially in the same workflow, there can be potential disk space
+issues. For instance, if your workflow first executes tests on one docker image, such as
+`unityci/editor:ubuntu-2022.3.4f1-linux-il2cpp-2`, and subsequently runs a build on another target
+platform, e.g., `unityci/editor:ubuntu-2022.3.4f1-windows-mono-2`, it might run out of space during
+the build phase.
+
+This happens because each job might be downloading and using its separate docker image, which can
+collectively consume a significant amount of disk space.
+
+#### Solution
+
+1. **Parallel Execution**: A straightforward workaround is to execute the tests and builds in
+   parallel rather than sequentially. This ensures that each runner (or CI job) utilizes its own
+   docker image, thereby avoiding cumulative disk usage. By structuring your CI workflow to execute
+   these jobs concurrently, each job can independently manage its disk space. You can refer to
+   [our Github 'Parallel execution of Tests and Builds' example](/docs/github/getting-started#parallel-execution-of-tests-and-builds).
+
+2. **Free Up Disk Space**: Use the
+   [Free Disk Space (Ubuntu)](https://github.com/marketplace/actions/free-disk-space-ubuntu) action
+   at the start of your workflow to clear some space on the GitHub-hosted runner. This action can be
+   especially useful if only a small amount of additional space is needed.
+
+3. **Use Self-Hosted or Cloud Runners**: If your project inherently requires more disk space than
+   what GitHub-hosted runners provide, consider switching to
+   [Self-hosted Runners](https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/about-self-hosted-runners)
+   or
+   [Cloud Runners](https://game.ci/docs/github-cloud-runner/game-ci-vs-cloud-runner#large-github-projects).
+   This would give you more control over the resources and disk space.
+
+---
+
+This revised section provides a clearer understanding of the issue and offers more directed
+solutions.
+
+## General tips
+
+These are tips that are usually applicable to problems you may encounter while working with a game
+engine and CI/CD:
+
+- Try to isolate your problem as much as possible
+- Try with a blank project, this will help you to isolate your problem. Is it a something with your
+  project specifically or is it with Unity or GameCI?
+- Try to search for error keywords in your message such as `error`, `failed`, `exception`, etc.
+- Read the error message closely to understand what's going on.
+
+## Still having problems?
+
+You can **search for existing issues**:
+
+- [GitHub Actions: game-ci/unity-actions](https://github.com/game-ci/unity-actions/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc)
+- [Documentation: game-ci/documentation](https://github.com/game-ci/documentation/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc)
+- [gitlab-ci: game-ci/unity3d-gitlab-ci-example](https://gitlab.com/game-ci/unity3d-gitlab-ci-example/-/issues)
+
+You can **open an issue** on one of the related projects:
+
+- [GitHub Actions: game-ci/unity-actions](https://github.com/game-ci/unity-actions/issues/new/choose)
+- [Documentation: game-ci/documentation](https://github.com/game-ci/documentation/issues/new/choose)
+- [gitlab-ci: game-ci/unity3d-gitlab-ci-example](https://gitlab.com/game-ci/unity3d-gitlab-ci-example/-/issues/new)
+
+You can also visit us on [discord][discord]. _Discord also has a search feature_. 😉
+
+[discord]: https://game.ci/discord
+[unity-docker-versions]: /docs/docker/versions
diff --git a/versioned_docs/version-3/10-faq/index.mdx b/versioned_docs/version-3/10-faq/index.mdx
new file mode 100644
index 00000000..4f0b4e52
--- /dev/null
+++ b/versioned_docs/version-3/10-faq/index.mdx
@@ -0,0 +1,311 @@
+---
+title: Frequently Asked Questions (FAQ)
+---
+
+## What is GameCI?
+
+GameCI is a community of game developers aiming to automate the process of creating and maintaining
+games. It is also a set of tools related to CI/CD process that can be used by game developers.
+
+## What is GameCI's goal?
+
+- Making Continuous Integration and Continuous Delivery more accessible to game developers
+- Providing tools and resources to automate game development and deployment process
+- Having fun doing it
+
+## What does CI stand for in GameCI?
+
+Did you know that `.ci` in [game.ci](https://game.ci/) is
+[the Internet country code top-level domain (ccTLD) for Côte d'Ivoire](https://en.wikipedia.org/wiki/.ci)?
+In our case, it is also the abbreviation of Continuous Integration.
+
+## What is CI/CD?
+
+Continuous Integration and Continuous Delivery is a process that allows developers to build and
+deploy software without having to manually intervene each time there is a change. Learn more on
+[Wikipedia: CI/CD](https://en.wikipedia.org/wiki/CI/CD)
+
+## What game engines are supported?
+
+Right now, GameCI only supports **[Unity](https://unity3d.com/)**. We see a bright future with
+GameCI's integration with other game engines or simply put, building a community of people who are
+interested in automation around game development.
+
+### Recommendations for other game engines
+
+For **[Unreal Engine](https://unrealengine.com/)** users, it's worth checking out
+[unrealcontainers](https://unrealcontainers.com), a great resource created by our friend
+[Adam Rehn](https://adamrehn.com/).
+
+For **[Godot](https://godotengine.org/)** developers, there are several options to consider. We
+recommend both [abarichello/godot-ci](https://github.com/abarichello/godot-ci) by
+[Artur Barichello](https://barichello.me/) and
+[firebelley/godot-export](https://github.com/firebelley/godot-export).
+
+**[MonoGame](https://www.monogame.net/)** enthusiasts should look at
+[Lean MonoGame - Automate Release](https://learn-monogame.github.io/how-to/automate-release/), an
+excellent guide from [Jean-David Moisan (Apostolique)](https://jeandavidmoisan.com/).
+
+## Why use GameCI for Unity?
+
+We want developers to concentrate on their game development, not on the stuff of CI/CD. Having a
+CI/CD pipeline setup can benefit developers, but also artists, designers, Q/A and testers by
+providing game builds faster and automatically. We have a large community of developers who are
+using GameCI on a daily basis. We have community driven documentation to help you get started.
+Everything we provide is free and open source.
+
+## How does GameCI for Unity work?
+
+We provide ready to use docker images published to docker hub with Unity pre-installed and ready to
+run. This is especially useful for CI/CD pipelines where you don't want to waste time installing
+Unity each time. The main goal is to use these images as part of a pipeline you own. You can find a
+list of [all supported Unity versions here][unity-docker-versions]. We have a documentation website
+providing complete examples of working pipelines for building, testing and publishing games using
+major CI/CD platforms such as [Github Actions](https://help.github.com/en/actions),
+[Gitlab CI](https://docs.gitlab.com/ee/ci/quick_start/) and [CircleCI](https://circleci.com/).
+
+We rely on the community to help us maintain and improve the images.
+
+## Which CI/CD platforms are supported by GameCI for Unity?
+
+Right now, we have official support for the following CI/CD platforms:
+
+- **[Github Actions](https://help.github.com/en/actions)**
+- **[Gitlab CI](https://docs.gitlab.com/ee/ci/quick_start/)**
+- **[CircleCI](https://circleci.com/)**
+
+## Can I use GameCI for Unity with `<insert other CI/CD service here>`?
+
+This question is often ask for these CI/CD services:
+
+- [Jenkins](https://jenkins.io/)
+- [Travis CI](https://www.travis-ci.com/)
+- [Bitbucket Pipelines](https://bitbucket.org/product/features/pipelines)
+- [Azure DevOps](https://azure.microsoft.com/en-us/services/devops/)
+- [AWS CodeBuild](https://aws.amazon.com/codebuild/)
+- [Drone.io](https://www.drone.io/)
+
+If the service you want to use supports Docker (the above list does), then chances are it will work,
+but we might not have official support for it. Your best bet is to translate the
+[GameCI gitlab-ci unity example project](https://unity-ci.com/docs/gitlab/example-project) to your
+desired CI/CD service provider. Caution: if this is your first time using GameCI, you might want to
+try officially supported services first. The easiest one is Github Actions.
+
+We are also working on a **GameCI for Unity CLI** which will make it easier to integrate with any
+CI/CD service. See our [Roadmap v3.0.0](https://github.com/orgs/game-ci/projects/4).
+
+### Azure devOps
+
+You might also want to have a look at [Unity Tools for Azure DevOps](https://unitydevops.com/)
+
+## Which Unity versions are supported?
+
+You can find [all supported Unity versions here][unity-docker-versions].
+
+## What Unity build targets are supported?
+
+You can find a list of succeeding pipelines for
+[supported build targets in game-ci/unity-actions's ReadMe](https://github.com/game-ci/unity-actions#unity-actions).
+
+We have linux and windows based docker images to support as many build targets as possible. This
+includes the following build targets:
+
+- WebGL
+- Windows Mono
+- Linux Mono
+- macOS Mono
+- Windows IL2CPP
+- Linux IL2CPP
+- macOS IL2CPP
+- Android
+- iOS
+- Universal Windows Platform
+- AppleTV
+
+You can find a list of build targets on Unity's website:
+[Unity Build Targets](https://docs.unity3d.com/ScriptReference/BuildTarget.html)
+
+## Do you support Unity IL2CPP builds?
+
+Yes, we do, but there are limitations. See
+[Docker images limited IL2CPP support](/docs/docker/docker-images#limited-il2cpp-support)
+
+## Do you have macOS based docker images for Unity?
+
+No, we don't as it is currently not possible to build macos based images. If this is something you
+are interested in, have a look at [macOS Containers initiative](https://macoscontainers.org/).
+
+## Do I need a mac to build for iOS?
+
+Yes, but not for all steps. You will only need a mac for building the generated Xcode project. Unity
+on linux can generate an xcode project.
+
+## Do you have docker images for alpha and beta versions of Unity?
+
+No, you can learn why by looking at the following issue:
+[game-ci/docker - Support alpha and beta versions of Unity #50](https://github.com/game-ci/docker/issues/50)
+
+## Unity just released a new version, do you have a docker image for it?
+
+Most likely yes. We have automated pipelines watching every 15 minutes for new releases of Unity.
+Jobs are then created on github to build and push the docker images to docker hub. You can find the
+status of the images on [the supported Unity versions page][unity-docker-versions].
+
+## How long does it take for a new version of Unity to become available as a Docker image?
+
+We have automated pipelines that check for new releases of Unity **every 15 minutes**. Once a new
+release is detected, a job is created on GitHub to build and publish a new Docker image to Docker
+Hub. When the version is available on the Unity's download page, it usually takes a few hours for
+the new version to become available on Docker Hub. _However, the exact time it takes for a new
+version to become available as a Docker image can vary depending on several factors, such as the
+time it takes to build the images, the availability of the new version on the Unity download page._
+
+We have a discord channel which you can watch to be notified of new versions detected by our bot
+here: [#new-versions](https://discord.com/channels/710946343828455455/731947345478156391). You will
+need to join our [discord server](https://game.ci/discord) first.
+
+## How does the Docker image publication process work?
+
+The Docker image publication process involves several steps. First, we detect new releases of Unity
+based on [Unity's Archive page](https://unity.com/releases/editor/archive) and we trigger a build
+job on GitHub. This happens in the
+[GameCI Versioning Backend](https://github.com/game-ci/versioning-backend) project. Next, the build
+job uses Unity Hub to install Unity and the required packages and builds new Docker images for each
+supported target platforms. This happens in the
+[Docker images for Unity](https://github.com/game-ci/docker) project. The new images are tagged and
+pushed to Docker Hub, where they are publicly available for download.
+
+## Where is the source of truth for the process of publishing Docker images?
+
+The source of truth for the process of publishing Docker images is
+[Unity's Archive page](https://unity.com/releases/editor/archive). We use automated scripts to
+detect new releases on this page and trigger the build process for new Docker images. However, Unity
+may occasionally release updates that are not immediately available on their download page, which
+can cause a delay in the availability of new Docker images.
+
+If you are currently using a recent unity version from Unity Hub that is not yet available on the
+[Unity's Archive page](https://unity.com/releases/editor/archive), you can usually roll back to
+previous version which is most likely already available, or you can wait a few hours until Unity
+publishes the new version on its download page and wait for our pipelines to finish building and
+publishing the images.
+
+## How does Unity activation work?
+
+### The `machine-id`
+
+Unity has several activation methods, but they all share the same concept. Unity uses the
+`machine-id` to identify the user. This is usually unique per machine. On linux, the `machine-id` is
+located here:
+
+- `/etc/machine-id`
+- `/var/lib/dbus/machine-id`
+
+Using a different `machine-id` will cause Unity to require a new activation.
+
+To make it easier to use GameCI, we hardcoded the `machine-id` in all the docker images we publish,
+[see Ubuntu's base Dockerfile](https://github.com/game-ci/docker/blob/main/images/ubuntu/base/Dockerfile#L67-L68).
+
+This makes it easier to upgrade from one version of Unity to another as you will not need to
+re-activate.
+
+### I'm having troubles with Unity activation, what should I do?
+
+Have a look at the Have a look at the [troubleshooting / common issues][common-issues] page.
+
+## Can I use a free Unity license to build my project?
+
+Yes
+
+## Can I use a Unity Pro serial to build my project?
+
+Yes
+
+## Can I run multiple builds in parallel using Unity?
+
+Yes, but have a look at
+[Limitations: Concurrent builds on Windows and MacOS](/docs/docker/docker-images#concurrent-builds-on-windows-and-macos)
+
+## How much does it cost to use GameCI for Unity?
+
+GameCI is free and open source software. Depending on the CI/CD service you use, you can pay for
+build minutes but you can also use your own machines to build and test your project.
+
+Most CI/CD service providers offer a free tier with free build minutes for private projects. If you
+are building an open source project, it's often all free. ❤️
+
+### Github Actions
+
+- [About billing for GitHub Actions](https://docs.github.com/en/billing/managing-billing-for-github-actions/about-billing-for-github-actions)
+- [About self-hosted runners](https://docs.github.com/en/actions/hosting-your-own-runners/about-self-hosted-runners)
+
+### Gitlab CI
+
+- [Gitlab CI pricing](https://about.gitlab.com/pricing/)
+- [Gitlab CI self-hosted runners](https://docs.gitlab.com/runner/)
+
+### CircleCI
+
+- [CircleCI pricing](https://circleci.com/pricing/)
+- [CircleCI self-hosted runners](https://circleci.com/execution-environments/runner/)
+
+## Is GameCI free?
+
+Yes, GameCI is free and will always be free. The software we develop is open source and under the
+[MIT license](https://opensource.org/licenses/MIT).
+
+## I have an issue when using GameCI, how can I get in touch with you?
+
+First you should look at the [documentation](/docs) and the [troubleshooting / common
+issues][common-issues] page. You can also search in issues of related project on
+[github.com/game-ci/](https://github.com/game-ci/) or
+[gitlab.com/game-ci/](https://gitlab.com/game-ci/). If you still have problems, you can open an
+issue on the related project. Still unsure? You can visit us on our [discord server][discord].
+
+## Why is it so long to get support?
+
+We are a small community of developers who are trying to make the world a better place. We are not
+doing this for the money and no one is being paid for the support. This is all a community effort to
+end up with games that are less buggy ;). Don't hold your breath and be nice with people helping
+you. ❤️
+
+## Do you offer premium support?
+
+We don't offer premium support. We do offer free support for the community as a best-effort.
+
+## I have too much money, and I like your projects, how can I help?
+
+We have an [opencollective page](https://opencollective.com/game-ci) where you can donate. The
+donations are used to pay for the costs of the infrastructure, domains and the servers (which we
+kept to a very reasonable price, thanks to all the free services for open source projects). We might
+also use the money to pay for improving our visuals or anything that could help us become a better
+community. It is also possible that we send gifts to major contributors, who knows? ❤️
+
+## Do you have a roadmap?
+
+Yes, see our [Roadmap v3.0.0](https://github.com/orgs/game-ci/projects/4).
+
+## Who made GameCI?
+
+GameCI is a collaborative effort. We are a community of developers who are passionate about good
+practice and automation. You can find a list of our contributors on
+[github.com/game-ci/](https://github.com/game-ci/) in each project.
+
+The core maintainers of GameCI are:
+
+- [Gabriel "GabLeRoux" Le Breton](https://gableroux.com), founder of GameCI, Co-owner at
+  [Totema Studio](https://totemastudio.com), full time dev at [TLM](https://tlmgo.com/) and lecturer
+  at [UQAC](https://uqac.ca/).
+- [Dick "Webber" Webbink](https://takken.io/), founder of GameCI and Senior Software Engineer at
+  [Just Eat Takeaway.com](https://www.justeattakeaway.com/).
+- [Markus "Fisher" Dugdale](https://www.linkedin.com/in/markus-dugdale-136112136/) Lead game
+  developer [@bossastudios](https://www.bossastudios.com/), former product manager @unity3d, arma
+  modder. Game ai, networking, terrain.
+- [David Finol](https://davidmfinol.website/), creator of
+  [Card Game Simulator](https://www.cardgamesimulator.com/) and Software Engineer at
+  [JPMorgan Chase & Co](https://www.jpmorganchase.com/).
+
+See [About us](https://game.ci/about) for more details.
+
+[unity-docker-versions]: /docs/docker/versions
+[discord]: https://game.ci/discord
+[common-issues]: /docs/troubleshooting/common-issues
diff --git a/versioned_docs/version-3/11-circleci/01-getting-started.mdx b/versioned_docs/version-3/11-circleci/01-getting-started.mdx
new file mode 100644
index 00000000..60dca692
--- /dev/null
+++ b/versioned_docs/version-3/11-circleci/01-getting-started.mdx
@@ -0,0 +1,149 @@
+---
+toc_max_heading_level: 4
+---
+
+# Getting started
+
+This guide will help you test and build your Unity project using our
+[Unity Orb](https://circleci.com/developer/orbs/orb/game-ci/unity).
+
+## Overall steps
+
+1. Understand how CircleCI works.
+2. Set up a workflow for your project.
+3. Download the artifacts from your first build.
+
+## CircleCI
+
+If you are not familiar with CircleCI, read the official documentation on how to set up a
+[workflow](https://circleci.com/docs/getting-started). The following steps will assume you have done
+so.
+
+#### Unity Orb
+
+[Orbs](https://circleci.com/orbs/) are reusable snippets of code that help automate repeated
+processes, speed up project setup and make it easy to integrate with third-party tools.
+
+To streamline the process of testing and building Unity projects in CircleCI, we provide the
+[Unity Orb](https://circleci.com/developer/orbs/orb/game-ci/unity) — a certified orb capable of
+caching dependencies, storing artifacts, collecting test data and running on multiple
+[executors](/docs/circleci/executors).
+
+In the sections below, you will learn how to import and use the orb to test and build your project
+for different target platforms.
+
+_**Note:** the Orb is a work in progress. It doesn't have feature parity with our GitHub
+[Builder Action](/docs/github/builder) yet._
+
+## Activation
+
+To build and test projects, you need an
+[activated license](https://docs.unity3d.com/Manual/LicensesAndActivation.html). The Unity Orb will
+handle the activation process if you have all necessary environment variables set in the job's
+context. If you proceed to [set up your workflow](#setting-up-a-workflow) without doing so, your job
+will fail. For more details, head to the [Activation](/docs/circleci/activation) section.
+
+## Setting up a workflow
+
+Create a `.circleci/config.yml` file in the root of your repository and follow these steps:
+
+1. Import the [Unity Orb](https://circleci.com/developer/orbs/orb/game-ci/unity) and fix it to a
+   `minor` version (e.g. `1.1`) to avoid receiving updates with breaking changes:
+
+```yaml
+version: 2.1
+
+orbs:
+  unity: game-ci/unity@x.y
+```
+
+2. Include a [build job](/docs/circleci/build) in your workflow and modify the
+   [parameters](/docs/circleci/build#parameters) to accommodate your project needs:
+
+```yaml
+version: 2.1
+
+orbs:
+  unity: game-ci/unity@x.y
+
+workflows:
+  build-unity-project:
+    jobs:
+      - unity/build:
+          name: 'build-linux64-il2cpp'
+          step-name: 'Build StandaloneLinux64'
+          unity-license-var-name: 'UNITY_ENCODED_LICENSE'
+          unity-username-var-name: 'UNITY_USERNAME'
+          unity-password-var-name: 'UNITY_PASSWORD'
+          executor:
+            name: 'unity/ubuntu'
+            target_platform: 'linux-il2cpp'
+            editor_version: '2021.3.1f1'
+            resource_class: 'large'
+          project-path: 'Unity2D-Demo-Game-CI-CD/src'
+          build-target: StandaloneLinux64
+          compress: true
+          context: unity
+```
+
+3. Optionally, include a [test job](/docs/circleci/test) in your workflow:
+
+```yaml
+version: 2.1
+
+orbs:
+  unity: game-ci/unity@x.y
+
+workflows:
+  test-and-build-unity-project:
+    jobs:
+      - unity/test:
+          name: 'test-linux'
+          step-name: 'Check if tests run and results are uploaded'
+          unity-license-var-name: 'UNITY_ENCODED_LICENSE'
+          unity-username-var-name: 'UNITY_USERNAME'
+          unity-password-var-name: 'UNITY_PASSWORD'
+          executor:
+            name: 'unity/ubuntu'
+            target_platform: 'linux-il2cpp'
+            editor_version: '2021.3.1f1'
+            resource_class: 'medium'
+          project-path: 'Unity2D-Demo-Game-CI-CD/src'
+          test-platform: 'playmode'
+          context: unity
+      - unity/build: ...
+```
+
+You can add it as a [requirement](https://circleci.com/docs/configuration-reference#requires) in the
+build job to prevent it from running in case of failure:
+
+```yaml
+version: 2.1
+
+orbs:
+  unity: game-ci/unity@x.y
+
+workflows:
+  test-and-build-unity-project:
+    jobs:
+      - unity/test:
+          name: 'test-linux'
+          ...
+      - unity/build:
+          ...
+          requires:
+            - test-linux
+```
+
+4. Commit and push the new workflow.
+
+## Downloading the artifacts
+
+1. Navigate to your project in the CircleCI [web app](https://app.circleci.com/).
+
+2. Identify the pipeline triggered by your changes and open the `build-linux64-il2cpp` job.
+
+3. Navigate to the `ARTIFACTS` tab and download the `UnityBuild-StandaloneLinux64.tar.gz` file.
+
+4. Extract the `UnityBuild-StandaloneLinux64.tar.gz` file and you will have your first build using
+   the Unity Orb 🚀.
diff --git a/versioned_docs/version-3/11-circleci/02-activation.mdx b/versioned_docs/version-3/11-circleci/02-activation.mdx
new file mode 100644
index 00000000..3b2da252
--- /dev/null
+++ b/versioned_docs/version-3/11-circleci/02-activation.mdx
@@ -0,0 +1,135 @@
+---
+toc_max_heading_level: 4
+---
+
+# Activation
+
+The orb uses a Unity Editor instance to test and build your projects. These operations require the
+instance to be activated before each job you run.
+
+Unity separates its licenses between `Personal` and `Professional`. The former applies to the _free_
+and the latter to the _Pro_ and _Plus_ versions. Based on your use case proceed to the
+[Personal](#personal-license) or [Professional](#professional-license) license section.
+
+## Personal license
+
+Follow these steps if you are using Unity's _free_ version.
+
+> _**Note:** Do NOT follow the steps for the personal license if you have a professional license._
+
+#### Mental model
+
+1. Use the Unity Orb to create an activation file.
+2. Use the activation file to acquire a license file from the Unity website.
+3. Encode the license file and save it in a CircleCI Context.
+
+#### Acquiring an activation file
+
+Add the workflow below to a [project set up in CircleCI](https://circleci.com/docs/getting-started).
+As long as you can access it in the CircleCI web app and download its artifacts, it can be any
+project.
+
+```yaml
+version: 2.1
+
+orbs:
+  unity: game-ci/unity@x.y
+
+workflows:
+  create-unity-activation-file:
+    jobs:
+      - unity/create-activation-file
+```
+
+If you require an activation file for a specific version of the Unity Editor, you need to provide
+its version number as an argument. The available versions can be found on our
+[versions](/docs/docker/versions) page.
+
+```yaml
+version: 2.1
+
+orbs:
+  unity: game-ci/unity@x.y
+
+workflows:
+  create-unity-activation-file:
+    jobs:
+      - unity/create-activation-file:
+          editor_version: 2022.1.11f1
+```
+
+Commit and push the new workflow and navigate to your project in the CircleCI web app. Identify the
+pipeline triggered by your changes and open the `unity/create-activation-file` job. In the
+`ARTIFACTS` tab, you will encounter `Unity.alf`; this is your activation file. Download it and
+proceed to the following sub-section.
+
+#### Acquiring the license file
+
+1. Navigate to the [manual activation](https://license.unity3d.com/manual) page and upload the
+   `Unity.alf` activation file.
+2. Answer the prompted questions.
+3. Download the license file (Unity_v20XX.x.ulf).
+
+> _Note: It is fine if the version number in the file name does not match your exact Unity version._
+
+#### Encoding the license
+
+Encode the contents of your `Unity_v20XX.x.ulf` file to base64. If you have the `base64` command
+line utility you can use:
+
+```
+cat Unity_v20XX.x.ulf | base64 -w 0
+```
+
+#### Configuring your Context
+
+1. Navigate to [CircleCI](https://app.circleci.com/) ⇢ `Organization Settings` ⇢ `Contexts` ⇢
+   `Create Context` and choose a name for your context (e.g. `myProjectContext`). Alternatively,
+   open an existing Context that you would like to use.
+2. Create the following environment variables:
+   - `UNITY_ENCODED_LICENSE` - _(Paste the content from the
+     [Encoding the License](#encoding-the-license) section here)_
+   - `UNITY_USERNAME` - _(Add the email address that you use to log in to Unity)_
+   - `UNITY_PASSWORD` - _(Add the password that you use to log in to Unity)_
+3. Remove or disable the job you included to acquire your activation file. It's no longer necessary.
+
+> _**Note:** When changing the Unity version, you may need to repeat the same process._
+
+## Professional license
+
+Follow these steps if you are using Unity's _Pro_ or _Plus_ version.
+
+> _**Note:** Do NOT follow the steps for the professional license if you have a personal license._
+
+1. Get your Serial Key from the [subscriptions page](https://id.unity.com/en/subscriptions).
+2. Navigate to [CircleCI](https://app.circleci.com/) ⇢ `Organization Settings` ⇢ `Contexts` ⇢
+   `Create Context` and choose a name for your context (e.g. `myProjectContext`). Alternatively,
+   open an existing Context that you would like to use.
+3. Create the following environment variables:
+   - `UNITY_SERIAL` - _(Paste the serial acquired in **step 1** here. It should look like this:
+     `XX-XXXX-XXXX-XXXX-XXXX-XXXX`)_
+   - `UNITY_USERNAME` - _(Add the email address that you use to log in to Unity)_
+   - `UNITY_PASSWORD` - _(Add the password that you use to log in to Unity)_
+
+## Next steps
+
+Now you are prepared to start [testing](/docs/circleci/test) and [building](/docs/circleci/build)
+your Unity project. However, remember to reference your context in every job you run; otherwise,
+they will fail:
+
+```yaml
+version: 2.1
+
+orbs:
+  unity: game-ci/unity@x.y
+
+workflows:
+  build-unity-project:
+    jobs:
+      - unity/test:
+          ...
+          context: unity
+      - unity/build:
+          ...
+          context: unity
+```
diff --git a/versioned_docs/version-3/11-circleci/03-build.mdx b/versioned_docs/version-3/11-circleci/03-build.mdx
new file mode 100644
index 00000000..a5ed15e6
--- /dev/null
+++ b/versioned_docs/version-3/11-circleci/03-build.mdx
@@ -0,0 +1,816 @@
+---
+toc_max_heading_level: 4
+---
+
+# Build
+
+The Unity Orb provides the
+[build job](https://circleci.com/developer/orbs/orb/game-ci/unity#jobs-build) to facilitate the
+process of building your Unity project for multiple platforms.
+
+### Parameters
+
+Below you will find information on each parameter that can be passed to the build job.
+
+#### build-method
+
+The command used to build your project. A valid `build-method` contains the path to a `static`
+method in a class inside the `Assets/Editor` directory. The Unity Orb will fall back to the
+[default script](https://github.com/game-ci/unity-orb/blob/main/src/dependencies/unity-builder/BuildCommand.cs)
+if this parameter is left empty.
+
+To illustrate, if you were to modify the default script and use it to build your project, you would
+need to place its content in `Assets/Editor/MyBuildMethod.cs` and pass `BuildCommand.PerformBuild`
+as your `build-method` value.
+
+If your custom build method requires additional parameters, see
+[custom-parameters](#custom-parameters).
+
+```yaml
+version: 2.1
+
+orbs:
+  unity: game-ci/unity@x.y
+
+workflows:
+  build-unity-project:
+    jobs:
+      - unity/build:
+          build-method: 'BuildCommand.PerformBuild'
+```
+
+- _Default_: `N/A`
+- _Required_: `false`
+- _Type_: `string`
+
+#### build-name
+
+Your build's name. If left blank, the build will be named after the target platform.
+
+```yaml
+version: 2.1
+
+orbs:
+  unity: game-ci/unity@x.y
+
+workflows:
+  build-unity-project:
+    jobs:
+      - unity/build:
+          build-name: 'MyUnityProject'
+```
+
+- _Default_: `N/A`
+- _Required_: `false`
+- _Type_: `string`
+
+#### build-target
+
+The platform on which you want to run your game or application. Available targets can be found in
+the Unity Editor
+[documentation](https://docs.unity3d.com/2022.2/Documentation/ScriptReference/BuildTarget.html).
+
+```yaml
+version: 2.1
+
+orbs:
+  unity: game-ci/unity@x.y
+
+workflows:
+  build-unity-project:
+    jobs:
+      - unity/build:
+          build-target: 'StandaloneLinux64'
+```
+
+- _Default_: `N/A`
+- _Required_: `true`
+- _Type_: `string`
+
+#### compress
+
+Whether to compress the build output to a `.tar.gz` file. Set it to `true` if you want to download
+the build artifacts from the CircleCI web app. Otherwise, you will have to download each file
+individually. If set to `false` for
+[decompressed WebGL](https://docs.unity3d.com/Manual/webgl-deploying.html) builds, the built project
+can be run directly from the GameCI dashboard.
+
+```yaml
+version: 2.1
+
+orbs:
+  unity: game-ci/unity@x.y
+
+workflows:
+  build-unity-project:
+    jobs:
+      - unity/build:
+          compress: true
+```
+
+- _Default_: `true`
+- _Required_: `false`
+- _Type_: `boolean`
+
+#### custom-parameters
+
+Additional parameters for the Unity CLI. This is useful if you want to change Unity's
+[build options](https://docs.unity3d.com/ScriptReference/BuildOptions.html) or pass custom
+parameters to your [build method](#build-method).
+
+The parameters must be separated by space and must be in the format `-key value` or `-key` for
+booleans. Environment variables are supported and will be expanded in runtime.
+
+```yaml
+version: 2.1
+
+orbs:
+  unity: game-ci/unity@x.y
+
+workflows:
+  build-unity-project:
+    jobs:
+      - unity/build:
+          custom-parameters:
+            '-customParam1 potato -customParam2 tomato -customParam3 $CIRCLE_WORKFLOW_ID
+            -DetailedBuildReport'
+```
+
+- _Default_: `N/A`
+- _Required_: `false`
+- _Type_: `string`
+
+#### executor
+
+The executor that you want to run your build job on. Bear in mind that projects using `IL2CPP` for a
+[scripting backend](https://docs.unity3d.com/Manual/scripting-backends.html) should run on the same
+OS as the [build target](#build-target). For example, if you want to build for macOS using `IL2CPP`,
+then you must use the [macos](/docs/circleci/executors#macos) or
+[macos-runner](/docs/circleci/executors#macos-runner) executor.
+
+Each executor has its set of parameters. See the [Executors](/docs/circleci/executors) section for
+more details.
+
+```yaml
+version: 2.1
+
+orbs:
+  unity: game-ci/unity@x.y
+
+workflows:
+  build-unity-project:
+    jobs:
+      - unity/build:
+          executor:
+            name: 'unity/ubuntu'
+            target_platform: 'linux-il2cpp'
+            editor_version: '2021.3.2f1'
+            resource_class: 'large'
+```
+
+- _Default_: `N/A`
+- _Required_: `true`
+- _Type_: `executor`
+
+#### no_output_timeout
+
+Elapsed time without output before the job is canceled and stopped. The value can be in hours,
+minutes or seconds - a digit followed by h, m or s respectively. Consider increasing it if you see
+this error:
+
+> Too long with no output (exceeded 20m0s): context deadline exceeded
+
+```yaml
+version: 2.1
+
+orbs:
+  unity: game-ci/unity@x.y
+
+workflows:
+  build-unity-project:
+    jobs:
+      - unity/build:
+          no_output_timeout: 30m
+```
+
+- _Default_: `20m`
+- _Required_: `false`
+- _Type_: `string`
+
+#### project-path
+
+If your project sits at the root of your repository, leave it to the default value. Otherwise, enter
+the path to your Unity project. It should be the directory that has the "Assets" folder inside it.
+
+```yaml
+version: 2.1
+
+orbs:
+  unity: game-ci/unity@x.y
+
+workflows:
+  build-unity-project:
+    jobs:
+      - unity/build:
+          project-path: 'Unity2D-Demo-Game-CI-CD/src'
+```
+
+- _Default_: `.`
+- _Required_: `false`
+- _Type_: `string`
+
+#### return-license
+
+Whether to manually return the Unity license after the build job is finished. This is usually
+unnecessary and only useful when running into an unrecoverable error while having a license active.
+Additionally, Unity only allows returning professional licenses.
+
+```yaml
+version: 2.1
+
+orbs:
+  unity: game-ci/unity@x.y
+
+workflows:
+  build-unity-project:
+    jobs:
+      - unity/build:
+          return-license: true
+```
+
+- _Default_: `false`
+- _Required_: `false`
+- _Type_: `boolean`
+
+#### step-name
+
+Specify a custom step name to be shown in the CircleCI web app.
+
+```yaml
+version: 2.1
+
+orbs:
+  unity: game-ci/unity@x.y
+
+workflows:
+  build-unity-project:
+    jobs:
+      - unity/build:
+          step-name: 'Build my Unity project'
+```
+
+- _Default_: `Build the project`
+- _Required_: `false`
+- _Type_: `string`
+
+#### store-artifacts
+
+Whether to store the build output. If set to `false` you won't be able to download your build in the
+CircleCI web app.
+
+```yaml
+version: 2.1
+
+orbs:
+  unity: game-ci/unity@x.y
+
+workflows:
+  build-unity-project:
+    jobs:
+      - unity/build:
+          store-artifacts: false
+```
+
+- _Default_: `true`
+- _Required_: `false`
+- _Type_: `boolean`
+
+#### fetch-submodules
+
+Whether to fetch git submodules relating to the project repository.
+
+```yaml
+version: 2.1
+
+orbs:
+  unity: game-ci/unity@x.y
+
+workflows:
+  build-unity-project:
+    jobs:
+      - unity/build:
+          fetch-submodules: true
+```
+
+- _Default_: `false`
+- _Required_: `false`
+- _Type_: `boolean`
+
+#### unity-license-var-name
+
+The name of the environment variable holding the license set in your
+[Context](/docs/circleci/activation#preparing-the-context). Only required when using a Personal
+License. See [activation](/docs/circleci/activation) for more details.
+
+```yaml
+version: 2.1
+
+orbs:
+  unity: game-ci/unity@x.y
+
+workflows:
+  build-unity-project:
+    jobs:
+      - unity/build:
+          unity-license-var-name: 'UNITY_ENCODED_LICENSE'
+```
+
+- _Default_: `UNITY_ENCODED_LICENSE`
+- _Required_: `false`
+- _Type_: `env_var_name`
+
+#### unity-password-var-name
+
+The name of the environment variable holding the password set in your
+[Context](/docs/circleci/activation#preparing-the-context). See
+[activation](/docs/circleci/activation) for more details.
+
+```yaml
+version: 2.1
+
+orbs:
+  unity: game-ci/unity@x.y
+
+workflows:
+  build-unity-project:
+    jobs:
+      - unity/build:
+          unity-password-var-name: 'UNITY_PASSWORD'
+```
+
+- _Default_: `UNITY_PASSWORD`
+- _Required_: `false`
+- _Type_: `env_var_name`
+
+#### unity-serial-var-name
+
+The name of the environment variable holding the serial set in your
+[Context](/docs/circleci/activation#preparing-the-context). Only required when using a Pro or Plus
+License. See [activation](/docs/circleci/activation) for more details.
+
+```yaml
+version: 2.1
+
+orbs:
+  unity: game-ci/unity@x.y
+
+workflows:
+  build-unity-project:
+    jobs:
+      - unity/build:
+          unity-serial-var-name: 'UNITY_SERIAL'
+```
+
+- _Default_: `UNITY_SERIAL`
+- _Required_: `false`
+- _Type_: `env_var_name`
+
+#### unity-username-var-name
+
+The name of the environment variable holding the username set in your
+[Context](/docs/circleci/activation#preparing-the-context). See
+[Activation](/docs/circleci/activation) for more details.
+
+```yaml
+version: 2.1
+
+orbs:
+  unity: game-ci/unity@x.y
+
+workflows:
+  build-unity-project:
+    jobs:
+      - unity/build:
+          unity-username-var-name: 'UNITY_USERNAME'
+```
+
+- _Default_: `UNITY_USERNAME`
+- _Required_: `false`
+- _Type_: `env_var_name`
+
+### Examples
+
+In this section, you will find examples of workflows using this job. However, notice that the
+separation used in the examples is only for the sake of visualisation. You can build for all target
+platforms in the same workflow. All examples are based on CircleCI's
+[Demo Project](https://github.com/CircleCI-Public/Unity2D-Demo-Game-CI-CD).
+
+#### Personal License
+
+This example shows how to build your project for several platforms using a Personal License.
+
+##### IL2CPP
+
+```yaml
+version: 2.1
+
+orbs:
+  unity: game-ci/unity@x.y
+
+workflows:
+  build-unity-project:
+    jobs:
+      # Linux IL2CPP
+      - unity/build:
+          name: 'build-linux64-il2cpp'
+          step-name: 'Build StandaloneLinux64'
+          unity-license-var-name: 'UNITY_ENCODED_LICENSE'
+          unity-username-var-name: 'UNITY_USERNAME'
+          unity-password-var-name: 'UNITY_PASSWORD'
+          executor:
+            name: 'unity/ubuntu'
+            target_platform: 'linux-il2cpp'
+            editor_version: '2021.3.1f1'
+            resource_class: 'large'
+          project-path: 'Unity2D-Demo-Game-CI-CD/src'
+          build-target: StandaloneLinux64
+          compress: true
+          context: unity
+
+      # Windows IL2CPP
+      - unity/build:
+          name: 'build-Windows64-il2cpp'
+          step-name: 'Build StandaloneWindows64 il2cpp'
+          unity-license-var-name: 'UNITY_ENCODED_LICENSE'
+          unity-username-var-name: 'UNITY_USERNAME'
+          unity-password-var-name: 'UNITY_PASSWORD'
+          executor:
+            name: 'unity/windows-2019'
+            size: 'large'
+            editor_version: '2021.3.2f1'
+            target_platform: 'windows-il2cpp'
+          project-path: 'Unity2D-Demo-Game-CI-CD/src'
+          build-target: StandaloneWindows64
+          compress: true
+          context: unity
+
+      # macOS IL2CPP
+      - unity/build:
+          name: 'build-osx-il2cpp'
+          step-name: 'Build macOS IL2CPP'
+          unity-license-var-name: 'UNITY_ENCODED_LICENSE'
+          unity-username-var-name: 'UNITY_USERNAME'
+          unity-password-var-name: 'UNITY_PASSWORD'
+          executor:
+            name: 'unity/macos'
+            resource_class: 'large'
+            editor_version: '2021.3.2f1'
+          project-path: 'Unity2D-Demo-Game-CI-CD/src'
+          build-target: StandaloneWindows64
+          compress: true
+          context: unity
+```
+
+##### Mono
+
+```yaml
+version: 2.1
+
+orbs:
+  unity: game-ci/unity@x.y
+
+workflows:
+  build-unity-project:
+    jobs:
+      # Linux Mono
+      - unity/build:
+          name: 'build-linux64-mono'
+          step-name: 'Build StandaloneLinux64'
+          unity-license-var-name: 'UNITY_ENCODED_LICENSE'
+          unity-username-var-name: 'UNITY_USERNAME'
+          unity-password-var-name: 'UNITY_PASSWORD'
+          executor:
+            name: 'unity/ubuntu'
+            target_platform: 'base'
+            editor_version: '2021.3.1f1'
+            resource_class: 'large'
+          project-path: 'Unity2D-Demo-Game-CI-CD/src'
+          build-target: StandaloneLinux64
+          compress: true
+          context: unity
+
+      # Windows Mono
+      - unity/build:
+          name: 'build-Windows64-mono'
+          step-name: 'Build StandaloneWindows64'
+          unity-license-var-name: 'UNITY_ENCODED_LICENSE'
+          unity-username-var-name: 'UNITY_USERNAME'
+          unity-password-var-name: 'UNITY_PASSWORD'
+          executor:
+            name: 'unity/ubuntu'
+            target_platform: 'windows-mono'
+            editor_version: '2021.3.2f1'
+            resource_class: 'large'
+          project-path: 'Unity2D-Demo-Game-CI-CD/src'
+          build-target: 'StandaloneWindows64'
+          context: unity
+
+      # macOS Mono
+      - unity/build:
+          name: 'build-osx-mono'
+          step-name: 'Build StandaloneOSX'
+          unity-license-var-name: 'UNITY_ENCODED_LICENSE'
+          unity-username-var-name: 'UNITY_USERNAME'
+          unity-password-var-name: 'UNITY_PASSWORD'
+          executor:
+            name: 'unity/ubuntu'
+            target_platform: 'mac-mono'
+            editor_version: '2021.3.2f1'
+            resource_class: 'large'
+          project-path: 'Unity2D-Demo-Game-CI-CD/src'
+          build-target: 'StandaloneOSX'
+          context: unity
+```
+
+##### Other Platforms
+
+```yaml
+version: 2.1
+
+orbs:
+  unity: game-ci/unity@x.y
+
+workflows:
+  build-unity-project:
+    jobs:
+      # WebGL
+      - unity/build:
+          name: 'build-webgl'
+          step-name: 'Build WebGL'
+          unity-license-var-name: 'UNITY_ENCODED_LICENSE'
+          unity-username-var-name: 'UNITY_USERNAME'
+          unity-password-var-name: 'UNITY_PASSWORD'
+          executor:
+            name: 'unity/ubuntu'
+            target_platform: 'webgl'
+            editor_version: '2021.3.1f1'
+            resource_class: 'large'
+          project-path: 'Unity2D-Demo-Game-CI-CD/src'
+          build-target: 'WebGL'
+          compress: false
+          context: unity
+
+      # Android
+      - unity/build:
+          name: 'build-android'
+          step-name: 'Build Android'
+          unity-license-var-name: 'UNITY_ENCODED_LICENSE'
+          unity-username-var-name: 'UNITY_USERNAME'
+          unity-password-var-name: 'UNITY_PASSWORD'
+          executor:
+            name: 'unity/ubuntu'
+            target_platform: 'android'
+            editor_version: '2021.3.2f1'
+            resource_class: 'large'
+          project-path: 'Unity2D-Demo-Game-CI-CD/src'
+          build-target: 'Android'
+          context: unity
+
+      # iOS
+      - unity/build:
+          name: 'build-ios'
+          step-name: 'Build iOS'
+          unity-license-var-name: 'UNITY_ENCODED_LICENSE'
+          unity-username-var-name: 'UNITY_USERNAME'
+          unity-password-var-name: 'UNITY_PASSWORD'
+          executor:
+            name: 'unity/ubuntu'
+            target_platform: 'ios'
+            editor_version: '2021.3.2f1'
+            resource_class: 'large'
+          project-path: 'Unity2D-Demo-Game-CI-CD/src'
+          build-target: 'iOS'
+          context: unity
+
+      # tvOS
+      - unity/build:
+          name: 'build-tvOS'
+          step-name: "Build Apple's tvOS"
+          unity-license-var-name: 'UNITY_ENCODED_LICENSE'
+          unity-username-var-name: 'UNITY_USERNAME'
+          unity-password-var-name: 'UNITY_PASSWORD'
+          executor:
+            name: 'unity/windows-2019'
+            size: 'large'
+            editor_version: '2021.3.2f1'
+            target_platform: 'appletv'
+          project-path: 'Unity2D-Demo-Game-CI-CD/src'
+          build-target: tvOS
+          compress: true
+          context: unity
+```
+
+#### Professional License
+
+This example shows how to build your project for several platforms using a Pro License.
+
+##### IL2CPP
+
+```yaml
+version: 2.1
+
+orbs:
+  unity: game-ci/unity@x.y
+
+workflows:
+  build-unity-project:
+    jobs:
+      # Linux IL2CPP
+      - unity/build:
+          name: 'build-linux64-il2cpp'
+          step-name: 'Build StandaloneLinux64'
+          unity-serial-var-name: 'UNITY_SERIAL'
+          unity-username-var-name: 'UNITY_USERNAME'
+          unity-password-var-name: 'UNITY_PASSWORD'
+          executor:
+            name: 'unity/ubuntu'
+            target_platform: 'linux-il2cpp'
+            editor_version: '2021.3.1f1'
+            resource_class: 'large'
+          project-path: 'Unity2D-Demo-Game-CI-CD/src'
+          build-target: StandaloneLinux64
+          compress: true
+          context: unity
+
+      # Windows IL2CPP
+      - unity/build:
+          name: 'build-Windows64-il2cpp'
+          step-name: 'Build StandaloneWindows64 il2cpp'
+          unity-serial-var-name: 'UNITY_SERIAL'
+          unity-username-var-name: 'UNITY_USERNAME'
+          unity-password-var-name: 'UNITY_PASSWORD'
+          executor:
+            name: 'unity/windows-2019'
+            size: 'large'
+            editor_version: '2021.3.2f1'
+            target_platform: 'windows-il2cpp'
+          project-path: 'Unity2D-Demo-Game-CI-CD/src'
+          build-target: StandaloneWindows64
+          compress: true
+          context: unity
+
+      # macOS IL2CPP
+      - unity/build:
+          name: 'build-osx-il2cpp'
+          step-name: 'Build macOS IL2CPP'
+          unity-serial-var-name: 'UNITY_SERIAL'
+          unity-username-var-name: 'UNITY_USERNAME'
+          unity-password-var-name: 'UNITY_PASSWORD'
+          executor:
+            name: 'unity/macos'
+            resource_class: 'large'
+            editor_version: '2021.3.2f1'
+          project-path: 'Unity2D-Demo-Game-CI-CD/src'
+          build-target: StandaloneOSX
+          compress: true
+          context: unity
+```
+
+##### Mono
+
+```yaml
+version: 2.1
+
+orbs:
+  unity: game-ci/unity@x.y
+
+workflows:
+  build-unity-project:
+    jobs:
+      # Linux Mono
+      - unity/build:
+          name: 'build-linux64-mono'
+          step-name: 'Build StandaloneLinux64'
+          unity-serial-var-name: 'UNITY_SERIAL'
+          unity-username-var-name: 'UNITY_USERNAME'
+          unity-password-var-name: 'UNITY_PASSWORD'
+          executor:
+            name: 'unity/ubuntu'
+            target_platform: 'base'
+            editor_version: '2021.3.1f1'
+            resource_class: 'large'
+          project-path: 'Unity2D-Demo-Game-CI-CD/src'
+          build-target: StandaloneLinux64
+          compress: true
+          context: unity
+
+      # Windows Mono
+      - unity/build:
+          name: 'build-Windows64-mono'
+          step-name: 'Build StandaloneWindows64'
+          unity-serial-var-name: 'UNITY_SERIAL'
+          unity-username-var-name: 'UNITY_USERNAME'
+          unity-password-var-name: 'UNITY_PASSWORD'
+          executor:
+            name: 'unity/ubuntu'
+            target_platform: 'windows-mono'
+            editor_version: '2021.3.2f1'
+            resource_class: 'large'
+          project-path: 'Unity2D-Demo-Game-CI-CD/src'
+          build-target: 'StandaloneWindows64'
+          context: unity
+
+      # macOS Mono
+      - unity/build:
+          name: 'build-osx-mono'
+          step-name: 'Build StandaloneOSX'
+          unity-serial-var-name: 'UNITY_SERIAL'
+          unity-username-var-name: 'UNITY_USERNAME'
+          unity-password-var-name: 'UNITY_PASSWORD'
+          executor:
+            name: 'unity/ubuntu'
+            target_platform: 'mac-mono'
+            editor_version: '2021.3.2f1'
+            resource_class: 'large'
+          project-path: 'Unity2D-Demo-Game-CI-CD/src'
+          build-target: 'StandaloneOSX'
+          context: unity
+```
+
+##### Other Platforms
+
+```yaml
+version: 2.1
+
+orbs:
+  unity: game-ci/unity@x.y
+
+workflows:
+  build-unity-project:
+    jobs:
+      # WebGL
+      - unity/build:
+          name: 'build-webgl'
+          step-name: 'Build WebGL'
+          unity-serial-var-name: 'UNITY_SERIAL'
+          unity-username-var-name: 'UNITY_USERNAME'
+          unity-password-var-name: 'UNITY_PASSWORD'
+          executor:
+            name: 'unity/ubuntu'
+            target_platform: 'webgl'
+            editor_version: '2021.3.1f1'
+            resource_class: 'large'
+          project-path: 'Unity2D-Demo-Game-CI-CD/src'
+          build-target: 'WebGL'
+          compress: false
+          context: unity
+
+      # Android
+      - unity/build:
+          name: 'build-android'
+          step-name: 'Build Android'
+          unity-serial-var-name: 'UNITY_SERIAL'
+          unity-username-var-name: 'UNITY_USERNAME'
+          unity-password-var-name: 'UNITY_PASSWORD'
+          executor:
+            name: 'unity/ubuntu'
+            target_platform: 'android'
+            editor_version: '2021.3.2f1'
+            resource_class: 'large'
+          project-path: 'Unity2D-Demo-Game-CI-CD/src'
+          build-target: 'Android'
+          context: unity
+
+      # iOS
+      - unity/build:
+          name: 'build-ios'
+          step-name: 'Build iOS'
+          unity-serial-var-name: 'UNITY_SERIAL'
+          unity-username-var-name: 'UNITY_USERNAME'
+          unity-password-var-name: 'UNITY_PASSWORD'
+          executor:
+            name: 'unity/ubuntu'
+            target_platform: 'ios'
+            editor_version: '2021.3.2f1'
+            resource_class: 'large'
+          project-path: 'Unity2D-Demo-Game-CI-CD/src'
+          build-target: 'iOS'
+          context: unity
+
+      # tvOS
+      - unity/build:
+          name: 'build-tvOS'
+          step-name: "Build Apple's tvOS"
+          unity-serial-var-name: 'UNITY_SERIAL'
+          unity-username-var-name: 'UNITY_USERNAME'
+          unity-password-var-name: 'UNITY_PASSWORD'
+          executor:
+            name: 'unity/windows-2019'
+            size: 'large'
+            editor_version: '2021.3.2f1'
+            target_platform: 'appletv'
+          project-path: 'Unity2D-Demo-Game-CI-CD/src'
+          build-target: tvOS
+          compress: true
+          context: unity
+```
diff --git a/versioned_docs/version-3/11-circleci/04-test.mdx b/versioned_docs/version-3/11-circleci/04-test.mdx
new file mode 100644
index 00000000..ab4b9626
--- /dev/null
+++ b/versioned_docs/version-3/11-circleci/04-test.mdx
@@ -0,0 +1,381 @@
+---
+toc_max_heading_level: 4
+---
+
+# Test
+
+The Unity Orb provides the
+[test job](https://circleci.com/developer/orbs/orb/game-ci/unity#jobs-test) to facilitate the
+process of testing your Unity project.
+
+At the end of the run, the test results are parsed to JUnit and
+[stored](https://circleci.com/docs/collect-test-data) in CircleCI so that
+[test insights](https://circleci.com/docs/insights-tests) can be used. You can access test insights
+from the CircleCI web app.
+
+### Parameters
+
+Below you will find information on each parameter that can be passed to the test job.
+
+#### executor
+
+The executor on which you want to run your test job on. Each executor has its set of parameters. See
+the [Executors](/docs/circleci/executors) section for more details.
+
+```yaml
+version: 2.1
+
+orbs:
+  unity: game-ci/unity@x.y
+
+workflows:
+  test-unity-project:
+    jobs:
+      - unity/test:
+          executor:
+            name: 'unity/ubuntu'
+            target_platform: 'linux-il2cpp'
+            editor_version: '2021.3.2f1'
+            resource_class: 'medium'
+```
+
+- _Default_: `N/A`
+- _Required_: `True`
+- _Type_: `Executor`
+
+#### no_output_timeout
+
+Elapsed time without output before the job is canceled and stopped. The value can be in hours,
+minutes or seconds - a digit followed by h, m or s respectively. Consider increasing it if you see
+this error:
+
+> Too long with no output (exceeded 20m0s): context deadline exceeded
+
+```yaml
+version: 2.1
+
+orbs:
+  unity: game-ci/unity@x.y
+
+workflows:
+  test-unity-project:
+    jobs:
+      - unity/test:
+          no_output_timeout: 30m
+```
+
+- _Default_: `20m`
+- _Required_: `false`
+- _Type_: `string`
+
+#### project-path
+
+If your project sits at the root of your repository, leave it to the default value. Otherwise, enter
+the path of your Unity project. This should be the directory that has an "Assets" folder inside it.
+
+```yaml
+version: 2.1
+
+orbs:
+  unity: game-ci/unity@x.y
+
+workflows:
+  test-unity-project:
+    jobs:
+      - unity/test:
+          project-path: 'Unity2D-Demo-Game-CI-CD/src'
+```
+
+- _Default_: `.`
+- _Required_: `False`
+- _Type_: `String`
+
+#### return-license
+
+Whether to manually return the Unity license after the test job is finished. This is usually
+unnecessary and only useful when running into an unrecoverable error while having a license active.
+Additionally, Unity only allows returning professional licenses.
+
+```yaml
+version: 2.1
+
+orbs:
+  unity: game-ci/unity@x.y
+
+workflows:
+  test-unity-project:
+    jobs:
+      - unity/test:
+          return-license: true
+```
+
+- _Default_: `false`
+- _Required_: `false`
+- _Type_: `boolean`
+
+#### step-name
+
+Specify a custom step name to be shown in the CircleCI web app.
+
+```yaml
+version: 2.1
+
+orbs:
+  unity: game-ci/unity@x.y
+
+workflows:
+  test-unity-project:
+    jobs:
+      - unity/test:
+          step-name: 'Test my Unity project'
+```
+
+- _Default_: `Run tests`
+- _Required_: `False`
+- _Type_: `String`
+
+#### test-platform
+
+Choose the platform to run your tests on. The available options can be found on the Unity test
+framework
+[documentation](https://docs.unity3d.com/Packages/com.unity.test-framework@2.0/manual/reference-command-line.html).
+
+```yaml
+version: 2.1
+
+orbs:
+  unity: game-ci/unity@x.y
+
+workflows:
+  test-unity-project:
+    jobs:
+      - unity/test:
+          test-platform: 'playmode'
+```
+
+- _Default_: `editmode`
+- _Required_: `False`
+- _Type_: `String`
+
+#### unity-license-var-name
+
+The name of the environment variable holding the license set in your
+[Context](/docs/circleci/activation#preparing-the-context). If you are testing your project using
+the Unity Pro or Plus license, this is **not** required. See [Activation](/docs/circleci/activation)
+for more details.
+
+```yaml
+version: 2.1
+
+orbs:
+  unity: game-ci/unity@x.y
+
+workflows:
+  test-unity-project:
+    jobs:
+      - unity/test:
+          unity-license-var-name: 'UNITY_ENCODED_LICENSE'
+```
+
+- _Default_: `UNITY_ENCODED_LICENSE`
+- _Required_: `False`
+- _Type_: `env_var_name`
+
+#### unity-password-var-name
+
+The name of the environment variable holding the password set in your
+[Context](/docs/circleci/activation#preparing-the-context). See
+[Activation](/docs/circleci/activation) for more details.
+
+```yaml
+version: 2.1
+
+orbs:
+  unity: game-ci/unity@x.y
+
+workflows:
+  test-unity-project:
+    jobs:
+      - unity/test:
+          unity-password-var-name: 'UNITY_PASSWORD'
+```
+
+- _Default_: `UNITY_PASSWORD`
+- _Required_: `False`
+- _Type_: `env_var_name`
+
+#### unity-serial-var-name
+
+The name of the environment variable holding the serial set in your
+[Context](/docs/circleci/activation#preparing-the-context). If you are testing your project using
+the Unity Personal license, this is **not** required. See [Activation](/docs/circleci/activation)
+for more details.
+
+```yaml
+version: 2.1
+
+orbs:
+  unity: game-ci/unity@x.y
+
+workflows:
+  test-unity-project:
+    jobs:
+      - unity/test:
+          unity-serial-var-name: 'UNITY_SERIAL'
+```
+
+- _Default_: `UNITY_SERIAL`
+- _Required_: `False`
+- _Type_: `env_var_name`
+
+#### unity-username-var-name
+
+The name of the environment variable holding the username set in your
+[Context](/docs/circleci/activation#preparing-the-context). See
+[Activation](/docs/circleci/activation) for more details.
+
+```yaml
+version: 2.1
+
+orbs:
+  unity: game-ci/unity@x.y
+
+workflows:
+  test-unity-project:
+    jobs:
+      - unity/test:
+          unity-username-var-name: 'UNITY_USERNAME'
+```
+
+- _Default_: `UNITY_USERNAME`
+- _Required_: `False`
+- _Type_: `env_var_name`
+
+### Examples
+
+In this section, you will find examples of workflows using this job. However, notice that the
+separation used in the examples is only for the sake of visualisation. You can test all target
+platforms in the same workflow. All examples are based on CircleCI's
+[Demo Project](https://github.com/CircleCI-Public/Unity2D-Demo-Game-CI-CD).
+
+#### Personal License
+
+This example shows how to build your project for several platforms using a Personal License.
+
+```yaml
+version: 2.1
+
+orbs:
+  unity: game-ci/unity@x.y
+
+workflows:
+  build-unity-project:
+    jobs:
+      # Linux
+      - unity/test:
+          name: 'test-linux'
+          step-name: 'Check if the tests run and results are uploaded'
+          unity-license-var-name: 'UNITY_ENCODED_LICENSE'
+          unity-username-var-name: 'UNITY_USERNAME'
+          unity-password-var-name: 'UNITY_PASSWORD'
+          executor:
+            name: 'unity/ubuntu'
+            target_platform: 'linux-il2cpp'
+            editor_version: '2021.3.1f1'
+            resource_class: 'medium'
+          project-path: 'Unity2D-Demo-Game-CI-CD/src'
+          test-platform: 'playmode'
+          context: unity
+
+      # Windows
+      - unity/test:
+          name: 'test-windows'
+          step-name: 'Check if the tests run and results are uploaded'
+          unity-license-var-name: 'UNITY_ENCODED_LICENSE'
+          unity-username-var-name: 'UNITY_USERNAME'
+          unity-password-var-name: 'UNITY_PASSWORD'
+          executor:
+            name: 'unity/windows-2022'
+            size: 'large'
+            editor_version: '2021.3.2f1'
+            target_platform: 'windows-il2cpp'
+          project-path: 'Unity2D-Demo-Game-CI-CD/src'
+          test-platform: 'playmode'
+          context: unity
+
+      # macOS
+      - unity/test:
+          name: 'test-osx'
+          step-name: 'Check if the tests run and results are uploaded'
+          unity-license-var-name: 'UNITY_ENCODED_LICENSE'
+          unity-username-var-name: 'UNITY_USERNAME'
+          unity-password-var-name: 'UNITY_PASSWORD'
+          executor:
+            name: 'unity/macos'
+            editor_version: '2021.3.1f1'
+            resource_class: 'large'
+          project-path: 'Unity2D-Demo-Game-CI-CD/src'
+          test-platform: 'playmode'
+          context: unity
+```
+
+#### Professional License
+
+This example shows how to build your project for several platforms using a Pro License.
+
+```yaml
+version: 2.1
+
+orbs:
+  unity: game-ci/unity@x.y
+
+workflows:
+  build-unity-project:
+    jobs:
+      # Linux
+      - unity/test:
+          name: 'test-linux'
+          step-name: 'Check if the tests run and results are uploaded'
+          unity-serial-var-name: 'UNITY_SERIAL'
+          unity-username-var-name: 'UNITY_USERNAME'
+          unity-password-var-name: 'UNITY_PASSWORD'
+          executor:
+            name: 'unity/ubuntu'
+            target_platform: 'linux-il2cpp'
+            editor_version: '2021.3.1f1'
+            resource_class: 'medium'
+          project-path: 'Unity2D-Demo-Game-CI-CD/src'
+          test-platform: 'playmode'
+          context: unity
+
+      # Windows
+      - unity/test:
+          name: 'test-windows'
+          step-name: 'Check if the tests run and results are uploaded'
+          unity-serial-var-name: 'UNITY_SERIAL'
+          unity-username-var-name: 'UNITY_USERNAME'
+          unity-password-var-name: 'UNITY_PASSWORD'
+          executor:
+            name: 'unity/windows-2022'
+            size: 'large'
+            editor_version: '2021.3.2f1'
+            target_platform: 'windows-il2cpp'
+          project-path: 'Unity2D-Demo-Game-CI-CD/src'
+          test-platform: 'playmode'
+          context: unity
+
+      # macOS
+      - unity/test:
+          name: 'test-osx'
+          step-name: 'Check if the tests run and results are uploaded'
+          unity-serial-var-name: 'UNITY_SERIAL'
+          unity-username-var-name: 'UNITY_USERNAME'
+          unity-password-var-name: 'UNITY_PASSWORD'
+          executor:
+            name: 'unity/macos'
+            editor_version: '2021.3.1f1'
+            resource_class: 'large'
+          project-path: 'Unity2D-Demo-Game-CI-CD/src'
+          test-platform: 'playmode'
+          context: unity
+```
diff --git a/versioned_docs/version-3/11-circleci/05-executors.mdx b/versioned_docs/version-3/11-circleci/05-executors.mdx
new file mode 100644
index 00000000..e802e505
--- /dev/null
+++ b/versioned_docs/version-3/11-circleci/05-executors.mdx
@@ -0,0 +1,448 @@
+# Executors
+
+The Orb provides reusable execution environments for you to run your jobs on. The executors
+available are [macOS](#macos), [macOS on Runner](#macos-runner), [Windows](#windows),
+[Windows on Runner](#windows-runner), [Ubuntu on Docker](#ubuntu)
+
+The `macos` and `windows` executors take longer to setup due to the installation of external
+dependencies. This can be mitigated using their [Runner](https://circleci.com/docs/runner-overview)
+variants. As Runner doesn't share the ephemeral nature of the CircleCI cloud executors, the external
+dependencies will already be installed after the first run, decreasing the environment preparation
+time.
+
+Notice that projects using `IL2CPP` as the
+[scripting backend](https://docs.unity3d.com/Manual/scripting-backends.html) should run on the same
+OS as the [build target](/docs/circleci/build#build-target). For example, if you want to build for
+macOS using `IL2CPP`, you must use the [macos](#macos) or [macos-runner](#macos-runner) executors.
+For other use-cases, it's recommended to use [ubuntu](#ubuntu) for all supported platforms as it
+will be cheaper and faster.
+
+### macos
+
+This executor uses the
+[macOS cloud executor](https://circleci.com/docs/configuration-reference#macos) and it's recommended
+for **macOS IL2CPP builds**. As there are no GameCI images for macOS at the moment, the Unity Editor
+and Hub are installed in runtime, leading to longer build times. Should it become an issue, consider
+using [macos-runner](#macos-runner) instead.
+
+#### editor_version
+
+Choose the Unity Editor version that you want to use to build your project. The options available
+can be found on the Unity [archive](https://unity3d.com/get-unity/download/archive).
+
+```yaml
+version: 2.1
+
+orbs:
+  unity: game-ci/unity@x.y
+
+workflows:
+  build-unity-project:
+    jobs:
+      - unity/build:
+          executor:
+            name: 'unity/macos'
+            editor_version: '2021.3.2f1'
+```
+
+- _Default_: `N/A`
+- _Required_: `True`
+- _Type_: `String`
+
+#### resource_class
+
+Choose the
+[resource class](https://circleci.com/docs/configuration-reference#macos-execution-environment) for
+your execution environment. Try increasing it if your environment is running out of memory during
+the build.
+
+```yaml
+version: 2.1
+
+orbs:
+  unity: game-ci/unity@x.y
+
+workflows:
+  build-unity-project:
+    jobs:
+      - unity/build:
+          executor:
+            name: 'unity/macos'
+            resource_class: 'large'
+```
+
+- _Default_: `medium`
+- _Required_: `False`
+- _Type_: `Enum`
+
+#### xcode_version
+
+Choose the [xcode version](https://circleci.com/docs/using-macos#supported-xcode-versions) for your
+execution environment.
+
+```yaml
+version: 2.1
+
+orbs:
+  unity: game-ci/unity@x.y
+
+workflows:
+  build-unity-project:
+    jobs:
+      - unity/build:
+          executor:
+            name: 'unity/macos'
+            xcode_version: '14.0.0'
+```
+
+- _Default_: `13.4.1`
+- _Required_: `False`
+- _Type_: `String`
+
+### macos-runner
+
+This executor uses [self-hosted runner](https://circleci.com/docs/runner-overview). If you are
+unsure how to create or configure it, follow  
+[Installing Self-Hosted Runners with the Web App](https://circleci.com/docs/runner-installation) and
+[CircleCI Self-hosted Runner Installation on macOS](https://circleci.com/docs/runner-installation-mac).
+
+The `macos-runner` is an excellent alternative over [macos](#macos) to build macOS IL2CPP with
+faster build times. Its non-ephemeral nature saves times on installing external dependencies after
+the first run. And in addition, you are free to use an agent with hardware exceeding the
+[available](https://circleci.com/docs/configuration-reference#macos-execution-environment) for the
+web macOS executor.
+
+#### editor_version
+
+Choose the Unity Editor version that you want to use to build your project. The options available
+can be found on the Unity [archive](https://unity3d.com/get-unity/download/archive).
+
+```yaml
+version: 2.1
+
+orbs:
+  unity: game-ci/unity@x.y
+
+workflows:
+  build-unity-project:
+    jobs:
+      - unity/build:
+          executor:
+            name: 'unity/macos-runner'
+            editor_version: '2021.3.2f1'
+```
+
+- _Default_: `N/A`
+- _Required_: `True`
+- _Type_: `String`
+
+#### resource_class
+
+Enter your [runner resource class](https://circleci.com/docs/runner-overview). If you are unsure
+what this means, navigate to the beginning of this [sub-section](#macos-runner).
+
+```yaml
+version: 2.1
+
+orbs:
+  unity: game-ci/unity@x.y
+
+workflows:
+  build-unity-project:
+    jobs:
+      - unity/build:
+          executor:
+            name: 'unity/macos-runner'
+            resource_class: 'my_runner_resource_class'
+```
+
+- _Default_: `N/A`
+- _Required_: `True`
+- _Type_: `String`
+
+#### working_directory
+
+Enter the working directory of your runner agent. This will be where the job steps will run.
+
+```yaml
+version: 2.1
+
+orbs:
+  unity: game-ci/unity@x.y
+
+workflows:
+  build-unity-project:
+    jobs:
+      - unity/build:
+          executor:
+            name: 'unity/macos-runner'
+            working_directory: '/var/opt/circleci/unity_working_dir'
+```
+
+- _Default_: `/var/opt/circleci/workdir`
+- _Required_: `False`
+- _Type_: `String`
+
+### ubuntu
+
+This executor uses the
+[Docker cloud executor](https://circleci.com/docs/configuration-reference#docker) with GameCI
+[images](/docs/docker/docker-images). Since the latter ships with the Unity Hub, Editor and all
+necessary dependencies, none of it is installed in runtime - making `ubuntu` more time-efficient
+than [macos](#macos) and [windows](#windows).
+
+For faster and cheaper runs, use it for all [build targets](/docs/circleci/build#build-target) that
+don't require a host OS other than Linux.
+
+#### editor_version
+
+Choose the Unity Editor version that you want to use to build your project. The available options
+can be found on the [versions](/docs/docker/versions) page.
+
+```yaml
+version: 2.1
+
+orbs:
+  unity: game-ci/unity@x.y
+
+workflows:
+  build-unity-project:
+    jobs:
+      - unity/build:
+          executor:
+            name: 'unity/ubuntu'
+            editor_version: '2021.3.2f1'
+```
+
+- _Default_: `N/A`
+- _Required_: `True`
+- _Type_: `String`
+
+#### resource_class
+
+Choose the
+[resource class](https://circleci.com/docs/configuration-reference#docker-execution-environment) for
+your execution environment. Try increasing it if your environment is running out of memory during
+the build.
+
+```yaml
+version: 2.1
+
+orbs:
+  unity: game-ci/unity@x.y
+
+workflows:
+  build-unity-project:
+    jobs:
+      - unity/build:
+          executor:
+            name: 'unity/macos'
+            resource_class: 'large'
+```
+
+- _Default_: `medium`
+- _Required_: `False`
+- _Type_: `Enum`
+
+#### target_platform
+
+Choose the target platform to be used for the GameCI image. The available options can be found on
+the [versions](/docs/docker/versions) page.
+
+```yaml
+version: 2.1
+
+orbs:
+  unity: game-ci/unity@x.y
+
+workflows:
+  build-unity-project:
+    jobs:
+      - unity/build:
+          executor:
+            name: 'unity/macos'
+            target_platform: 'linux-il2cpp'
+```
+
+- _Default_: `N/A`
+- _Required_: `True`
+- _Type_: `Enum`
+
+### windows
+
+This executor uses the
+[Windows cloud executor](https://circleci.com/docs/configuration-reference#available-windows-machine-images)
+with GameCI [images](/docs/docker/docker-images) and it's recommended for **Windows IL2CPP builds**.
+Due to [limitations](/docs/docker/windows-docker-images#limitations), jobs running on the Windows
+executor must install third-party dependencies in runtime, leading to longer build times. Should it
+become an issue, consider using [windows-runner](#windows-runner) instead.
+
+The orb ships with three variants:
+[windows-2019](https://circleci.com/developer/machine/image/windows-server-2019),
+[windows-2019-cuda](https://circleci.com/developer/machine/image/windows-server-2019-cuda) and
+[windows-2022](https://circleci.com/developer/machine/image/windows-server-2022-gui). If you are
+unsure of which one to use, pick `windows-2022`. If you need an executor with GPU, then choose
+`windows-2019-cuda`.
+
+#### editor_version
+
+Choose the Unity Editor version that you want to use to build your project. The available options
+can be found on the [versions](/docs/docker/versions) page.
+
+```yaml
+version: 2.1
+
+orbs:
+  unity: game-ci/unity@x.y
+
+workflows:
+  build-unity-project:
+    jobs:
+      - unity/build:
+          executor:
+            name: 'unity/windows-2022'
+            ## or name: "unity/windows-2019"
+            ## or name: "unity/windows-2019-cuda"
+            editor_version: '2021.3.2f1'
+```
+
+- _Default_: `N/A`
+- _Required_: `True`
+- _Type_: `String`
+
+#### size
+
+Choose the [size](https://circleci.com/docs/configuration-reference#windows-execution) of your
+execution environment resource class. Try increasing it if your environment is running out of memory
+during the build.
+
+```yaml
+version: 2.1
+
+orbs:
+  unity: game-ci/unity@x.y
+
+workflows:
+  build-unity-project:
+    jobs:
+      - unity/build:
+          executor:
+            name: 'unity/windows-2022'
+            ## or name: "unity/windows-2019"
+            ## or name: "unity/windows-2019-cuda"
+            resource_class: 'xlarge'
+```
+
+- _Default_: `large`
+- _Required_: `False`
+- _Type_: `Enum`
+
+#### target_platform
+
+Choose the target platform to be used for the GameCI image. The available options can be found on
+the [versions](/docs/docker/versions) page.
+
+```yaml
+version: 2.1
+
+orbs:
+  unity: game-ci/unity@x.y
+
+workflows:
+  build-unity-project:
+    jobs:
+      - unity/build:
+          executor:
+            name: 'unity/windows-2022'
+            ## or name: "unity/windows-2019"
+            ## or name: "unity/windows-2019-cuda"
+            target_platform: 'windows-il2cpp'
+```
+
+- _Default_: `N/A`
+- _Required_: `True`
+- _Type_: `Enum`
+
+### windows-runner
+
+This executor uses [self-hosted runner](https://circleci.com/docs/runner-overview). If you are
+unsure how to create or configure it, follow  
+[Installing Self-Hosted Runners with the Web App](https://circleci.com/docs/runner-installation) and
+[CircleCI Self-hosted Runner Installation on Windows](https://circleci.com/docs/runner-installation-windows).
+
+The `windows-runner` is an excellent alternative over [windows](#windows) to build Windows IL2CPP
+with faster build times. Its non-ephemeral nature saves times on installing external dependencies
+after the first run. And in addition, you are free to use an agent with hardware exceeding the
+[available](https://circleci.com/docs/configuration-reference#windows-execution) for the web Windows
+executor.
+
+#### editor_version
+
+Choose the Unity Editor version that you want to use to build your project. The available options
+can be found on the [versions](/docs/docker/versions) page.
+
+```yaml
+version: 2.1
+
+orbs:
+  unity: game-ci/unity@x.y
+
+workflows:
+  build-unity-project:
+    jobs:
+      - unity/build:
+          executor:
+            name: 'unity/windows-runner'
+            editor_version: '2021.3.2f1'
+```
+
+- _Default_: `N/A`
+- _Required_: `True`
+- _Type_: `String`
+
+#### resource_class
+
+Enter your [runner resource class](https://circleci.com/docs/runner-overview). If you are unsure
+what this means, navigate to the beginning of [this section](#windows-runner).
+
+```yaml
+version: 2.1
+
+orbs:
+  unity: game-ci/unity@x.y
+
+workflows:
+  build-unity-project:
+    jobs:
+      - unity/build:
+          executor:
+            name: 'unity/windows-runner'
+            resource_class: 'my_runner_resource_class'
+```
+
+- _Default_: `N/A`
+- _Required_: `True`
+- _Type_: `String`
+
+#### working_directory
+
+Enter the working directory of your runner agent. This is be where the job steps will run from.
+
+```yaml
+version: 2.1
+
+orbs:
+  unity: game-ci/unity@x.y
+
+workflows:
+  build-unity-project:
+    jobs:
+      - unity/build:
+          executor:
+            name: 'unity/windows-runner'
+            working_directory: 'C:\Users\circleci\AppData\Local\Temp\Unity_Working_Dir'
+```
+
+- _Default_: `C:\Users\circleci\AppData\Local\Temp\Workdir`
+- _Required_: `False`
+- _Type_: `String`
diff --git a/versioned_docs/version-3/11-circleci/_category_.yaml b/versioned_docs/version-3/11-circleci/_category_.yaml
new file mode 100644
index 00000000..d61b697c
--- /dev/null
+++ b/versioned_docs/version-3/11-circleci/_category_.yaml
@@ -0,0 +1,5 @@
+---
+position: 5.0
+label: CircleCI
+collapsible: true
+collapsed: true
diff --git a/versioned_docs/version-3/index.mdx b/versioned_docs/version-3/index.mdx
new file mode 100644
index 00000000..03ac8283
--- /dev/null
+++ b/versioned_docs/version-3/index.mdx
@@ -0,0 +1,25 @@
+---
+sidebar_position: 1
+---
+
+# Introduction
+
+This site hosts all documentation for GameCI, and will help you setup Continuous Integration for
+your game projects.
+
+Continuous Integration is a widely-used practice where automated pipelines check the latest code
+changes actually work, before merging them into the main branch. This helps developers stay in the
+flow and release faster and (ultimately) with more confidence.
+
+Follow the development on [GitHub](https://github.com/game-ci/documentation).
+
+<iframe
+  title="GameCI discord widget"
+  src="https://discord.com/widget?id=710946343828455455&theme=dark"
+  width="350"
+  height="500"
+  frameBorder="0"
+  sandbox="allow-popups allow-popups-to-escape-sandbox allow-same-origin allow-scripts"
+/>
+
+Join the discussion on [Discord](https://game.ci/discord).
diff --git a/versioned_sidebars/version-3-sidebars.json b/versioned_sidebars/version-3-sidebars.json
new file mode 100644
index 00000000..cff0c94e
--- /dev/null
+++ b/versioned_sidebars/version-3-sidebars.json
@@ -0,0 +1,8 @@
+{
+  "defaultSidebar": [
+    {
+      "type": "autogenerated",
+      "dirName": "."
+    }
+  ]
+}
diff --git a/versions.json b/versions.json
index d34f7a24..89a34a9b 100644
--- a/versions.json
+++ b/versions.json
@@ -1 +1 @@
-["2", "1"]
+["3", "2", "1"]