create-manifest

To generate a Trellis migration manifest from git commits, analyze the commit history since your previous release tag to extract user-observable behavior changes. This process categorizes conventional commits to produce the required JSON fields for breaking behaviors and recommendMigrate rules.

Automating docs-site changelog updates involves generating matching MDX changelog files from your git commit history. It updates the docs.json navbar and page lists to synchronize mirrored English and Chinese sections for the new release version.

A migration manifest is a JSON file that defines breaking behaviors and file migrations so `trellis update` can guide users correctly. You need one for patch, beta, rc, and minor releases where changelog voice and migration actions must be strictly accurate.

Changelog generation supports both English and Chinese MDX files by applying strict MDX structure rules. It mirrors the technical content across both language sections to ensure accurate docs-site synchronization for diverse audiences.

You need conventional commit-style messages to generate accurate release changelogs. The analysis process relies on these commit conventions to draft technical changelog entries focused on user-observable source behavior.

Manually written Trellis manifests fail during `trellis update` when they lack correct JSON fields for breaking behavior or recommendMigrate rules. Automating manifest generation from git commits ensures strict manifest correctness and prevents manual oversights.