Re-add pending release notes

Now that 3.19.1 has been merged, re-add these notes (with modified ids)
so they will appear in the next release.

Change-Id: If2906763c51f1c829b1bbc1c5672b5e3f3746c6f

releasenotes/notes/admin_web_api_promote-2-b72d137af109341d.yaml

@@ -0,0 +1,5 @@
+---
+features:
+  - |
+    The action "promote" is now available via the tenant-scoped REST API using
+    the zuul cli.

releasenotes/notes/ansible-2.7-2-4b6504e46c18cc58.yaml

@@ -0,0 +1,4 @@
+---
+upgrade:
+  - |
+    Support for Ansible 2.7 has been removed.

releasenotes/notes/builds_held_attribute-2-711abd33402ce037.yaml

@@ -0,0 +1,10 @@
+---
+features:
+  - |
+    Builds in the SQL reporter have a "held" attribute set to True if the build
+    triggered a autohold request. Builds can be filtered by held status.
+upgrade:
+  - |
+    If using a SQL reporter, the zuul_builds table will be updated with a new
+    'held' column. The `zuul-scheduler` and `zuul-web` services need to be restarted
+    together for the change to take effect.

releasenotes/notes/change-missing-build-url-2-6df030ae3d8793af.yaml

@@ -0,0 +1,7 @@
+---
+upgrade:
+  - |
+    Previously the SqlReporter would record the job name in the database in
+    place of the url if the url was empty. This has now been updated to store
+    a null in the database for that case. Zuul will automatically run a
+    database migration to correct old values.

releasenotes/notes/config-zuul-ignore-2-695aafd639d874ea.yaml

@@ -0,0 +1,6 @@
+---
+features:
+  - |
+    Subdirectories of ``zuul.d`` or ``.zuul.d`` can be ignored when
+    reading configuration by placing a ``.zuul.ignore`` file inside
+    them.

releasenotes/notes/find-executor-2-cd3f110245c499c1.yaml

@@ -0,0 +1,4 @@
+---
+features:
+  - |
+    The ``find`` module is now allowed to run on the executor.

releasenotes/notes/github-checks-dequeue-2-643b7f757ca4d49c.yaml

@@ -0,0 +1,6 @@
+---
+features:
+  - |
+    Changes can now be dequeued via the Github checks API. If a github
+    reporter is configured to use the checks API, all running checks will
+    provide a custom "Abort" action.

releasenotes/notes/github-review-requirement-2-874b2dd8c6fa1293.yaml

@@ -0,0 +1,6 @@
+---
+features:
+  - |
+    Zuul now respects GitHub review requirements when enqueuing into gate
+    pipelines. This works for github.com and GitHub Enterprise starting with
+    version 2.21.0.

releasenotes/notes/intermediate-jobs-2-101e04e7e1497afa.yaml

@@ -0,0 +1,5 @@
+---
+features:
+  - Jobs may specify the new ``intermediate`` flag to note they may only
+    be inherited by abstract jobs.  This can be useful if building a job
+    hierarchy where wish to limit where a base job is instantiated.

releasenotes/notes/mqtt-report-build-page-1780225ca98c7457.yaml

@@ -0,0 +1,13 @@
+---
+fixes:
+  - |
+    Although the documentation states that the MQTT reporter reports the build's
+    log_url, this was only true as long as :attr:`tenant.report-build-page` was
+    disabled. As soon as the setting was enabled, the MQTT reporter reported the
+    url to the build's result page in Zuul. As MQTT is meant to be consumed by
+    machines, this broke use cases like log post processing.
+
+    This was fixed so that the :attr:`<mqtt schema>.buildset.builds.log_url` now
+    always contains the log url, while an additional field
+    :attr:`<mqtt schema>.buildset.builds.web_url` contains the url to the
+    build's result page if :attr:`tenant.report-build-page` is enabled.

releasenotes/notes/non-final-builds-2-d9024df868c7e038.yaml

@@ -0,0 +1,9 @@
+---
+features:
+  - |
+    The builds/ and buildset/ API endpoints now include information about
+    retried builds. They are called non-final as those are all builds that
+    were retried at least once and thus weren't visible to the user so far.
+
+    The builds/ API can filter those retried builds and you might exclude
+    them from API result by setting ``final=false`` in the API request.

releasenotes/notes/python35-2-fd8e7f7f577b55e6.yaml

@@ -0,0 +1,4 @@
+---
+upgrade:
+  - |
+    Support for running Zuul under Python 3.5 has been dropped.

releasenotes/notes/report-build-page-2-49088c2b0a36e1b7.yaml

@@ -0,0 +1,17 @@
+---
+features:
+  - |
+    An option to use the URL of the Zuul build page when reporting has
+    been added.  This fetaure requires that all the pipelines in the
+    tenant have a :ref:`SQL reporter<sql_reporter>` configured, and at
+    least one of :attr:`tenant.web-root` or :attr:`web.root` must be
+    defined.
+
+    See :attr:`tenant.report-build-page`.
+upgrade:
+  - |
+    As further integration with the web interface is planned, the
+    :attr:`web.root` setting in ``zuul.conf`` is marked required and
+    future releases may error if it is missing.  Please add it to your
+    configuration now.  See :attr:`tenant.web-root` for additional
+    information about whitelabel tenants.

releasenotes/notes/scoping_REST_API-2-866574c4d73c577b.yaml

@@ -0,0 +1,11 @@
+---
+features:
+  - |
+    REST API: authorizations: add a tenant-scoped endpoint at
+    '/api/tenant/{tenant}/authorizations'. Calling the endpoint will return
+    a list of admin tenants limited to the scoped tenant, if the user has admin
+    privileges on it.
+deprecations:
+  - |
+    REST API: authorizations: the /api/user/authorizations endpoint is deprecated
+    in favor of the tenant-scoped endpoint. It will be removed next release.

releasenotes/notes/skip-host-keys-2-61418c8be322a825.yaml

@@ -0,0 +1,6 @@
+---
+features:
+  - |
+    Host key checking is now disabled for a host in the generated
+    Ansible inventory if ``host-key-checking`` is set to ``False``
+    in the corresponding nodepool config.