Keep a package current

A saved Project starts generation for its active Targets and keeps automatic generation on by default. Configure a repository Delivery to receive updates as pull requests, then review the first result.

You need a Project, at least one active Target, and the GitHub App installed on each destination repository. Terminal steps use the authenticated Typeship CLI.

Review updates

1. Inspect the Project and its Targets. Confirm that each repository Delivery points to the intended repository and directory:

   typeship projects get <project_id>
   typeship targets list --project-id <project_id> --all
   typeship specs get <spec_id>

   Use the Project's spec_id in the last command. Project responses do not embed Targets or Deliveries.

2. Inspect the initial Generations and their results:

   typeship generations list --project-id <project_id>

   The Console shows the same history under Generations. Review each Target's files, warnings, coverage, and Delivery result. A missing destination or GitHub installation can prevent delivery while leaving a successful artifact available to download. Use Generate now to retry a Target when needed.

3. Review each changed Target's destination pull request. Confirm the package builds and the proposed version fits the changes. When no Draft is open and the destination already matches the package in the Draft, the result reports Up to date. An existing Draft keeps your commits and checks.

With automatic generation enabled, Typeship watches the Spec and starts Generations when you save Project config, Target config, or Delivery and check settings. A Target already queued or running reuses that Generation. See Generation behavior for polling and missed events.

Inspect history

Each Generation identifies its target_id, type, and spec_revision_id. Retrieve the revision to see the source used:

typeship spec-revisions get <revision_id>

List a Generation's files with typeship generations list-files <generation_id>, then read one with typeship files get <file_id>.

Handle a breaking change

Fix an unintended break in the source or a reviewed Spec patch, then regenerate. For an intentional break, follow Release a breaking change. Destination reviews compare against the last merged release, so several source changes can accumulate in one Draft.

See Generation behavior for change detection, file ownership, and Draft update behavior.