Release Checklist

Use this checklist when releasing llamadart.

1. Pre-release validation#

# Print release-tier rows for evidence planning; this does not run validation.
dart run tool/testing/test_matrix.dart --tier release
dart format --output=none --set-exit-if-changed .
dart analyze
dart test
./tool/docs/build_site.sh
./tool/docs/validate_links.sh

Ensure migration/changelog docs reflect behavior in the release branch.

Before publishing a release that changes native runtime pins, verify native version alignment:

• hook/build.dart native-assets pins and darwin/llamadart/Package.swift Apple SPM pins must reference the same native repo releases.
• llamadart-native owns llama.cpp bridge artifacts for both native-assets and Apple SPM.
• litert-lm-native owns LiteRT-LM bridge artifacts for both native-assets and Apple SPM.
• If native versions changed, prefer the Sync Native Version, Bindings & SPM Pins workflow PR over hand-editing pins. That workflow updates Apple SPM checksums from the published native release asset digests.

2. Version and docs updates#

• Update pubspec.yaml version.
• Update CHANGELOG.md.
• Move accumulated Unreleased entries into the new version section; remove the Unreleased heading when it would otherwise be empty. Add it back only when the next unreleased change is documented.
• Update MIGRATION.md if breaking behavior changed.
• Keep docs pages aligned with new defaults/options.
• Keep local SwiftPM artifact caches out of pub archives: darwin/llamadart/Artifacts/ is for local/offline SPM testing only, and published packages should rely on the remote binary targets in darwin/llamadart/Package.swift.

3. Publish flow#

Tag with vX.Y.Z and push tag.

Current workflows involved:

• publish_pubdev.yml: publishes package release on version tags.
• docs_version_cut.yml: creates versioned docs snapshot on v* tags.
• docs_pages.yml: deploys docs to GitHub Pages after successful docs_version_cut.yml runs (and can be manually triggered).

4. Post-release verification#

• Verify pub.dev package page and API docs for the new version.
• Verify docs version selector includes the new release.
• Re-run smoke checks for representative examples.

5. If automation is blocked#

If docs_version_cut.yml cannot push directly to main (for example due to branch protections), run the version cut locally and open a PR:

cd website
npm ci
npm run docusaurus docs:version 0.6.2