diff --git a/.github/workflows/build.yml b/.github/workflows/build.yml
index 8cd7909d6..186db8c03 100644
--- a/.github/workflows/build.yml
+++ b/.github/workflows/build.yml
@@ -184,12 +184,12 @@ jobs:
       # This is done because, based on how you execute Apex tests, the running user may have an active session (synchrously) or not (asynchronously).
       # This data is also mocked during tests, but running the Apex tests sync & async serves within the pipeline acts as an extra level of
       # integration testing to ensure that everything works with or without an active session.
-      - name: 'Run Apex Tests Synchronously'
-        run: npm run test:apex:nocoverage -- --synchronous
-
       - name: 'Run Apex Tests Asynchronously'
         run: npm run test:apex:nocoverage
 
+      - name: 'Run Apex Tests Synchronously'
+        run: npm run test:apex:nocoverage -- --synchronous
+
       - name: 'Delete Scratch Org'
         run: npx sf org delete scratch --no-prompt
         if: ${{ always() }}
@@ -252,12 +252,12 @@ jobs:
       # This is done because, based on how you execute Apex tests, the running user may have an active session (synchrously) or not (asynchronously).
       # This data is also mocked during tests, but running the Apex tests sync & async serves within the pipeline acts as an extra level of
       # integration testing to ensure that everything works with or without an active session.
-      - name: 'Run Apex Tests Synchronously'
-        run: npm run test:apex:nocoverage -- --synchronous
-
       - name: 'Run Apex Tests Asynchronously'
         run: npm run test:apex:nocoverage
 
+      - name: 'Run Apex Tests Synchronously'
+        run: npm run test:apex:nocoverage -- --synchronous
+
       - name: 'Delete Scratch Org'
         run: npx sf org delete scratch --no-prompt
         if: ${{ always() }}
@@ -320,12 +320,12 @@ jobs:
       # This is done because, based on how you execute Apex tests, the running user may have an active session (synchrously) or not (asynchronously).
       # This data is also mocked during tests, but running the Apex tests sync & async serves within the pipeline acts as an extra level of
       # integration testing to ensure that everything works with or without an active session.
-      - name: 'Run Apex Tests Synchronously'
-        run: npm run test:apex:nocoverage -- --synchronous
-
       - name: 'Run Apex Tests Asynchronously'
         run: npm run test:apex:nocoverage
 
+      - name: 'Run Apex Tests Synchronously'
+        run: npm run test:apex:nocoverage -- --synchronous
+
       - name: 'Delete Scratch Org'
         run: npx sf org delete scratch --no-prompt
         if: ${{ always() }}
@@ -391,12 +391,12 @@ jobs:
       # This is done because, based on how you execute Apex tests, the running user may have an active session (synchrously) or not (asynchronously).
       # This data is also mocked during tests, but running the Apex tests sync & async serves within the pipeline acts as an extra level of
       # integration testing to ensure that everything works with or without an active session.
-      - name: 'Run Apex Tests Synchronously'
-        run: npm run test:apex:nocoverage -- --synchronous
-
       - name: 'Run Apex Tests Asynchronously'
         run: npm run test:apex:nocoverage
 
+      - name: 'Run Apex Tests Synchronously'
+        run: npm run test:apex:nocoverage -- --synchronous
+
       - name: 'Delete Scratch Org'
         run: npx sf org delete scratch --no-prompt
         if: ${{ always() }}
@@ -466,12 +466,12 @@ jobs:
       # This is done because, based on how you execute Apex tests, the running user may have an active session (synchrously) or not (asynchronously).
       # This data is also mocked during tests, but running the Apex tests sync & async serves within the pipeline acts as an extra level of
       # integration testing to ensure that everything works with or without an active session.
-      - name: 'Run Apex Tests Synchronously'
-        run: npm run test:apex:nocoverage -- --synchronous
-
       - name: 'Run Apex Tests Asynchronously'
         run: npm run test:apex:nocoverage
 
+      - name: 'Run Apex Tests Synchronously'
+        run: npm run test:apex:nocoverage -- --synchronous
+
       - name: 'Delete Base Scratch Org'
         run: npx sf org delete scratch --no-prompt
         if: ${{ always() }}
@@ -534,18 +534,18 @@ jobs:
       # This is done because, based on how you execute Apex tests, the running user may have an active session (synchrously) or not (asynchronously).
       # This data is also mocked during tests, but running the Apex tests sync & async serves within the pipeline acts as an extra level of
       # integration testing to ensure that everything works with or without an active session.
-      - name: 'Run Apex Tests Synchronously'
-        run: npm run test:apex:nocoverage -- --synchronous
-
       - name: 'Run Apex Tests Asynchronously'
         run: npm run test:apex:nocoverage
 
+      - name: 'Run Apex Tests Synchronously'
+        run: npm run test:apex:nocoverage -- --synchronous
+
       - name: 'Delete Scratch Org'
         run: npx sf org delete scratch --no-prompt
         if: ${{ always() }}
 
   create-managed-package-beta:
-    environment: 'Demo Org'
+    environment: 'Base Scratch Org'
     name: 'Create Managed Package Beta'
     needs:
       [
@@ -634,19 +634,10 @@ jobs:
           DEV_HUB_CONSUMER_KEY: ${{ secrets.DEV_HUB_CONSUMER_KEY }}
           DEV_HUB_JWT_SERVER_KEY: ${{ secrets.DEV_HUB_JWT_SERVER_KEY }}
 
-      # - name: 'Authorize Demo Org'
-      #   shell: bash
-      #   run: |
-      #     echo ${{ env.PKG_DEMO_ORG_SFDX_URL }} > ./PKG_DEMO_ORG_SFDX_URL.txt
-      #     npx sf org login sfdx-url --sfdx-url-file ./PKG_DEMO_ORG_SFDX_URL.txt --alias nebula-logger-package-demo
-      #   env:
-      #     PKG_DEMO_ORG_SFDX_URL: ${{ secrets.NEBULA_PKG_DEMO_SANDBOX_SFDX_URL }}
-
       - name: 'Create Scratch Org'
         run: npx sf org create scratch --no-namespace --no-track-source --alias base_package_subscriber_scratch_org --duration-days 1 --definition-file ./config/scratch-orgs/base-scratch-def.json --wait 20 --set-default --json
 
       - name: 'Create & Install Package Version'
-        # run: npx pwsh ./scripts/build/create-and-install-package-version.ps1 -targetpackagealias '"Nebula Logger - Core"' -targetreadme ./README.md -targetusername nebula-logger-package-demo
         run: npx pwsh ./scripts/build/create-and-install-package-version.ps1 -targetpackagealias '"Nebula Logger - Core"' -targetreadme ./README.md  -targetusername base_package_subscriber_scratch_org
 
       # This is the only place in Nebula Logger's pipeline where the `LoggerCore` test suite runs & the results are sent to Codecov.io.