Skip to content

A lightweight WebAssembly runtime that is fast, secure, and standards-compliant

Document the effect of CI outages on releases (#12521)

Alex Crichtonc190d7c48263
diff --git a/docs/security-vulnerability-runbook.md b/docs/security-vulnerability-runbook.md
index 2441783eaf..2887646df4 100644
--- a/docs/security-vulnerability-runbook.md
+++ b/docs/security-vulnerability-runbook.md
@@ -69,7 +69,10 @@ is created these steps are followed:
going to be patched. Patch notes should be included with the private PRs, so
no need to worry about that. Plan on merging these PRs after the PRs below
are merged. Note that CI should be green as we test that it's green weekly
- for all supported branches, but if it's not you'll need to fix that.
+ for all supported branches, but if it's not you'll need to fix that. GitHub
+ Actions has a nontrivial chance of having an outage during a release. If
+ this is the case all that can be done is waiting for the outage to be
+ resolved.
[online trigger]: https://github.com/bytecodealliance/wasmtime/actions/workflows/release-process.yml
diff --git a/docs/stability-release.md b/docs/stability-release.md
index 09ecae3b98..bc07ccb913 100644
--- a/docs/stability-release.md
+++ b/docs/stability-release.md
@@ -153,3 +153,24 @@ time warrant patch releases for Wasmtime.
[rfc4]: https://github.com/bytecodealliance/rfcs/blob/main/accepted/wasmtime-one-dot-oh.md
[RFC process]: https://github.com/bytecodealliance/rfcs
+
+## Releases and "CI Weather"
+
+Wasmtime relies on GitHub Actions to perform a release. This is true for both
+normal releases and security releases. GitHub Actions has become much less
+reliable over time and is often subject to widespread outages which can prevent
+Wasmtime from making a release. At this time Wasmtime has no alternative for
+making a release and we're entirely subject to the whims of Azure and GitHub
+Actions and how they're doing that day. If there is an outage when a release is
+being made then Wasmtime will not be able to make a release. This can affect the
+timely publish of a security release, for example. We do our best to keep tabs
+on the status of GitHub Actions and will publish a release once it recovers if
+there's an outage.
+
+Wasmtime as a project does not currently have the resources to dedicate to
+self-hosted runners, different CI providers, or maintaining escape hatches to
+perform releases locally instead of CI. If you maintain an embedding of
+Wasmtime and this caveat is unacceptable to you please feel free to reach out.
+We would be happy to talk about coordinating alternative CI architecture coupled
+with external investment in maintainership. For now, though, GitHub Actions is
+the best option available to us even with its unreliability.