Hi, Aleksandr. Publishing documentation for already released versions is triggered by a commit(cherry-pick) to the release branch. The GitHub Actions workflow will run on branch update [1].
[1] https://github.com/apache/ignite/blob/master/.github/workflows/publish-website-on-branch-update.yml On Mon, Apr 20, 2026 at 4:07 PM Aleksandr Chesnokov <[email protected]> wrote: > > Hi Igniters, > I noticed broken images on the Performance Statistics documentation page: > https://ignite.apache.org/docs/ignite2/2.17.0/extensions-and-integrations/performance-statistics > > The page references images like: > https://ignite.apache.org/docs/assets/images/integrations/performance-statistics/perf_stat_2.jpg > > These URLs return 404. The issue seems to affect multiple published Ignite > 2 versions, not only 2.17.0. > > Other documentation images are served from the versioned path (e.g. > /docs/ignite2/<version>/images/...), while these screenshots are referenced > from /docs/assets/images/... > > It looks like these images are stored under docs/assets/images/..., but > since they are used in the documentation, they probably should be placed > under docs/_docs/images/... and referenced as images/... in AsciiDoc. > > I can fix this as part of IGNITE-28579. However, this would only affect > future builds and not already published versioned docs. > > What is the recommended way to fix broken assets in already published > documentation? > > -- > Best regards, > Aleksandr Chesnokov -- Best wishes, Amelchev Nikita
