Skip to content

Latest commit

 

History

History
68 lines (46 loc) · 2.67 KB

RELEASING.md

File metadata and controls

68 lines (46 loc) · 2.67 KB
Raw

Release Checklist

These steps assume that you've checked out the scale-info-legacy repository and are in the root directory of it.

  1. Ensure that everything you'd like to see released is on the main branch.

  2. Create a release branch off main, for example release-v0.1.0. The branch name should start with release so that we can target commits with CI. Decide how far the version needs to be bumped based on the changes to date. If unsure what to bump the version to (e.g. is it a major, minor or patch release), check with the Parity Tools team.

  3. Check that you're happy with the current documentation.

    cargo doc --open --all-features

    CI checks for broken internal links at the moment. Optionally you can also confirm that any external links are still valid like so:

    cargo install cargo-deadlinks
cargo deadlinks --check-http -- --all-features

    If there are minor issues with the documentation, they can be fixed in the release branch.

  4. Bump the crate version in Cargo.toml to whatever was decided in step 2.

  5. Update CHANGELOG.md to reflect the difference between this release and last. If you're unsure of what to add, check with the Tools team.

    You should look through the commit history on main to find the code changes since the last release (eg git log --pretty LAST_VERSION_TAG..HEAD).

    Looking at the closed PRs can also help to provide details for the changes.

  6. Commit any of the above changes to the release branch and open a PR in GitHub with a base of main.

  7. Once the branch has been reviewed and passes CI, merge it.

  8. Now, we're ready to publish the release to crates.io.

    Checkout main, ensuring we're looking at that latest merge (git pull).

    Next, do a final sanity check to make sure there are no new issues:

    cargo fmt
cargo clippy --all-targets
cargo test --all-targets
cargo test --doc

    If we're happy with everything, proceed with the release:

    cargo publish

  9. If the release was successful, then tag the commit that we released in the main branch with the version that we just released, for example:

    git tag v0.1.0 # use the version number you've just published to crates.io, not this one
git push --tags

    Once this is pushed, go along to the releases page on GitHub and draft a new release which points to the tag you just pushed to main above. Copy the changelog comments for the current release into the release description.