Extending the GitHub workflow for documentation for regular execution

[froschdesign]

The documentation is not updated for repositories without a new version. Changes to the documentation theme therefore do not affect the component documentation.

Example

laminas-escaper

• the API tools are still present
• content is missing in the footer
• the copyright year is out of date
• icons are missing

Suggestion

Add a schedule event that additionally creates the documentation.

I don't know if this is a problem:

In a public repository, scheduled workflows are automatically disabled when no repository activity has occurred in 60 days.

[gsteel]

Considering that renovate will touch repositories fairly regularly with lock file updates, it should only be a problem for repositories that are stuck on failing CI, or those that have very few dependencies such as laminas-xml, however, if the gh-pages branch is being committed during docs build, that should keep the schedule going too right?

[gsteel]

The other problem with building the docs is figuring out current-stable - the default branch could be an un-released major like laminas-validator right now. Looking at tags might work if we can extrapolate the current release series from that so that we can figure out the correct release branch to build for… Unsure if this is already handled.

[froschdesign]

…the default branch could be an un-released major like laminas-validator right now.

Good point.