-
Notifications
You must be signed in to change notification settings - Fork 0
263 lines (239 loc) · 10.3 KB
/
Copy pathrelease.yml
File metadata and controls
263 lines (239 loc) · 10.3 KB
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
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
name: Release
# Release variant: serialize per-tag, never cancel. A cancelled release
# mid-publish leaves the GitHub Release page, build attestations, and
# per-target binary archives in an inconsistent state — better to queue
# than abort. Mirrors the pulseengine/rivet and pulseengine/witness
# release workflows.
concurrency:
group: release-${{ github.ref }}
cancel-in-progress: false
on:
push:
tags:
- "v*"
# Manual re-run for a tag whose initial run failed partway. The tag
# must already exist; this does not create tags.
workflow_dispatch:
inputs:
tag:
description: "Existing release tag to (re)build (e.g. v0.3.1)"
required: true
type: string
permissions:
contents: read
env:
CARGO_TERM_COLOR: always
jobs:
# ── Cross-platform binary builds ──────────────────────────────────────
# synth-cli builds with `--features riscv` only (the workspace default).
# The `verify` feature is intentionally NOT enabled here. Historically it
# pulled z3-sys (vendored C++ Z3 build — slow, network-hungry); since #553
# it is pure Rust (ordeal engine), so enabling it is now feasible but is a
# deliberate follow-up decision, not a build constraint. The CLI degrades
# gracefully without it (`synth verify` fails loudly with "rebuild with
# --features verify").
build-binaries:
name: Build ${{ matrix.target }}
runs-on: ${{ matrix.os }}
strategy:
fail-fast: false
matrix:
include:
- target: x86_64-unknown-linux-gnu
os: ubuntu-latest
archive: tar.gz
- target: aarch64-unknown-linux-gnu
os: ubuntu-latest
archive: tar.gz
cross: true
# x86_64-apple-darwin cross-compiles on the arm64 macos-14
# runner — matches pulseengine/rivet and pulseengine/witness
# (both Rust-workspace CLIs, the closest analogs to synth).
- target: x86_64-apple-darwin
os: macos-14
archive: tar.gz
- target: aarch64-apple-darwin
os: macos-latest
archive: tar.gz
steps:
- uses: actions/checkout@v7
with:
ref: ${{ inputs.tag || github.ref }}
- uses: dtolnay/rust-toolchain@stable
with:
targets: ${{ matrix.target }}
- uses: Swatinem/rust-cache@v2
with:
key: release-${{ matrix.target }}
- name: Install cross
if: matrix.cross
run: cargo install cross --git https://github.com/cross-rs/cross --locked
- name: Build synth (native)
if: ${{ !matrix.cross }}
run: cargo build --release --target ${{ matrix.target }} -p synth-cli
- name: Build synth (cross)
if: matrix.cross
run: cross build --release --target ${{ matrix.target }} -p synth-cli
- name: Strip binary
if: ${{ !matrix.cross }}
run: strip "target/${{ matrix.target }}/release/synth" 2>/dev/null || true
- name: Package archive
env:
TARGET: ${{ matrix.target }}
# Resolve the version once: tag push -> refs/tags/vX.Y.Z;
# workflow_dispatch -> the user-supplied tag input. Bound via
# env: and dereferenced as $VERSION below — never expand
# ${{ ... }} directly inside run: (command-injection vector).
INPUT_TAG: ${{ inputs.tag }}
run: |
set -euo pipefail
VERSION="${INPUT_TAG:-${GITHUB_REF#refs/tags/}}"
ARCHIVE="synth-${VERSION}-${TARGET}.tar.gz"
mkdir -p staging
cp "target/${TARGET}/release/synth" staging/
cp README.md LICENSE staging/ 2>/dev/null || true
tar -czf "$ARCHIVE" -C staging .
echo "ARCHIVE=$ARCHIVE" >> "$GITHUB_ENV"
- uses: actions/upload-artifact@v7
with:
name: binary-${{ matrix.target }}
path: ${{ env.ARCHIVE }}
retention-days: 7
# ── Create the GitHub Release: checksums, provenance, signing ─────────
create-release:
name: Create GitHub Release
needs: [build-binaries]
runs-on: ubuntu-latest
permissions:
# Keyless signing + provenance need an OIDC token; release-asset
# upload needs contents: write; build provenance attestation
# needs attestations: write. This block mirrors the permissions
# set used by the pulseengine/sigil release workflow.
contents: write
id-token: write
attestations: write
steps:
- uses: actions/checkout@v7
with:
ref: ${{ inputs.tag || github.ref }}
- name: Download all build artifacts
uses: actions/download-artifact@v8
with:
path: artifacts
- name: Flatten release assets
run: |
set -euo pipefail
mkdir -p release-assets
find artifacts -type f -name "*.tar.gz" -exec cp {} release-assets/ \;
ls -la release-assets/
# Phase 6: CycloneDX SBOM for the synth toolchain itself. The
# SBOM is generated *before* SHA256SUMS so its digest is captured
# in the checksum manifest; the existing cosign signature over
# SHA256SUMS.txt transitively covers the SBOM. See docs/sbom.md
# for the distinction between this and `synth compile --sbom`.
- name: Install cargo-cyclonedx
run: cargo install --locked cargo-cyclonedx
- name: Generate toolchain SBOM (CycloneDX)
env:
INPUT_TAG: ${{ inputs.tag }}
run: |
set -euo pipefail
VERSION="${INPUT_TAG:-${GITHUB_REF#refs/tags/}}"
BARE="${VERSION#v}"
# cargo-cyclonedx doesn't proxy cargo's `-p` package-selection flag
# (caught the hard way on the first v0.6.0 release attempt). Use
# `--manifest-path` to target synth-cli's Cargo.toml directly; the
# generated SBOM lands next to that Cargo.toml.
cargo cyclonedx \
--manifest-path crates/synth-cli/Cargo.toml \
--format json \
--spec-version 1.5
SBOM_SRC="crates/synth-cli/synth-cli.cdx.json"
if [ ! -f "$SBOM_SRC" ]; then
SBOM_SRC=$(find crates/synth-cli -maxdepth 2 -name '*.cdx.json' | head -1)
fi
test -n "$SBOM_SRC" && test -f "$SBOM_SRC"
cp "$SBOM_SRC" "release-assets/synth-${BARE}.cdx.json"
echo "::notice::Toolchain SBOM written to release-assets/synth-${BARE}.cdx.json"
ls -la release-assets/
- name: Generate SHA256 checksums
run: |
set -euo pipefail
cd release-assets
sha256sum ./* > SHA256SUMS.txt
cat SHA256SUMS.txt
# ── SLSA build provenance (GitHub-native) ──────────────────────────
# actions/attest-build-provenance generates an in-toto SLSA v1
# provenance statement for every binary archive, signs it keyless
# via Sigstore (Fulcio cert bound to this workflow's OIDC identity),
# and records it in the Rekor transparency log. Consumers verify
# with `gh attestation verify <file> --repo pulseengine/synth`.
# GitHub-native attestation (not the standalone SLSA generator)
# keeps the workflow self-contained — see docs/release-process.md.
- name: Generate SLSA build provenance
uses: actions/attest-build-provenance@v4
with:
subject-path: "release-assets/*.tar.gz"
# ── Sigstore keyless signing (cosign) ──────────────────────────────
# Signs SHA256SUMS.txt so a consumer can verify the checksum file
# itself was produced by this workflow (closes the gap where an
# attacker who can replace a release asset could also replace the
# plain checksum file). Mirrors the pulseengine/witness and
# pulseengine/rivet cosign sign-blob pattern. The .cosign.bundle is
# the verifier-friendly artifact; .sig + .pem are the detached
# signature and Fulcio certificate. Verify with:
# cosign verify-blob \
# --certificate-identity-regexp \
# 'https://github.com/pulseengine/synth/.github/workflows/release.yml@.*' \
# --certificate-oidc-issuer \
# 'https://token.actions.githubusercontent.com' \
# --bundle SHA256SUMS.txt.cosign.bundle \
# SHA256SUMS.txt
- name: Install cosign
uses: sigstore/cosign-installer@v3
with:
cosign-release: 'v2.4.1'
- name: Sign SHA256SUMS with cosign (keyless OIDC)
run: |
set -euo pipefail
cd release-assets
cosign sign-blob \
--yes \
--bundle SHA256SUMS.txt.cosign.bundle \
--output-signature SHA256SUMS.txt.sig \
--output-certificate SHA256SUMS.txt.pem \
SHA256SUMS.txt
echo "::notice::SHA256SUMS signed via Sigstore keyless flow."
ls -la ./*
- name: Capture build environment
run: |
set -euo pipefail
{
echo "rustc: $(rustc --version)"
echo "cargo: $(cargo --version)"
echo "cosign: $(cosign version 2>&1 | head -1)"
echo "runner: $(uname -srm)"
} > release-assets/build-env.txt
cat release-assets/build-env.txt
- name: Create or update GitHub Release
env:
GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
# Untrusted-input safety: the tag name flows in via env: and is
# dereferenced through $VERSION, never expanded into the shell.
INPUT_TAG: ${{ inputs.tag }}
run: |
set -euo pipefail
VERSION="${INPUT_TAG:-${GITHUB_REF#refs/tags/}}"
# Idempotent: re-running the workflow for an existing release
# uploads/overwrites assets rather than failing. --clobber lets
# a re-run replace assets a previous partial run left behind.
if gh release view "$VERSION" >/dev/null 2>&1; then
echo "::notice::Release $VERSION exists; uploading assets"
gh release upload "$VERSION" --clobber release-assets/*
else
echo "::notice::Creating Release $VERSION with assets"
gh release create "$VERSION" \
--title "synth $VERSION" \
--generate-notes \
release-assets/*
fi