bbtree 0.1.3

Fastest B-tree.
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
95
96
97
98

name: Publish Release

# Publishes a merged release: a push to main that changes
# the version, by the same test as ci.yml's merge gate. Only that commit is
# published, never a later one that skipped the release checks, so to retry a
# failed publish, re-run its run.
on:
  push:
    branches: [main]
    paths: [Cargo.toml]

permissions:
  contents: read

env:
  CARGO_TERM_COLOR: always

jobs:
  detect:
    name: Detect a release
    runs-on: ubuntu-latest
    outputs:
      release: ${{ steps.version.outputs.changed }}
      version: ${{ steps.version.outputs.version }}
    steps:
      - uses: actions/checkout@v4

      - id: version
        uses: ./.github/actions/version-change
        with:
          base: ${{ github.event.before }}

  # Each step skips what an earlier attempt finished, so that a failed run can
  # be re-run.
  publish:
    name: Publish Crate and Release
    needs: detect
    if: needs.detect.outputs.release == 'true'
    runs-on: ubuntu-latest
    # Holds the crates.io token, and only main may deploy to it.
    environment: crates-io
    permissions:
      # The tag and the GitHub release.
      contents: write
      # To start fuzz.yml on main.
      actions: write
    concurrency:
      group: publish
      cancel-in-progress: false
    env:
      VERSION: ${{ needs.detect.outputs.version }}
    steps:
      - uses: actions/checkout@v4

      # Keep this exact nightly aligned with flake.nix.
      - name: Install Rust (nightly-2026-10-07)
        uses: dtolnay/rust-toolchain@master
        with:
          toolchain: nightly-2026-10-07

      - name: Publish crate
        env:
          CARGO_REGISTRY_TOKEN: ${{ secrets.CARGO_REGISTRY_TOKEN }}
        run: |
          # crates.io asks API clients to name themselves.
          if curl --silent --fail --output /dev/null \
              --user-agent "bbtree publish workflow (github.com/$GITHUB_REPOSITORY)" \
              "https://crates.io/api/v1/crates/bbtree/$VERSION"; then
            echo "crates.io already has bbtree $VERSION"
          else
            cargo publish --locked
          fi

      - name: Create GitHub Release
        env:
          GH_TOKEN: ${{ github.token }}
        run: |
          if gh release view "v$VERSION" > /dev/null 2>&1; then
            echo "v$VERSION is already released on GitHub"
          else
            gh release create "v$VERSION" --target "$GITHUB_SHA" \
              --title "Release v$VERSION" --generate-notes
          fi

      # The release was fuzzed before it merged, in ci.yml, whose runs the
      # README's fuzzing badge doesn't count: a run of fuzz.yml on main, now
      # the release, shows it there.
      - name: Fuzz the release on main
        env:
          GH_TOKEN: ${{ github.token }}
        run: |
          started=$(gh run list --repo "$GITHUB_REPOSITORY" --workflow fuzz.yml \
            --commit "$GITHUB_SHA" --json databaseId --jq length)
          if [ "$started" -gt 0 ]; then
            echo "fuzz.yml already runs on $GITHUB_SHA"
          else
            gh workflow run fuzz.yml --repo "$GITHUB_REPOSITORY" --ref main
          fi