timberfs 0.8.1

Experimental append-only, transparently compressed, write-time-indexed filesystem for log files
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
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118

name: Release

# Tag-driven releases: push a tag `vX.Y.Z` (matching the Cargo.toml
# version) and this builds the .deb, re-runs the full VM package suite
# against that exact artifact, attests its build provenance, creates the
# GitHub release with generated notes, and publishes to crates.io.
#
# crates.io publishing uses Trusted Publishing (OIDC) — no stored secret.
# One-time setup on crates.io: the timberfs crate -> Settings -> Trusted
# Publishing -> GitHub, repository torstei/timberfs, workflow release.yml.
# Until that's configured, the publish step skips with a note.
#
# The .deb is attached twice: with its versioned name, and as the stable
# `timberfs_amd64.deb` so
#   curl -LO https://github.com/torstei/timberfs/releases/latest/download/timberfs_amd64.deb
# always fetches the newest release. Verify a download with:
#   gh attestation verify timberfs_amd64.deb --repo torstei/timberfs

on:
  push:
    tags: ["v*"]

permissions:
  contents: write
  id-token: write
  attestations: write

env:
  CARGO_TERM_COLOR: always

jobs:
  release:
    runs-on: ubuntu-latest
    timeout-minutes: 30
    steps:
      - uses: actions/checkout@v4

      - name: Check that the tag matches the Cargo.toml version
        run: |
          TAG="${GITHUB_REF_NAME#v}"
          VER=$(grep -m1 '^version' Cargo.toml | cut -d'"' -f2)
          if [ "$TAG" != "$VER" ]; then
            echo "tag ${GITHUB_REF_NAME} does not match Cargo.toml version ${VER}" >&2
            exit 1
          fi

      - name: Enable KVM for the runner user
        run: |
          echo 'KERNEL=="kvm", GROUP="kvm", MODE="0666", OPTIONS+="static_node=kvm"' \
            | sudo tee /etc/udev/rules.d/99-kvm4all.rules
          sudo udevadm control --reload-rules
          sudo udevadm trigger --name-match=kvm

      - name: Install QEMU and ISO tooling
        run: |
          sudo apt-get update -qq
          sudo apt-get install -y -qq qemu-system-x86 qemu-utils genisoimage

      - uses: dtolnay/rust-toolchain@stable
      - uses: Swatinem/rust-cache@v2

      - name: Cache Debian cloud base image
        uses: actions/cache@v4
        with:
          path: ~/.cache/timberfs-vm-tests
          key: debian-13-genericcloud-amd64

      - uses: taiki-e/install-action@v2
        with:
          tool: cargo-deb

      - name: Build the .deb
        run: cargo deb

      - name: Test the exact release artifact in a VM
        run: tests/vm/run-vm-test.sh

      # Assets are staged OUTSIDE the checkout: cargo publish refuses to
      # run from a dirty working tree, and rightly so.
      - name: Stage release assets
        run: |
          mkdir -p "$RUNNER_TEMP/dist"
          cp target/debian/timberfs_*_amd64.deb "$RUNNER_TEMP/dist/"
          cp target/debian/timberfs_*_amd64.deb "$RUNNER_TEMP/dist/timberfs_amd64.deb"

      - name: Attest build provenance
        uses: actions/attest-build-provenance@v2
        with:
          subject-path: ${{ runner.temp }}/dist/*

      - name: Create the GitHub release
        env:
          GH_TOKEN: ${{ github.token }}
        run: gh release create "$GITHUB_REF_NAME" "$RUNNER_TEMP"/dist/* --generate-notes --verify-tag

      - name: Get a crates.io token via Trusted Publishing (OIDC)
        id: crates_auth
        continue-on-error: true
        uses: rust-lang/crates-io-auth-action@v1

      - name: Publish to crates.io (skipped when Trusted Publishing is not configured)
        if: steps.crates_auth.outcome == 'success'
        env:
          CARGO_REGISTRY_TOKEN: ${{ steps.crates_auth.outputs.token }}
        run: cargo publish

  # Rebuild and redeploy the apt repository on GitHub Pages with the new
  # release included. (A separate `on: release` workflow would never fire:
  # events created with the workflow's own GITHUB_TOKEN don't trigger
  # other workflows.)
  apt-repo:
    needs: release
    uses: ./.github/workflows/apt-repo.yml
    permissions:
      contents: read
      pages: write
      id-token: write
    secrets: inherit