Fail CI if the DB dump is dirty (#56)

* Bump CI dependencies
* Add a CI check for dirty CI dump
* Print dirty DB files for CI
* Ignore compiled files
* Test CI dirty DB check
* Revert "Test CI dirty DB check"
* Print the full dirty diff in CI check

Author: michaelblyons

.github/workflows/build.yml

@@ -6,18 +6,18 @@ jobs:
     runs-on: ubuntu-latest
     timeout-minutes: 15
     steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v6
         with:
           submodules: true
 
       - name: Setup Go
-        uses: actions/setup-go@v5
+        uses: actions/setup-go@v6
 
       - name: Install Dashing
         run: go install github.com/technosophos/dashing@latest
 
       - name: Set up Python
-        uses: actions/setup-python@v5
+        uses: actions/setup-python@v6
         with:
           python-version: 3.13
 
@@ -26,12 +26,19 @@ jobs:
           python -m pip install --upgrade pip
           pip install -r requirements.txt
 
-      - name: Build the docset
-        run: |
-          make
+      - name: Build the docsets
+        run: make
 
       - name: Upload the docsets
-        uses: actions/upload-artifact@v4
+        uses: actions/upload-artifact@v7
         with:
           name: docset-bundle
           path: out/sublime-*.docset
+          if-no-files-found: error
+
+      # Do this at the end to upload the zip even if we fail
+      - name: Check for dirty DB dump
+        run: |
+          git status
+          git diff
+          git diff-files --quiet

.gitignore

@@ -1 +1,6 @@
+# Compiled files
+*.py[cd]
+__pycache__/
+
+# Build artifacts
 out/