update latest pandoc and spec guidance

Author: chrisfenner

.github/workflows/actions.yml

@@ -12,39 +12,68 @@ jobs:
   render:
     runs-on: ubuntu-latest
     container:
-      image: ghcr.io/trustedcomputinggroup/pandoc:0.8.2
+      image: ghcr.io/trustedcomputinggroup/pandoc:0.10.2
     name: Render PDF
     steps:
       - name: Checkout
         uses: actions/checkout@v3
+        with:
+          fetch-depth: 0
+          fetch-tags: true
+
+      - name: Cache LaTeX files
+        uses: actions/cache@v3
+        env:
+          cache-name: cache-latex-files
+        with:
+          path: |
+            *.aux
+            *.fdb_latexmk
+            *.lof
+            *.lot
+            *.toc
+            *.convert.pdf
+          key: latex-${{ github.run_id }}
+          restore-keys: latex
 
       - name: Render
         uses: trustedcomputinggroup/markdown@v0.4.2
         with:
           input-md: spec.md
+          extra-build-options: "--versioned_filenames"
           output-pdf: spec.pdf
           output-docx: spec.docx
 
       - name: Upload PDF to PR
         uses: actions/upload-artifact@master
         if: ${{ github.event_name == 'pull_request' }}
         with:
-          name: spec.pdf
-          path: spec.pdf
+          name: PDF
+          path: spec.*.pdf
 
       - name: Upload Word to PR
         uses: actions/upload-artifact@master
         if: ${{ github.event_name == 'pull_request' }}
         with:
-          name: spec.docx
-          path: spec.docx
+          name: Word
+          path: spec.*.docx
+
+      - name: Upload PDF to release
+        uses: svenstaro/upload-release-action@v2
+        if: ${{ github.event_name == 'release' }}
+        with:
+          repo_token: ${{ secrets.GITHUB_TOKEN }}
+          file: spec.*.pdf
+          tag: ${{ github.ref }}
+          overwrite: true
+          file_glob: true
 
-      - name: Upload PDF and docx to release
+      - name: Upload Word to release
         uses: svenstaro/upload-release-action@v2
         if: ${{ github.event_name == 'release' }}
         with:
           repo_token: ${{ secrets.GITHUB_TOKEN }}
-          file: spec.*
+          file: spec.*.docx
           tag: ${{ github.ref }}
           overwrite: true
           file_glob: true

spec.md

@@ -68,17 +68,9 @@ comment_, it can be considered a _normative statement_.
 
 EXAMPLE:
 
-::: Informative :::
-This is the first paragraph of 1–n paragraphs containing text of the kind
-informative comment ...
-
-This is the second paragraph of text of the kind informative comment ...
-
-This is the nth paragraph of text of the kind informative comment ...
-
-To understand the TCG specification, the user must read the specification.
-(This use of MUST does not require any action).
-:::::::::::::::::::
+::: Informative ::::
+Reach out to <admin@trustedcomputinggroup> with any questions about this document.
+::::::::::::::::::::
 
 ---
 
@@ -93,7 +85,8 @@ To understand the TCG specification, the user must read the specification.
 # Checklist for users of this template
 
 * Ensure the repository is set to private
-* Add the correct GitHub team(s) to Collaborators* Add TCGadmin to Admin
+* Add the correct GitHub team(s) to Collaborators
+* Add TCGadmin to Admin
 * Add a branch protection rule on `main`
   * Require a pull request before merging
   * Require approvals
@@ -104,6 +97,7 @@ To understand the TCG specification, the user must read the specification.
   [markdown](https://github.com/trustedcomputinggroup/markdown) action versions
   for `actions.yml`
 * Update the document title and type in the YAML front matter
-  * For GUIDANCE or REFERENCE docs, add `template: bluetop`
 * (Optional) Do an initial release to set baseline version (e.g., if migrating
-  from an existing Word doc).
+  from an existing Word doc).
+* (Optional) Review the guidance about release naming in the latest User's
+  Guide from <https://github.com/trustedcomputinggroup/pandoc>.