[Feature Request]: Handle docs-build checks on non-`current` or `next` branches

[colleenmcginnis]

Prerequisites

• I have searched existing issues to ensure this feature hasn't already been requested
• I have tested using the latest version of docs-builder

What problem are you trying to solve?

In several repos, we publish from minor version branches instead of main. For example, in the logstash repo, we're currently publishing 9.2 to staging and 9.1 to prod. We're no longer publishing 9.0 anywhere. As a result, the docs-build check is failing on all 9.0 commits.

cc @reakaleek @alexcams

Proposed Solution

Can we adjust the workflow to prevent these CI failures from showing up without removing the workflow file from old branches when a new release branch is cut? If the branch doesn't match any version in the configuration file, can we just not run the later steps without making the check fail?

Examples and Research

No response

Alternative Solutions

We have to remember to remove the workflow file from old branches when a new minor version branch is created.

Additional Context

No response

How important is this feature to you?

Critical

[Mpdreamz]

Thanks for raising this @colleenmcginnis !

Fixed by #2095