CI and releases
bbtex supports Apple Silicon Macs. Checks run locally on an Apple Silicon Mac with scripts/ci.sh; the GitHub Actions workflows are kept but run only when started by hand (Actions → workflow → Run workflow), because Actions minutes are limited on this private repository.
Local CI
scripts/ci.sh # check HEAD
scripts/ci.sh --report # ... and post the result on GitHub
scripts/ci.sh --engines REF # also compile the corpus with real TeX enginesThe script checks out the commit into a temporary git worktree, so uncommitted changes in your working folder never affect the result, then runs:
dune buildanddune runtest(unit and cram tests).- Integration checks that need no editor session: project builds, preview cancellation, the snippet page, and draft-release gating.
- shellcheck and
bash -non every script,perl -con the preview lock, andgit diff --checkon the commit's changes relative tomain. - The release package:
test/integration/check_preview_release.sh, an arm64 architecture check, and a check that the binary links only system libraries. The package ZIP, its SHA-256 checksum and build information (commit, macOS, OCaml, dune and uv versions) are written todist/release/. The ZIP carries no extended attributes except the stationery templates' Finder flags, so its__MACOSXfolder holds only those seven files; Dropbox and macOS provenance tags on the build tree are left out. Staged installation checks also cover renamed package discovery, nested command conflicts, attachment receipts, protected upgrades and removal without touching the real BBEdit support folder. - With
--engines: the article/book/Beamer corpus with pdfLaTeX, XeLaTeX and LuaLaTeX, including BibTeX/Biber and Poppler. With--tectonic: the Tectonic tier with the same pinned bundle as the GitHub workflow. That bundle's biblatex needs Biber 2.17 (MacTeX's newer Biber refuses its files), so the script downloads Biber 2.17 once, checks its SHA-256, and caches it in~/Library/Caches/bbtex/biber-2.17/; see real-engine coverage.
--report posts the commit status local-ci/macos-arm64 (or local-ci/macos-arm64+engines) through gh, so pull requests show the local result. Statuses use no Actions minutes. The output of every step goes to a log next to the temporary checkout; a failing run keeps both for inspection (--keep keeps them after a pass too). The script notes when the local OCaml differs from the version CI pins (OCAML_COMPILER in .github/workflows/ci.yml).
Skim, save attachments, and native focus/selection checks remain separate local integration tests (BBTEX_TEST_NATIVE=1). Packages are built and tested on the macOS version of the Mac running the checks; older versions are unverified.
Prepare a release
Update release notes, complete the native checks, and merge the intended changes into
main.Set the version in
lib/version.ml(the binary and the docs site read it there; the cram test checksbbtex --version), the README version badge, the heading indocs/changelog.mdand the first line of the release notes. Merge that, then create and push an annotated tag:shgit tag -a v0.1.0 -m 'bbtex v0.1.0' git push origin v0.1.0Run
scripts/ci.sh --engines --report --release v0.1.0 v0.1.0. After every check passes, it creates or updates a draft GitHub release with the arm64 package ZIP, checksum and build information. It refuses to change a release that is already published. Publishing the draft is manual.Publish the docs from the released
main:scripts/docs-site.sh deploy(GitHub Pages serves thegh-pagesbranch at louloulibs.github.io/bbtex).Mirror the release and its docs to the UMN copy:
scripts/mirror-release.sh v0.1.0. Only the tag,mainat the tagged commit and the tag's docs are pushed there.