Publish Rust crates using GitHub Actions

Features

• Reads manifests to get info about crates and dependencies
• Checks versions of external dependencies to be exists in registry
• Checks matching paths and versions of internal dependencies
• Checks that no changes happened since published release when version of internal dependency is not changed
• Skips publishing of internal dependencies which does not updated
• Publishes updated crates in right order according to dependencies
• Awaits when published crate will be available in registry before publishing crates which depends from it
• Works fine with workspaces without cyclic dependencies

Unimplemented features

• Support different registries than crates.io

Inputs

• token GitHub API token (github.token by default)
• path Sets path to crate or workspace ('.' by default)
• args Extra arguments for cargo publish command
• registry-token Cargo registry token (not used when dry-run: true)
• dry-run Set to 'true' to bypass exec cargo publish

Usage examples

Basic usage (Cargo.toml sits in repository root):

steps:
    - uses: actions/checkout@v2
    - uses: actions-rs/toolchain@v1
      with:
          toolchain: stable
          override: true
    - uses: katyo/publish-crates@v1
      with:
          registry-token: ${{ secrets.CARGO_REGISTRY_TOKEN }}

Advanced usage (Cargo.toml sits in 'packages' subdir, and you would like to skip verification and bypass real publishing):

steps:
    - uses: actions/checkout@v2
    - uses: actions-rs/toolchain@v1
      with:
          toolchain: stable
          override: true
    - uses: katyo/publish-crates@v1
      with:
          path: './packages'
          args: --no-verify
          dry-run: true