ci: automate creation of GitHub releases and tags

.github/workflows/release-check.yml

@@ -0,0 +1,32 @@
+name: Release Checker
+
+on:
+  pull_request_target:
+    paths:
+      - "**/Cargo.toml"
+    types: [ opened, synchronize, reopened, labeled, unlabeled ]
+  workflow_dispatch:
+
+permissions:
+  contents: write
+  pull-requests: write
+
+concurrency:
+  group: ${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  release-check:
+    uses: ipdxco/unified-github-workflows/.github/workflows/[email protected]
+    with:
+      sources: |
+        [
+          "frc42_dispatch/Cargo.toml",
+          "frc42_dispatch/hasher/Cargo.toml",
+          "frc42_dispatch/macros/Cargo.toml",
+          "frc46_token/Cargo.toml",
+          "frc53_nft/Cargo.toml",
+          "fvm_actor_utils/Cargo.toml",
+          "fvm_dispatch_tools/Cargo.toml"
+        ]
+      separator: "@"

.github/workflows/releaser.yml

@@ -0,0 +1,32 @@
+name: Releaser
+
+on:
+  push:
+    paths:
+      - "**/Cargo.toml"
+  workflow_dispatch:
+
+permissions:
+  contents: write
+
+concurrency:
+  group: ${{ github.workflow }}-${{ github.sha }}
+  cancel-in-progress: true
+
+jobs:
+  releaser:
+    uses: ipdxco/unified-github-workflows/.github/workflows/[email protected]
+    with:
+      sources: |
+        [
+          "frc42_dispatch/Cargo.toml",
+          "frc42_dispatch/hasher/Cargo.toml",
+          "frc42_dispatch/macros/Cargo.toml",
+          "frc46_token/Cargo.toml",
+          "frc53_nft/Cargo.toml",
+          "fvm_actor_utils/Cargo.toml",
+          "fvm_dispatch_tools/Cargo.toml"
+        ]
+      separator: "@"
+    secrets:
+      UCI_GITHUB_TOKEN: ${{ secrets.UCI_GITHUB_TOKEN }}

RELEASE.md

@@ -0,0 +1,33 @@
+# Release Process
+
+This document describes the process for releasing a new version of the `actors-utils` project.
+
+## Current State
+
+1. Create a pull request which updates the [`version` in one or more `Cargo.toml` files](https://github.com/search?q=repo%3Afilecoin-project%2Factors-utils+path%3ACargo.toml+%2F%5Eversion+%3D%2F&type=code).
+   - Title the PR `chore: release Ɑ for Ƅ` where:
+      - `Ɑ` is what is being released like "all crates"
+      - `Ƅ` is the cause for the release like "fvm vX.Y.Z" or "nvXX"
+2. On such a release PR's creation, a [Release Checker](.github/workflows/release-check.yml) workflow will run. It will perform the following actions:
+    1. Extract the version from the modified `Cargo.toml` files, and process each crate in the workspace **independently**.
+    2. Check if a git tag for the version, using the `crate_name@version` as the pattern, already exists, and continue only if it does not.
+    3. Create a draft GitHub release with the version as the tag.
+    4. Comment on the pull request with a link to the draft release.
+2. **[MANUAL]** Run `cargo publish --dry-run` for each crate that is proposed to be released in the reverse dependency order.
+3. On pull request merge, a [Releaser](.github/workflows/release.yml) workflow will run. It will perform the following actions:
+    1. Extract the version from the modified `Cargo.toml` files, and process each crate in the workspace **independently**.
+    2. Check if a git tag for the version, using the `crate_name@version` as the pattern, already exists, and continue only if it does not.
+    3. Check if a draft GitHub release with the version as the tag exists.
+    4. If the draft release exists, publish it. Otherwise, create a new release with the version as the tag.
+4. **[MANUAL]** Run `cargo publish` for each crate that has been released in the reverse dependency order.
+   - You will need to be part of [fvm-create-owners](https://github.com/orgs/filecoin-project/teams/fvm-crate-owners) to do this per https://crates.io/crates/fvm_actor_utils .
+
+#### Known Limitations
+
+1. `cargo publish --dry-run` has to be run manually.
+2. `cargo publish` has to be run manually.
+
+#### Possible Improvements
+
+1. Run `cargo publish --dry-run` in the reverse dependency order automatically. Use a local registry to simulate the dependencies that are not yet published.
+2. Run `cargo publish` in the [**reverse dependency order**](#crate-dependency-graph) automatically after the merge.