Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[skip ci] Update release notes #7

Merged
merged 1 commit into from
Aug 16, 2024
Merged

[skip ci] Update release notes #7

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion RELEASE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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`
Expand Down