Retire mkdocs, publish plugins to Reposilite, refresh docs

.github/workflows/publish-maven.yml

@@ -1,9 +1,9 @@
 name: publish-maven
 
 on:
-  workflow_run:
-    workflows: ["docs"]
-    types: [completed]
+  # Dispatched by release.yml after the tag is created (documentation moved to
+  # the separate MagicUtilsWebsite project, so there is no docs workflow to chain
+  # from anymore). Also runnable manually.
   workflow_dispatch:
 
 # Publishing targets the self-hosted Reposilite (maven.theroer.dev) over HTTPS,
@@ -21,14 +21,13 @@ jobs:
   # one-line edit to targets.properties — this workflow never lists targets.
   resolve-matrix:
     runs-on: ubuntu-latest
-    if: ${{ github.event_name == 'workflow_dispatch' || github.event.workflow_run.conclusion == 'success' }}
     outputs:
       units: ${{ steps.matrix.outputs.units }}
       repo_url: ${{ steps.coords.outputs.repo_url }}
     steps:
       - uses: actions/checkout@v4
         with:
-          ref: ${{ github.event.workflow_run.head_sha || github.sha }}
+          ref: ${{ github.sha }}
       - uses: actions/setup-java@v5
         with:
           distribution: 'temurin'
@@ -61,7 +60,7 @@ jobs:
     steps:
       - uses: actions/checkout@v4
         with:
-          ref: ${{ github.event.workflow_run.head_sha || github.sha }}
+          ref: ${{ github.sha }}
       - uses: actions/setup-java@v5
         with:
           distribution: 'temurin'
@@ -88,7 +87,7 @@ jobs:
     steps:
       - uses: actions/checkout@v4
         with:
-          ref: ${{ github.event.workflow_run.head_sha || github.sha }}
+          ref: ${{ github.sha }}
       - uses: actions/setup-java@v5
         with:
           distribution: 'temurin'

.github/workflows/release.yml

@@ -88,20 +88,16 @@ jobs:
     runs-on: ubuntu-latest
     needs: [resolve, tag]
     steps:
-      - name: Dispatch docs and javadoc workflows
+      - name: Dispatch Maven publish
         env:
           GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
         run: |
           VERSION="${{ needs.resolve.outputs.version }}"
           TAG="${{ needs.resolve.outputs.tag }}"
-          # Use workflow_dispatch (not the tag push) to launch docs.yml.
-          # This avoids GitHub's GITHUB_TOKEN-pushed-tag rule that suppresses
-          # downstream workflow_run events — publish-maven.yml will then see
-          # docs as a workflow_dispatch source and trigger correctly.
-          gh workflow run docs.yml --repo "$GITHUB_REPOSITORY" --ref "$TAG" \
-            -f version="$VERSION" \
-            -f alias=stable \
-            -f set_default=true
-          gh workflow run javadoc.yml --repo "$GITHUB_REPOSITORY" --ref "$TAG" \
+          # Documentation lives in the separate MagicUtilsWebsite (Nuxt) project,
+          # so the release only dispatches the Maven publish. Use workflow_dispatch
+          # (not the tag push) to avoid GitHub's GITHUB_TOKEN-pushed-tag rule that
+          # suppresses downstream workflow_run events.
+          gh workflow run publish-maven.yml --repo "$GITHUB_REPOSITORY" --ref "$TAG" \
             -f version="$VERSION"
-          echo "Dispatched docs.yml and javadoc.yml for $TAG"
+          echo "Dispatched publish-maven.yml for $TAG"

README.md

@@ -43,7 +43,10 @@ dependencies {
 }
 ```
 
-Shared bundle install:
+Standalone install: `magicutils-fabric-bundle` is also a runnable Fabric mod on
+its own — drop the jar into `mods/` and it boots the shared MagicUtils runtime
+and registers the `/magicutils` (alias `/mu`) command with diagnostics
+sub-commands, no host mod required. Depend on it from your mod with:
 
 ```kotlin
 dependencies {
@@ -124,8 +127,9 @@ https://magicutils.theroer.dev/getting-started/quickstart/
 
 ## Notes
 
-- GitHub Pages Maven does not host `*-all` shaded artifacts. Use the thin jars
-  from Maven or build shaded jars locally when you need them.
+- Artifacts are published to the self-hosted Reposilite at
+  `https://maven.theroer.dev/releases`. Both the thin jars and the `*-all`
+  shaded jars (where produced) are available there.
 
 ## Reflection Automation
 
@@ -142,14 +146,14 @@ new reflection usage automatically.
 
 ## Release Helper
 
-Maintainers can prepare and dispatch a tagged release with:
+Maintainers cut a tagged release with the Gradle release tasks (the former
+`scripts/publish_release.py` is deprecated):
 
 ```bash
-python3 scripts/publish_release.py 1.19.2 --dry-run
-python3 scripts/publish_release.py 1.19.2
+./gradlew releasePreflight -Pversion=X.Y.Z   # validate version + tags, no changes
+./gradlew release -Pversion=X.Y.Z            # preflight → bump → dispatch release.yml
 ```
 
-The helper mirrors the GitHub Actions flow: it can sync `gradle.properties`,
-push the selected branch, wait until `origin/<ref>` resolves to the pushed
-commit, and then dispatch `release.yml`. Optional flags are available for
-manual `javadoc.yml` and `publish-maven.yml` dispatches when needed.
+`release` validates the version, bumps `gradle.properties`, commits, and
+dispatches `release.yml`. CI then tags `vX.Y.Z`, builds docs/javadoc, and
+publishes the artifacts to Reposilite. See `RELEASING.md` for the full flow.