Commit Graph
56 Commits
Author SHA1 Message Date
FredApps 773e67febf #4728: pass web-craft-fonts to the release workflow
The web release must check out craft-fonts so the on-demand CJK faces are packaged. VectorCraft, WordCraft and LightCraft already pass this input.
2026-11-15 12:02:27 +01:00
FredApps 9131b8aba5 Merge branch 'main' into gpu-software-adapter 2026-11-13 20:43:05 +01:00
FredApps 4d82e518c5 CI: use the shared git-sources check (#4686)
nix.yml ran its own copy of the git-sources job; it now calls
craft-common-actions git-sources.yml.
2026-11-13 14:04:54 +01:00
FredAppsandFredApps a1f5697c90 ci: provision fonts for coverage tests (#4751)
Co-authored-by: FredApps <FredApps@users.noreply.github.com>
2026-11-13 08:13:04 +01:00
cb9783ba1a CI (Windows): clippy and tests of the crates with Windows-only code (#4649)
* CI (Windows): clippy and tests of the crates with Windows-only code

A Windows leg through the shared gate and changed-paths workflows, as
LightCraft has: pull requests and pushes to main that touch the Windows
code (WASAPI audio, the graphics test start, Media Foundation / D3D11
decoding, their manifests and the lockfile), and pull requests labelled
full-ci. Nothing ran these crates' tests on Windows before.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* test(filmcraft): accept a reset when the control server drops an expired connection

The first Windows run of the new CI leg failed unterminated_request_releases_its_slot:
Windows ended the timed-out connection with a reset (os error 10054), not a close, so
read_to_string returned ConnectionReset. Either way the client got no reply. Bytes read
before a reset stay in the string, so the no-stale-reply check still applies.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* test(ui-egui): let the drag-while-playing test wait for frames on a busy runner

The Windows leg (#4649) failed program_monitor_plays_on_while_a_value_is_dragged once: in 90
passes (~1.5 s) the workers finished no frame at a newer revision, so only frame 23 showed. It
passed in the run before. The test now drags until five frames have shown, for up to ~10 s, so a
picture held for the whole drag (the #1673 bug) still fails.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* ci(windows): run the Windows leg's tests under nextest

`cargo test` runs all of a binary's tests in one process, so they share
rayon's global pool and one test's work waits behind another's. The UI
binary's drag-while-playing test failed on one of two attempts at the same
commit (run 43007266199). On a Windows 11 sandbox it passed in six runs:
alone, with the whole binary, pinned to 1, 2 or 4 cores, and with a
one-thread rayon pool. The last run did fail another timing-bound test
(proxy creation, no proxies after ~8 s), which shows how tests in one
process hold each other up.

The Linux gate (`cargo xtask ci`) already uses nextest: each test in its
own process, with .config/nextest.toml's groups. The gate installs
cargo-nextest 0.9.150 on every OS, and the targets are the same
(--lib --bins --tests; no doctests on either leg's test step).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* ci(windows): fix main's first Windows-only clippy error; drop the moved h264 crate

The Windows leg's first run against current main stopped at
crates/engine/src/lib.rs: `let mut dir = DirBuilder::new()` (#4264) is
only mutated on Unix, where it sets the folder's mode, so on Windows
`-D warnings` turns the unused `mut` into an error. The builder is now
made per platform. Nothing compiled Windows code on main until this leg.

crates/h264 moved to craft-libs (504fe9fc5), so `-p filmcraft-h264` no
longer matches a package and `crates/h264/*` no longer exists: both are
removed from the leg.

On a Windows 11 sandbox at main merged into this branch (c7ef3f96) with
this change: `cargo fmt --all --check` passes, the leg's clippy command
for its six packages passes, and filmcraft-engine's lib tests pass (907).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* test(nextest): run the real-time play_ahead tests with nothing beside them

On the Windows leg, two play_ahead tests failed with silence where
frames were due: plays_every_frame_in_order_from_the_start at frame
27648, and a_device_with_other_channels_plays_the_channels_both_have at
frame 1024, two callbacks in, after a 30 ms head start in which the
mixer should have filled its 200 ms lead at once. The mixer thread only
sleeps when its ring is full, so it wasn't scheduled: nextest runs a
test process per core, and these tests need a thread on time against a
wall-clock device. They get the same rule as render's mixer_perf. The
other 2531 tests passed, the drag-while-playing test among them
(run 43270273462).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: FredApps <FredApps@users.noreply.github.com>
2026-11-12 20:30:24 +01:00
FredApps e42e2c91a2 CI: nightly release dry run (#4684)
release.yml also runs nightly on main with craft-common-actions' dry-run: every release build
except macOS, with nothing signed, pushed or drafted. Breakage that only the release build hits
(riscv64, Flatpak, FreeBSD, packaging) then shows up the next morning instead of on release
day, as it did on 11 Nov 2026.
2026-11-11 23:04:13 +01:00
Dylan M. Taylor c3d98bce15 ci: run Harden-Runner on every job (#4672)
Adds step-security/harden-runner (audit, pinned to v2.22.4 like
craft-common-actions) as the first step of each job that did not have it,
so every workflow in the org's public repos reports its egress to
StepSecurity. Audit, not block: block-mode allow lists come from each
job's observed traffic.
2026-11-11 12:11:36 -05:00
Luis 4a56be9cff Release: refresh contributor credits for each release (#4415) (#4416)
About > Contributors still showed an old snapshot, because nothing
regenerated contributors/contributors.json before a release. Opt in to
the shared refresh from craft-common-actions: a read-only credits job
regenerates the snapshot for the release commit, and the shared release
workflow installs it before every source build. The snapshot is not
committed back.
2026-11-08 01:53:25 +01:00
FredApps 17a5a6c279 Copy the shared house rules into AGENTS.md.
The blocks come from craft-contrib at dde09ea31e2e457f5b4653a6e76f7cdf55944bdf. CLAUDE.md imports AGENTS.md. The house-rules workflow checks the copy.
2026-11-06 11:50:01 +01:00
Dylan M. Taylor 2508f5420e Pass the Linux signing key to the release workflow (#4303) 2026-11-04 17:45:08 -05:00
Dylan M. Taylor 9c6d66114c ci: grant packages write permission to release workflow 2026-10-31 23:42:59 -04:00
FredApps a864e83e83 Merge shared CI and fail GPU tests when required setup fails 2026-10-30 12:20:39 +01:00
Dylan M. Taylor 0f87f0018e CI: workflows only call craft-common-actions at @main (#3645)
AGENTS.md (and CLAUDE.md where present) gets a CI workflows section: workflows only call
craft-common-actions at @main, with no other jobs; feature and fix PRs don't touch CI and
link or open a craft-common-actions issue (a PR only for a small fix that is safe for
every app and does not increase CI time); legacy jobs
aren't added to and move only as their own task, staying until a shared workflow runs them.

windows-arm64.yml moves from its SHA pin to @main. The pinned revision is on
craft-common-actions main and the workflow (and the actions it calls) is identical
there, so nothing changes in behaviour.
2026-10-29 22:17:20 -04:00
aiongg a9bd7705d8 ci: use storytold/craft-common-actions at the merged installer-policy commit 2026-10-27 20:51:47 +00:00
Jeremy 8ba3f9174b fix(installer): harden install-policy checks and packaging-lint workflow 2026-10-27 12:01:21 +00:00
Jeremy 058050f32a fix(installer): address scope and ARM64 review feedback 2026-10-27 12:01:21 +00:00
Jeremy 9efa1e8755 feat(installer): default to a per-user ArtCraft folder 2026-10-27 12:01:21 +00:00
skylar taylor-barrickandDylan M. Taylor 320cae243d Migrate FilmCraft to egui 0.37 with current editing changes preserved (#3249)
* egui 0.37: migrate FilmCraft input and rendering integration

* egui-037: fix capture failures, UTF-8 input and hidden timing

* Fix screenshot crop scale for fitted native surfaces

* egui037: simplify UI helpers and preserve pointer IME cancellation

* Translate graphics and effect control accessibility labels

* egui037: Document capture and IME lifecycle contracts

* egui-037: document UI and input integration contracts

---------

Co-authored-by: Dylan M. Taylor <dylan@dylanmtaylor.com>
2026-10-25 14:45:04 -04:00
channelramble 3a5f217b34 docs: add structured issue intake and security reporting guidance (#2054) 2026-10-25 12:32:06 -04:00
Dylan M. Taylor e45ff58346 ci(sonar): don't cancel superseded runs on main, so coverage is published (#3026) 2026-10-23 17:00:18 -04:00
Dylan M. Taylor 20f02b9aa1 release: the git-sources gate moves into craft-common-actions (storytold/craft-common-actions#78) (#3014)
The check is shared at release.yml@main now; keep only the reusable call.
2026-10-23 14:41:15 -04:00
aiongg f46a1a8436 CI: run the gate through craft-common-actions' shared gate.yml; FreeBSD nightly and on release (#2937)
ci.yml calls the shared workflow (cached apt packages, nextest, main-only cache saves, Cargo.lock check). FreeBSD and Windows ARM64 run nightly and on pushes to release instead of on pull requests. Depends on storytold/craft-common-actions#69.
2026-10-23 14:21:15 -04:00
aiongg fbeccbe9bc Fonts: pin craft-fonts bfcbf71; CRAFT_FONTS_REQUIRED fails without CRAFT_FONTS_DIR (#2646)
* Fonts: pin craft-fonts bfcbf71; CRAFT_FONTS_REQUIRED fails without CRAFT_FONTS_DIR

craft-fonts main adds Noto Sans CJK SC, Noto Sans Arabic, Noto Sans Thai and
Noto Sans Georgian. FilmCraft registers every CRAFT_FONTS entry, so releases
pick them up with the pin bump. ATTRIBUTION.md and NOTICE list them.

With CRAFT_FONTS_REQUIRED set, crates/text/build.rs errors when
CRAFT_FONTS_DIR is unset or empty, not only when it is not a checkout.

Refs storytold/craft-libs#197

* Fonts: only CRAFT_FONTS_REQUIRED=1 enables required mode

* text: the CRAFT_FONTS_REQUIRED message says unset or empty
2026-10-23 13:38:11 -04:00
aiongg 4743cfb939 fix(engine): resolve stored media paths with craft-docpath's resolve_absolute (#2609)
* fix(engine): use resolve_absolute for stored media paths

* fix(engine): give the reason when a scratch disk folder is refused

* CI: check that git dependencies come from storytold

* CI: release only with git dependencies from storytold

* doc_path: a foreign drive path without a document is refused, not document-relative

* Workflows: one Git-source check: lockfile present and current, no source replacement, storytold hosts only

* Workflows: the Git-source check reads the legacy .cargo/config too

* Workflows: the Git-source check parses cargo config with tomllib
2026-10-23 13:37:55 -04:00
aiongg 0a881266c8 CI: xtask ci in the dev profile, one test binary per crate, nextest (#2860)
* Tests: one integration-test binary per crate

Each crate with several tests/*.rs files keeps them as modules of tests/it/,
so cargo links one test executable per crate instead of one per file. Files
that change process-wide state or time a workload stay binaries of their own.

* Profiles: line tables for workspace crates, no debug info for dependencies

* Windows ARM64: nightly and on release pushes instead of every push to main

* xtask ci: clippy and tests in the dev profile

The release profile's thin LTO and single codegen unit made linking the test
binaries take most of the gate. The codec and audio crates stay at opt-level 3
in the dev profile, so their tests run at release speed.

* xtask ci: nextest, doctests, no examples, one wasm check

Tests run with cargo nextest when it is installed (cargo test otherwise) and
build with --lib --bins --tests, so examples aren't linked; doctests run
separately. The wasm check keeps going past the first failing crate. VP8
fixture generation locks across processes, since nextest runs each test in
its own.

* VP9 synthetic fixtures: write aside and rename

A test in another process could read a fixture ffmpeg was still writing.

* Fuzz tests: a third of each sweep by default, all of it with FILMCRAFT_FUZZ_ITERS

Every seed, mutation kind and thread count still runs. Header bytes each get
one overwrite value and two bit flips in rotation, so every value and bit
index still occurs across the region. FILMCRAFT_FUZZ_ITERS=N runs the whole
sweep plus N random rounds per seed, as before.

* Platform fallback tests: one failure point per hybrid path

The failure-anywhere test injected a failure at four points around every
restart point; the hybrid's paths differ only in the first GOP, around the
second and last restart points, at the end and never. The replay test needs
the first two GOPs.

* Export tests: shorter ranges with the same checks

The bitrate test measures 0.5–1.5 s, where each preset reaches its own
target (on 0–3 s the simple demo left two presets at the same rate). The
every-preset test exports three frames per preset.

* Audio tests: effects in parallel, a table-driven FFT for the Opus quality metric

The extreme-settings test keeps both settings and the 40 s tail for every
effect, one thread each. The Opus quality metric's FFT builds its twiddles
once and allocates nothing per transform (same algorithm and summation order).

* CI: dev-profile gate with nextest

xtask ci no longer builds with --release, so the release-profile overrides
go; nextest is installed for the test step.

* CI: apt packages through the cached install-apt-packages action

* Review fixes: fuzz tests with a panic hook in their own binaries, loud fixture lock

The fuzz tests of av1, h264, hevc, mpeg2v, vp8 and vp9 count panics through
a process-wide hook, so a panic in another test of the same process would
fail them; they are binaries of their own again. The VP8 fixture lock fails
the test instead of skipping it silently, and the full-sweep doc comments say
how many truncation points the full run samples.

* Fuzz tests: rotate the default subset per run (FILMCRAFT_FUZZ_SEED replays one)

* platform tests: decode-switch tests in their own binaries, one NVENC lock
2026-10-23 13:34:16 -04:00
dependabot[bot] b12336cf73 ci(deps): bump Swatinem/rust-cache (#2971)
Bumps the actions group with 1 update: [Swatinem/rust-cache](https://github.com/swatinem/rust-cache).


Updates `Swatinem/rust-cache` from 2.9.2 to 2.9.3
- [Release notes](https://github.com/swatinem/rust-cache/releases)
- [Changelog](https://github.com/Swatinem/rust-cache/blob/master/CHANGELOG.md)
- [Commits](https://github.com/swatinem/rust-cache/compare/6323deb102c322ba6fcbdcafc7e3dddab59af2b6...d1527c8f67ef9af357290475d4af4b0fab8f12e0)

---
updated-dependencies:
- dependency-name: Swatinem/rust-cache
  dependency-version: 2.9.3
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: actions
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2026-10-23 10:53:33 -04:00
skylar taylor-barrick f47a1f6480 CI: run cargo xtask ci on pull requests and pushes to main (#2563)
CI: run cargo xtask ci on pull requests and pushes to main
2026-10-22 18:47:06 -06:00
Dylan M. Taylor 78ceb6e3c7 ci: add SonarCloud scan via shared reusable workflow
Calls storytold/craft-common-actions/.github/workflows/sonarcloud.yml@main
with secrets: inherit. Adds SonarCloud badge to README where missing and
removes the redundant sonar-project.properties (config now passed by the
reusable workflow).
2026-10-21 15:46:58 -04:00
Dylan M. Taylor d643a88665 Merge pull request #2157 from dylanmtaylor/ci/shared-nix-workflow
ci: switch to shared nix workflow from craft-common-actions
2026-10-21 02:38:55 -04:00
FredAppsandClaude Opus 5.5 0d4a48a756 CI: run the GPU tests on lavapipe and fail when they skip
The hosted runner has no GPU, but wgpu offers a software adapter when
there is none and the workflow already installs Mesa's lavapipe, so
the GPU-vs-CPU parity tests can run there. Their skip note goes to
stderr, which cargo test hides for passing tests, so a skip looked the
same as a pass.

- ci.yml: after the gate, run filmcraft-gpu and filmcraft-golden with
  --nocapture; fail on `no GPU adapter` / `SKIPPED (gpu ...)` or when
  no test printed its adapter. Install libvulkan1 explicitly.
- The GPU test device helpers print the adapter they use; the gpu
  crate's tests.rs reuses blend_tests::device instead of a copy.
- docs/testing.md: GPU tests run on a software adapter; what CI checks.

Follows lightcraft#1148. filmcraft needs no opt-in variable: nothing
in the test path refuses a software adapter.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-20 13:03:43 +02:00
FredAppsandClaude Opus 5.5 4c22bb010d CI: build the release test binaries without LTO, allow 120 minutes
xtask ci runs clippy and the tests with --release. With the shipped
release profile (thin LTO, codegen-units = 1) linking the test binaries
alone ran past 70 minutes on a standard runner. CI keeps opt-level but
turns LTO off and uses 16 codegen units.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-20 13:01:58 +02:00
FredAppsandClaude Opus 5.5 619b3609ec CI: run cargo xtask ci on pull requests and pushes to main
Only path-filtered workflows run on pull requests today, so most PRs land
without a test run. Port of the wordcraft#800 workflow: Linux, standard
GitHub-hosted runner, read-only token, no secrets, craft-fonts pinned to
the release.yml commit.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-20 13:01:58 +02:00
FredAppsandClaude Opus 5.5 28fcadddd2 CI: build the release test binaries without LTO, allow 120 minutes
xtask ci runs clippy and the tests with --release. With the shipped
release profile (thin LTO, codegen-units = 1) linking the test binaries
alone ran past 70 minutes on a standard runner. CI keeps opt-level but
turns LTO off and uses 16 codegen units.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-20 12:17:27 +02:00
FredAppsandClaude Opus 5.5 b787c150e7 CI: run cargo xtask ci on pull requests and pushes to main
Only path-filtered workflows run on pull requests today, so most PRs land
without a test run. Port of the wordcraft#800 workflow: Linux, standard
GitHub-hosted runner, read-only token, no secrets, craft-fonts pinned to
the release.yml commit.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-20 10:57:34 +02:00
Dylan M. Taylor 6c3948a36c ci: configure Dependabot for Cargo and GitHub Actions
Co-authored-by: Dylan M. Taylor <dylan@dylanmtaylor.com>
2026-10-18 12:31:32 -06:00
Dylan M. Taylor 09aaf9bf15 ci: standardize FreeBSD workflow on shared FreeBSD 15.1 action (#2158) 2026-10-16 10:08:51 -06:00
Dylan M. Taylor 756cfdd89d ci: switch to shared nix workflow from craft-common-actions 2026-10-15 23:57:12 -04:00
Dylan M. Taylor df97b85f59 ci: delegate FreeBSD workflow to craft-common-actions and add nix check 2026-10-15 20:45:39 -04:00
Brandon ThomasandClaude Opus 5.5 84518da96f Release workflow: pass the Azure signing secrets so Windows builds are signed (#1169)
Since the release workflow moved to storytold/craft-common-actions, it has
passed only the Apple and WINDOWS_CERTIFICATE secrets. The signing job reads
values from the release environment, but only for names the caller lists, so
the AZURE_* names that Trusted Signing uses came through empty and Windows
builds would ship unsigned. Same fix as storytold/craft-launcher#174.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-12 11:08:21 -04:00
Dylan M. Taylor 0800a8b0aa ci: refactor workflows to use storytold/craft-common-actions (#1051)
* ci: refactor workflows to use reusable artcraft-common-actions

* ci: point reusable workflows to storytold/craft-common-actions

* ci: pin storytold/craft-common-actions to commit 27a978f and pass secrets explicitly

* ci: use @main (unpinned) for craft-common-actions with explanation comment
2026-10-11 11:52:44 -04:00
Brandon ThomasandClaude Opus 5.5 2ff3f5e266 Release prep: 0.6.0 and a Linux riscv64 release build (#830)
- release.yml: new `linux-riscv64` job, cross-compiled on ubuntu-24.04 against
  ports.ubuntu.com riscv64 libs (ported from GridCraft), tar.gz only, CLI
  smoke-tested under QEMU. Installs libasound2-dev:riscv64 for cpal/ALSA; the
  VA-API and NVDEC/NVENC paths are loaded with libloading at run time, so they
  need no riscv64 libraries. The draft-release job now needs it, so its tarball
  is uploaded and covered by SHA256SUMS.txt.
- packaging/linux/package.sh: CROSS_ARCH / CROSS_TARGET / CROSS_COMPILE /
  EMULATOR support, as in GridCraft.
- README and docs/releasing.md list the riscv64 tarball.
- cargo xtask version set 0.6.0 (Cargo.toml, Cargo.lock); refresh contributors.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-10 19:28:41 -04:00
Brandon Thomas 701c433a96 Merge pull request #501 from dylanmtaylor/chore/update-actions
chore: bump github actions to fix Node 20 deprecation warnings
2026-10-10 05:03:26 -04:00
Dylan M. Taylor 75559a8f41 chore: bump github actions to fix Node 20 deprecation warnings 2026-10-09 20:08:27 -04:00
txiki739andClaude Opus 5.5 17921200d7 #346: the from-source Flatpak includes the CLI and MCP server
The release bundle manifest installs filmcraft and filmcraft-cli; the
from-source manifest built and installed only the desktop app, so a
Flatpak built from source had no headless CLI or stdio MCP server.

It now builds -p filmcraft -p filmcraft-cli and installs
/app/bin/filmcraft-cli. The default command stays filmcraft; the CLI
runs with `flatpak run --command=filmcraft-cli ai.storyteller.filmcraft`
(the manifest header and docs/releasing.md show it). Runtime, SDK and
finish-args are unchanged.

packaging-lint now also checks that both manifests install the same
programs, {filmcraft, filmcraft-cli}; it fails on the old manifest.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-09 15:37:09 +02:00
txiki739andClaude Opus 5.5 ae09ba904c #214: install script for the Linux tarball
The tarball now ships install.sh. It installs filmcraft, filmcraft-cli,
the desktop entry, icons, MIME type, metainfo and docs under ~/.local
without sudo; --prefix takes any absolute path (sudo ./install.sh
--prefix /usr/local for all users). Running it again updates.

The desktop entry's Exec/TryExec point at the installed binary's
absolute path, escaped per the Desktop Entry spec, so the menu entry
works without ~/.local/bin on PATH. The script checks the bundle is
complete before writing, refuses /, prefixes inside the extracted
bundle and characters launchers cannot express (=, %, control
characters), and treats the cache refresh tools as optional.

packaging/linux/test_install.py covers install and update, launching
through gio, bad arguments, an incomplete bundle, --help and a real
package.sh tarball build; Packaging lint runs it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-09 09:54:20 +02:00
86a531ad22 Release: FreeBSD, Flatpak (x86_64 + aarch64) and AppImage zsync; README Downloads (#267)
- release.yml: new `flatpak` jobs (x86_64 on ubuntu-24.04, aarch64 on ubuntu-24.04-arm) that
  repackage the Linux tarball as filmcraft-<v>-linux-<arch>.flatpak, and a `freebsd` job that
  builds filmcraft-<v>-freebsd-x86_64.tar.gz in a FreeBSD 14.3 VM; both feed the draft release.
- AppImages embed gh-releases-zsync update information and ship a .zsync beside them; the
  Linux job checks both.
- Jobs that sign nothing (version, Linux, Flatpak, FreeBSD, web) no longer use the `release`
  environment, so a dispatch on a branch dry-runs them; the signing jobs and the draft-release
  job stay in the environment, so nothing is published from a branch.
- packaging/linux/flatpak-bundle.sh + bundle manifest (same runtime and finish-args as the
  Flathub manifest; packaging-lint checks they agree), packaging/freebsd/package.sh (with a
  --dry-run that packaging-lint runs), and a nightly FreeBSD build workflow.
- README: Downloads section listing every build; docs/releasing.md updated.

Co-authored-by: Brandon Thomas <shared2@storyteller.ai>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-08 09:41:42 -04:00
Brandon ThomasandClaude Opus 5.5 61238bf8fc Release CI: macOS job on macos-15-xlarge
Custom macOS larger runners in a runner group do not pick up jobs; the
built-in M2 Pro label does. Only release.yml uses it, and the
actions_macos_xl budget caps the monthly spend.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-07 22:07:57 -04:00
Brandon ThomasandClaude Opus 5.5 08b769a92a Release CI: macOS job on the org macos-release runner
The standard macOS runners are shared with all CI and queue for an hour or
more. The macos-release runner (GitHub-hosted M2 Pro) is in a runner group
usable only by release.yml on the release branch, with a monthly spend cap
on the actions_macos_xl SKU.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-07 21:54:54 -04:00
Brandon ThomasandClaude Opus 5.5 86f3375775 Rename PrintCraft to PdfCraft (storytold/pdfcraft) (#177)
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-07 14:45:32 -04:00
Brandon ThomasandClaude Opus 5.5 9953befe28 Fonts: use craft-fonts as an optional build input
crates/text/build.rs embeds the fonts of a storytold/craft-fonts checkout
named by CRAFT_FONTS_DIR as filmcraft_text::fonts::CRAFT_FONTS (native:
all of them; wasm32: only BIZ UDPGothic Regular). Unset, CRAFT_FONTS is
empty and nothing changes. A bad CRAFT_FONTS_DIR is a warning, or an
error with CRAFT_FONTS_REQUIRED=1. Never a Cargo dependency, no network.

- UI: the Japanese faces are the last fallback of every egui font family
  (BIZ UDPGothic first, Bold first in the semibold/medium families).
- Text engine: registered after the bundled faces; fallback_for picks
  them after the bundled faces and before system faces (Mincho for serif
  text, Gothic otherwise, nearest weight).
- Tests: Japanese glyphs (no tofu) in the UI and title paths, skipped
  without craft-fonts; the theme works with CRAFT_FONTS empty.
- Release: every build job checks out craft-fonts at a pinned commit and
  builds with CRAFT_FONTS_DIR + CRAFT_FONTS_REQUIRED; packages carry
  OFL-<family>.txt. NOTICE, ATTRIBUTION.md (optional build input), AGENTS.md,
  CLAUDE.md, README and docs/contributing.md describe it.

FilmCraft main bundles no Japanese font, so no font files move.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-06 11:40:29 -04:00