From dfe18a6ac14f099aa4aa4514fc93dbd666d6a120 Mon Sep 17 00:00:00 2001 From: Jonathan Schwender <55576758+jschwe@users.noreply.github.com> Date: Tue, 1 Sep 2026 10:40:58 +0800 Subject: [PATCH] release docs: Add stylo section Add instructions for requesting a stylo release Signed-off-by: Jonathan Schwender <55576758+jschwe@users.noreply.github.com> --- src/for-maintainers/release-process.md | 17 +++++++++++++++-- 1 file changed, 15 insertions(+), 2 deletions(-) diff --git a/src/for-maintainers/release-process.md b/src/for-maintainers/release-process.md index 9938431..1319a6e 100644 --- a/src/for-maintainers/release-process.md +++ b/src/for-maintainers/release-process.md @@ -14,7 +14,20 @@ The version bump should be merged **after** this commit, so that all changes men Create a branch with the name `release/vX.Y.Z`, based on the commit that bumped the version number (in `main`). If the date of merge was (significantly) later, and significant changes were made, then the release branch can also be based on an earlier commit and the version number bump backported / re-applied. -The branch should be pushed to the upstream servo repository. +The branch should be pushed to the upstream servo repository. + +### Request a stylo release + +In order to publish `servo` to crates.io we need a stylo release, corresponding to the git commit we depend on. +Check the stylo commit hash specified in servos Cargo.toml, and open an issue on stylo requesting a release based on that commit. +Usually the stylo release is handled by @Loirooriol. +Once the new stylo release has been published, we need to create a PR against the servo release branch to update stylo to the crates.io version. +Create a branch based on the release branch, and edit the `Cargo.toml` to depend on the released crates, like in this [servo stylo bump example]. +Note that not all crates share the same stylo workspace version number, so pure search and replace won't work. +The `servo` PR against the release branch will be merged with `rebase`, so be sure to squash your commits if you have more than one. + +[stylo]: https://github.com/servo/stylo +[servo stylo bump example]: https://github.com/servo/servo/commit/77fccacc1f1fdce10498d50173aafaa09d02879e ### Creating a draft release for testing @@ -52,4 +65,4 @@ Contact the dedicated signer of the macOS artifact and ask them to sign the rele This might take a while, so this should be done a couple of days before the planned release date. Finally, add our usual release notes summary, linking to the blog post and to the common issues section (check the previous release notes for examples). -Once the blog post is published, we publish the release. \ No newline at end of file +Once the blog post is published, we publish the release.