Update release notes

RELEASE.md

@@ -17,8 +17,12 @@ If you want to release the packages on crates.io, follow this process:
     Check that the packages it complains about actually have the specified version, and if so,
     it's safe to proceed.
 7. Create a PR named `crates.io: Release <version>`. Get a review and merge it.
-8. From the main branch _after_ you merge it, run `cargo ws publish --publish-as-is`.
+8. From the main branch _after_ you merge it, run `cargo ws publish --publish-as-is --allow-dirty`.
   - The `--publish-as-is` argument skips the versioning step, which you already did before.
+  - The `--allow-dirty` argument is required, because `cargo ws` temporarily removes dev-dependencies
+    during publishing.
+  - Important: if something fails and you have to do changes to the code, it's safe to run the same
+    command again. `cargo ws` will skip already published packages.
 9. If something goes wrong, see recommendations below.
 10. If everything is OK, create a tag: `git tag v<version>`, e.g. `git tag v0.150.4`
 11. `git push --tags`