[Bug]: Docs Published when PR is accepted Not When Code is Live

[apedley]

What happened?

Right now the docs are published when changes to them are accepted instead of when a release is made. This causes drift between production and the documentation.

Comes from this discussion: #1600

Steps to reproduce

PR dos

Expected behavior

Docs should be published when a release is made to be sure the version number lines up.

How are you running SparkyFitness?

Docker Compose

SparkyFitness version

v0.17.3

Which area is affected?

Other

Docker Compose & Environment Configuration

Runtime Logs (Server, Web, or Mobile)

Screenshots or Screen Recordings

No response

Anything else?

No response

[hiSandog]

Publishing from the release tag or release commit would keep the default docs aligned, but contributors still need previews for documentation PRs. A clean split is to build an unlisted preview artifact on PRs and deploy production docs only from the same tag that produces the application images, recording the version/commit in the site. If multiple supported releases exist, versioned docs are safer than making every merged doc wait for the next release while the stable site remains ambiguous.

[apedley]

Between releases we can just read the markdown file or run the docs locally.