wip

.github/workflows/haddock.yml

@@ -18,7 +18,7 @@ jobs:
           nix_conf: |
             experimental-features = nix-command flakes
             accept-flake-config = true
-      - name: Build haddock site
+      - name: Build Haddock Site
         run: |
           nix build .#combined-haddock
           mkdir dist

.github/workflows/plutus-tx-template.yml

@@ -0,0 +1,21 @@
+name: CI
+
+on:
+  pull_request:
+
+jobs:
+  test-plutus-tx-template:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4.1.1
+
+      - name: Build Project With Docker
+        run: |
+          # Note: the -i flag in "bash -ic" is necessary and causes bash to
+          # "source ~/.bashrc" which correctly populates the env.
+          docker run \
+            -v ./.:/workspaces/plutus-tx-template \
+            -w /workspaces/plutus-tx-template \
+            -i ghcr.io/input-output-hk/devx-devcontainer:x86_64-linux.ghc96-iog \
+            bash -ic "cabal update && cabal run plutus-tx-template && test -e validator.uplc"

RELEASE.adoc

@@ -97,9 +97,16 @@ Another example is if a security audit is done on `rc1`, and the changes in `rc2
 
 8. Once the CHaP PR has been merged, make a PR to update the version used in `cardano-ledger`. Example: https://github.com/IntersectMBO/cardano-ledger/pull/3563.
 - Update the version bounds in cabal files.
-- Update the CHaP index state in `cabal.project`.
+- Update the CHaP index state
+ in `cabal.project`.
 - Update the CHaP flake input with `nix flake update CHaP`.  If you get "error: cannot find flake 'flake:CHaP' in the flake registries" your nix installation probably needs to be updated.
 
+9. Make a PR to update the version used in `plutus-tx-template`
+- Navigate to the https://github.com/IntersectMBO/plutus-tx-template/actions/workflows/bump-plutus-version.yml[Bump Plutus Version Action] on GitHub
+- Click the `Run workflow` button on the right, enter the new release version and confirm
+- This will automatically open a PR in `plutus-tx-template` with auto-merge enabled
+- Ensure that CI is green and the PR gets merged
+
 === Patch Releases
 
 Suppose we are releasing version `x.y.z.w`.

cabal.project

@@ -80,4 +80,4 @@ allow-newer:
   , inline-r:deepseq
   , inline-r:bytestring
   , inline-r:containers
-  , inline-r:primitive
+  , inline-r:primitive