Please feel free to open PRs! But first make sure you code passes tests, and please add tests for new features:
cargo test --all-featuresAlso format your code and check it with clippy before submitting a PR:
cargo fmt
cargo clippy --workspaceThe changelog is managed by git-cliff which will run with the release action.
You can preview the changelog with:
git cliff | lessTo cut a release, run:
cargo release {release type}or
git commit -am "release: 0.2.0"
git tag "v0.2.0"Where release type is one of: major, minor, patch.
The release page on GitHub will then be updated using cargo dist. You can preview this with:
cargo dist planand then run:
git push
git push --tagsIf the release workflow fails, fix the issue (e.g. update cargo-dist-version in dist-workspace.toml, then run dist generate-ci), commit, push to main, and re-tag:
gh release delete v0.X.Y --yes
git push origin :refs/tags/v0.X.Y
git tag -d v0.X.Y
git tag v0.X.Y
git push origin v0.X.Y --force