|
Revision tags: dev, v36.0.9, v44.0.1, v43.0.2, v36.0.8, v24.0.8, v44.0.0, v43.0.1, v42.0.2, v36.0.7, v24.0.7, v43.0.0, v42.0.1, v41.0.4, v42.0.0, v40.0.4, v36.0.6, v24.0.6, v41.0.3 |
|
| #
c190d7c4 |
| 04-Feb-2026 |
Alex Crichton <[email protected]> |
Document the effect of CI outages on releases (#12521)
* Document the effect of CI outages on releases
Clearly specify in our documentation that we are entirely subject to the
shims of Azure and Gi
Document the effect of CI outages on releases (#12521)
* Document the effect of CI outages on releases
Clearly specify in our documentation that we are entirely subject to the
shims of Azure and GitHub Actions. If they're down we just simply can't
do a release and there's nothing we can do about it. Document this both
for ourselves and for external users to understand our own limitations.
An offer is made as well in case a company is willing to donate
resources (e.g. money or engineering) to improve the situation as well.
* Update docs/stability-release.md
Co-authored-by: Nick Fitzgerald <[email protected]>
---------
Co-authored-by: Nick Fitzgerald <[email protected]>
show more ...
|
|
Revision tags: v41.0.2, v41.0.1, v36.0.5, v40.0.3, v41.0.0, v36.0.4, v39.0.2, v40.0.2, v40.0.1, v40.0.0, v39.0.1, v39.0.0, v38.0.4, v37.0.3, v36.0.3, v24.0.5, v38.0.3 |
|
| #
d335c07f |
| 22-Oct-2025 |
Alex Crichton <[email protected]> |
Adjust vulnerability runbook to not open PR version bumps (#11919)
Historically this was needed to give some time to figure out CI issues,
if any. Nowadays though we test all release branches weekly
Adjust vulnerability runbook to not open PR version bumps (#11919)
Historically this was needed to give some time to figure out CI issues,
if any. Nowadays though we test all release branches weekly to ensure
their CI is running so any failures should be at most a week old. Given
that there's no need to open version bumps ahead of time. This also
avoids leaking information in advance disclosure about affected versions
which narrows the range of the where the bug could be.
show more ...
|
|
Revision tags: v38.0.2, v38.0.1, v37.0.2, v37.0.1, v37.0.0, v36.0.2, v36.0.1, v36.0.0, v35.0.0, v24.0.4, v33.0.2, v34.0.2, v34.0.1, v33.0.1, v24.0.3, v32.0.1, v34.0.0 |
|
| #
7bf9be52 |
| 20-May-2025 |
Andrew Brown <[email protected]> |
Fix a missing link in the vulnerability runbook (#10818)
|
|
Revision tags: v33.0.0 |
|
| #
63f8267a |
| 02-May-2025 |
Alex Crichton <[email protected]> |
Add RustSec filing to our advisory process (#10708)
All our historical advisories have now been back-filled and it has been
ok'd to have a mostly empty description that points to the GitHub
advisori
Add RustSec filing to our advisory process (#10708)
All our historical advisories have now been back-filled and it has been
ok'd to have a mostly empty description that points to the GitHub
advisories we publish in this repository. Update the runbook process
with a final step mentioning RustSec.
Closes #10344
show more ...
|
|
Revision tags: v32.0.0 |
|
| #
2de55ccf |
| 31-Mar-2025 |
Alex Crichton <[email protected]> |
Add documentation for Wasmtime's LTS releases (#10481)
* Add documentation for Wasmtime's LTS releases
With Wasmtime's [LTS
releases](https://github.com/bytecodealliance/rfcs/pull/42) this commit
d
Add documentation for Wasmtime's LTS releases (#10481)
* Add documentation for Wasmtime's LTS releases
With Wasmtime's [LTS
releases](https://github.com/bytecodealliance/rfcs/pull/42) this commit
documents the various process changes and updates to our release
process. Additionally some improvements are made to the release
documentation with respect to showing current versions.
* Refactor some backport criteria docs
* Review comments
show more ...
|
|
Revision tags: v31.0.0, v30.0.2, v30.0.1, v30.0.0, v29.0.1, v29.0.0, v28.0.1, v28.0.0, v27.0.0, v26.0.1, v25.0.3, v24.0.2, v26.0.0 |
|
| #
866ede95 |
| 10-Oct-2024 |
Alex Crichton <[email protected]> |
Document a Wasmtime-specific vulnerability runbook (#9433)
This commit codifies the process [documented
here](https://github.com/bytecodealliance/rfcs/blob/main/accepted/vulnerability-response-runbo
Document a Wasmtime-specific vulnerability runbook (#9433)
This commit codifies the process [documented
here](https://github.com/bytecodealliance/rfcs/blob/main/accepted/vulnerability-response-runbook.md)
in the Wasmtime repository as it relates to Wasmtime itself. There's
also a few minor changes from recent advisories such as:
* We'll no longer use the publish-the-changes-from-the-advisory feature
from GitHub. That basically just doesn't work any more.
* PRs will instead be manually created to have CI run on them to weed
out any issues.
* Details about preparing the `main` branch ahead of the release are
interleaved with the rest of the runbook.
The intention is to supplement the official runbook with
Wasmtime-specific information and flesh out a few minor steps we're
following that are "extra" here too.
show more ...
|