Final changes to metatheory-site.yml workflow

.github/workflows/metatheory-site.yml

@@ -13,14 +13,14 @@ on:
         description: |
           The release version tag. For example if $version == "1.29.0.0" then the 
           current contents of the branch tagged "1.29.0.0" will be deployed to: 
-            https://intersectmbo.github.io/plutus/metatheory/$version
+          https://intersectmbo.github.io/plutus/metatheory/$version
         required: true
         type: string
 
       latest: 
         description: |
           If true, then the $version branch will also be deployed to:
-            https://intersectmbo.github.io/plutus/metatheory/latest
+          https://intersectmbo.github.io/plutus/metatheory/latest.
           You want to leave this to true unless you are deploying old versions.
         type: boolean
         required: true 
@@ -36,23 +36,26 @@ jobs:
       name: github-pages
     steps:
       - name: Checkout
-        uses: actions/checkout@latest
+        uses: actions/checkout@main
         with:
           ref: ${{ inputs.version }}
 
       - name: Build Site
-        run: nix build .#plutus-metatheory-site --out-link _site
+        run: | 
+          nix build --accept-flake-config .#plutus-metatheory-site
+          mkdir _site
+          cp -RL result/* _site
 
       - name: Deploy Site
-        uses: JamesIves/github-pages-deploy-action@latest
+        uses: JamesIves/github-pages-deploy-action@v4.6.1
         with:
           folder: _site
           target-folder: metatheory/${{ inputs.version }}
           single-commit: true
 
       - name: Deploy Latest
         if: ${{ inputs.latest == true }}
-        uses: JamesIves/github-pages-deploy-action@latest
+        uses: JamesIves/github-pages-deploy-action@v4.6.1
         with:
           folder: _site
           target-folder: metatheory/latest

RELEASE.adoc

@@ -98,6 +98,11 @@ Another example is if a security audit is done on `rc1`, and the changes in `rc2
 - This will automatically open a PR in `plutus-tx-template` with auto-merge enabled
 - Ensure that CI is green and the PR gets merged
 
+10. Publish the updated Metatheory site
+- Navigate to the https://github.com/IntersectMBO/plutus/actions/workflows/metatheory-site.yml[Metatheory Site Action] on GitHub
+- Click the `Run workflow` button on the right, enter the new release version and confirm
+- Ensure that the action completes successfully
+
 === Patch Releases
 
 Suppose we are releasing version `x.y.z.w`.