Release status

smif status is the read-only checkpoint between a changeset and version edits.

smif status

What it computes

Semifold loads configured packages into one dependency graph, merges requested bump levels, applies release-channel and dependency-propagation rules, and displays:

• current and target versions for every affected package;
• direct reasons such as .changes/add-api.md;
• packages included by dependency or shared-version propagation;
• warnings and a deterministic 12-character plan fingerprint.

The same release decision is recomputed by smif version from the same repository inputs. status does not persist a plan and does not edit manifests, changelogs, configuration, or changesets.

Pull-request comments

smif status --comment

--comment publishes the status report as a GitHub pull-request comment and is only valid in the expected CI environment. The workflow generated by smif init uses this path for review feedback.

With global --dry-run, Semifold may collect and render the read-only facts needed for the comment preview, but it never creates or updates the pull-request comment.

If GitHub rejects comment creation or update, the release plan remains available and status completes successfully. The warning includes the failed operation, GitHub API status and message, any documentation URL returned by GitHub, and a permission hint for 403 Forbidden responses.

If a package, target version, or reason is wrong, correct the changeset or dependency configuration rather than manually editing a package version.

GitHub error diagnostics

GitHub failures identify the operation and include the HTTP status, API message, validation details, and documentation link when available. Client failures include their underlying error chain. These details do not require --debug; GitHub tokens are redacted. A 403 includes permission checks appropriate to the operation, without assuming that permissions are the only possible cause.

Comment and changed-file queries, including pagination, report detailed failures. Comment creation or update failures remain warnings and do not invalidate the release plan.