Since gtk-rs has multiple crates which have inter-dependencies, it's a bit painful to make a new release. So here are the multiple steps:
cratebranch in every repository (starting with
sysand ending with
- Update crate version in
Cargo.tomland the number of its
- Open pull requests to
cratebranches to corresponding repositories.
- Once pull requests have been merged, publish all crates to
- Generate new docs (don't forget
cargo doc!). To do so, go to
cratebranch) and run
cargo doc --features=embed-lgpl-docs. Then run
cp -r target/doc/* ../docs(where
docsis the corresponding directory for the
gtk-rs/docsrepository). Commit then push the changes to the
docs(make a pull request and all the usual stuff...).
gtk-rs/examplesrepository (by opening a pull request of course).
- Update badges version number in the
- Write a blog post (add the file into
gtk-rs.github.iorepository) announcing the new release.
NOTE: Pull requests on the
crate branch aren't build.
Using this tool
I don't recommend it if you're not a member of the
gtk-rs organization but just in case:
python3 src/release.py -m MEDIUM -t [Your github token here]