The signing subkey for the 2026.1/Gazpacho Cycle was preemptively revoked and replaced on 2026-01-09 through project-config change I52abd4f99d39a3d57c4c08af086bbed5a62f0b68 as a precaution coincident with the Zuul 13.1.0 security fix: https://lists.zuul-ci.org/archives/list/zuul-announce@lists.zuul-ci.org/thread/2WHXPBPRLFF6ZNSSZ3AKOBBBHMWY4YNR/ Since this is the first time we've revoked a subkey, and listing revoked subkeys is not enabled by default in GnuPG, adjust our export instructions in order to make sure they're included in the preamble for transparency. Change-Id: I072c9327527a892bc2bae7edd54eb6a0cdd9a07c Signed-off-by: Jeremy Stanley <fungi@yuggoth.org>
OpenStack Releases
This repository is used to drive release automation for OpenStack release deliverables, ultimately publishing them on the https://releases.openstack.org/ website.
Changes to this repository are proposed using Gerrit at https://review.opendev.org. This repository is managed by the OpenStack Release Management team.
For more information on how to use this repository, please read our reference documentation.
Who should use this repository
All official OpenStack software should go through the OpenStack Release Management team team to produce releases. Exceptions to this rule are granted by the Technical Committee and documented in the openstack/governance repository ('release-management' key in reference/projects.yaml).
Deliverables managed by teams not under OpenStack governance should follow the tagging instructions in the infra manual.
More information
You can reach the Release Management team on the #openstack-release channel on OFTC IRC <https://www.oftc.net/>, or by sending an email with '[release]' as a subject prefix to the openstack-discuss mailing-list.