dig-message 0.5.1

The DIG Network generic base message protocol: the byte-deterministic Chia-Streamable envelope + InnerMessage, length-framed size-bounded framing, additive compression (raw + zstd, decompression-bomb guarded), and the extensible message-type registry that every directed (1:1 / group) e2e-sealed peer message rides.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94

name: Publish to crates.io

# Tag-driven release: pushing a version tag `vX.Y.Z` runs the gates, publishes to crates.io, and
# cuts a GitHub Release. A normal push to `main` runs the gates only (see ci.yml) — it does NOT
# publish. Mirrors the sibling DIG crates so the same org secrets apply. dig-ipc-protocol is a leaf
# crate with NO dig-* dependencies, so there is no release-ordering constraint on other DIG crates.

on:
  push:
    tags:
      - 'v*'
  workflow_dispatch:
    inputs:
      version:
        description: 'Version to publish (e.g., v0.1.0)'
        required: true
        type: string

permissions:
  contents: write

env:
  CARGO_TERM_COLOR: always

jobs:
  # No fmt/clippy/test/coverage re-run here: the PR that produced this tagged commit already went
  # through ci.yml's full gate set before it was allowed to merge. This workflow is build + package +
  # publish only.
  publish:
    name: Publish to crates.io
    runs-on: ubuntu-latest
    steps:
      - name: Checkout code
        uses: actions/checkout@v4

      - name: Install Rust toolchain
        uses: dtolnay/rust-toolchain@stable
        with:
          toolchain: stable

      - name: Cache dependencies
        uses: Swatinem/rust-cache@v2

      - name: Verify the package builds
        run: cargo build --release

      - name: Verify the package can be packaged
        run: cargo package --locked

      - name: Check CARGO_REGISTRY_TOKEN is set
        run: |
          if [ -z "${{ secrets.CARGO_REGISTRY_TOKEN }}" ]; then
            echo "CARGO_REGISTRY_TOKEN secret is not set in repository settings"
            exit 1
          fi

      - name: Publish to crates.io
        run: cargo publish --locked
        env:
          CARGO_REGISTRY_TOKEN: ${{ secrets.CARGO_REGISTRY_TOKEN }}

  create-release:
    name: Create GitHub Release
    runs-on: ubuntu-latest
    needs: publish
    if: startsWith(github.ref, 'refs/tags/v')
    steps:
      - name: Checkout code
        uses: actions/checkout@v4

      - name: Extract version from tag
        id: extract_version
        run: echo "VERSION=${GITHUB_REF#refs/tags/v}" >> "$GITHUB_OUTPUT"

      - name: Create GitHub Release
        uses: softprops/action-gh-release@v2
        with:
          tag_name: ${{ github.ref_name }}
          name: "dig-ipc-protocol v${{ steps.extract_version.outputs.VERSION }}"
          body: |
            ## dig-ipc-protocol v${{ steps.extract_version.outputs.VERSION }}

            Canonical dig-app ⇄ dig-node IPC session/signing contract: domain-separated challenge /
            callback / user-sign message builders (app signs, engine verifies), frame bounds, the
            JSON-RPC control.session.* wire types + sign callback, the seam traits + generic role-
            halves, and the stable APP-SIGN error taxonomy.

            ### Installation
            ```toml
            [dependencies]
            dig-ipc-protocol = "${{ steps.extract_version.outputs.VERSION }}"
            ```
          draft: false
          prerelease: false