From 43fe34f309224cf03383e405b29ee2508d99db0e Mon Sep 17 00:00:00 2001
From: Jeremy Stanley <fungi@yuggoth.org>
Date: Mon, 18 Apr 2022 19:20:55 +0000
Subject: [PATCH] Publish documentation at every release

We normally publish documentation updates in the promote pipeline,
using documentation built in the gate. As a result, the published
docs tend to lag behind release events until the next post-release
change lands. Run a separate docs build and publish it on release,
so that release notes and version information included in the
documentation reflect the most recent tag prior to the next change
merging (which for stable projects like this one, could be a while).
Override the tag jobvar to force publication to the branch path
rather than using a version-specific tree.

Change-Id: Ibf1ecfa0420a3c170beb79c14a9a9ef13fea9046
Depends-On: https://review.opendev.org/838525
---
 .zuul.yaml | 1 +
 1 file changed, 1 insertion(+)

diff --git a/.zuul.yaml b/.zuul.yaml
index 1379ba1e..c6f373a1 100644
--- a/.zuul.yaml
+++ b/.zuul.yaml
@@ -21,3 +21,4 @@
     release:
       jobs:
         - opendev-release-python
+        - opendev-publish-unversioned-tox-docs