[Feature/Request] - Update the docs/render job to render only on a release-cut instead of push to main

[kquinsland]

or, ideally, add a header to the docs site that allows browsing by version.

I just spent the better part of two hours trying to get the /mcp component working on an instance of 0.16.9 that I have deployed.

The docs say this:

The MCP server is now served in-process by the main SparkyFitness server at POST /mcp. There is no separate MCP service to run.

But what the docs don't say is that this feature has yet to land in a stable release. For users of 0.16.9... the quote from the docs above is ... wrong.

At least make the docs page default to the current release and not main!

---

I am not very familiar with how nuxt works / it does not appear to support versions out of the box but it might be possible to get something similar by doing this:

# ...
# Build docs at ~HEAD
      - name: Build Latest Docs
        run: |
          NUXT_APP_BASE_URL=/ npx nuxt build --preset github_pages
          mkdir -p final-site
          cp -r .output/public/* final-site/

      # 2. Loop through your git tags, check out each, and build into a subfolder
      - name: Build Historical Tagged Versions
        run: |
          for tag in $(git tag -l "v*"); do
            echo "Building documentation for version $tag"
            git checkout $tag
            
            # Install dependencies specific to that version tag if needed
            npm ci 
            
            # Build Nuxt telling it that its base URL is /vX.X.X/
            NUXT_APP_BASE_URL=/$tag/ npx nuxt build --preset github_pages
            
            # Move it to a subfolder in our final deployment directory
            mkdir -p final-site/$tag
            cp -r .output/public/* final-site/$tag/
          done
          
          # Switch back to main branch so subsequent actions don't break
          git checkout main
# ...

And then a basic / static "using the docs, browsing by version..." note so it's relatively straight-forward for people to discover that the docs can be browsed by tag/version

[apedley]

Publishing the docs to gh pages only at releases would fix it. Sorry about that.

[kquinsland]

Publishing the docs to gh pages only at releases would fix it. Sorry about that.

No worries. Once I figured out what the issue was i felt dumb for not checking sooner!
I get the value of having a "preview" version of the docs rendered live as well as the "stable/latest" version ... but a banner or some other "hey, you're browsing $latest which is not :stable..." indicator would be appreciated.