ContractSpecContractSpec

Start with OSS

Back to changelog index

4.4.0

Jul 16, 2026 · 3 packages · 7 unique changes · 1 release entry

appsbundlesBreaking changes

This release affects the solutions family.

Run contractspec connect adoption resolve --family solutions to see how it impacts your project.

Release summaries

  • canonical-release-pipeline

    Unify release authoring around guided capsules, canonical generated artifacts, and manifest-backed changelog surfaces.

    maintainer

    Release preparation now runs through guided `contractspec release prepare` and `contractspec release edit` flows, generated release artifacts become the canonical source of truth, and stable publish automation creates a GitHub Release from patch notes plus attached release artifacts.

    customer

    The public changelog now renders canonical release summaries, deprecations, migration guidance, and upgrade steps directly from the generated release manifest instead of scraping package changelogs.

    integrator

    Existing tooling that depended on `contractspec changelog` or on the `@lssm-tech/action.version` changelog side effect must move to `contractspec release prepare` plus `generated/releases/*`.

Deprecations

  • - `contractspec changelog generate` is no longer the supported release-authoring flow.
  • - `contractspec changelog show` is no longer the supported public release surface.

Migration guide

  • Replace the legacy changelog CLI flow

    Required

    Stop invoking `contractspec changelog` for release preparation and use `contractspec release prepare`, `contractspec release build`, or `contractspec release brief` instead.

    When: When local scripts, docs, or release automation still call the legacy changelog commands.

    1. Replace `contractspec changelog generate` and `contractspec changelog show` calls with the new release commands that match the workflow intent.
    2. Treat `generated/releases/manifest.json` and `generated/releases/upgrade-manifest.json` as the canonical inputs for downstream changelog and upgrade tooling.

  • Stop relying on action-version changelog side effects

    Required

    `@lssm-tech/action.version` no longer runs the generic changelog generator during bump mode.

    When: When CI expects the action to emit generic changelog files automatically.

    1. Generate canonical release artifacts with the release pipeline instead of expecting generic changelog output from the action.
    2. Read release data from `generated/releases/*` rather than from package changelog aggregation.

Upgrade steps

  • Use guided release authoring

    manual

    Create and revise release metadata through `contractspec release prepare` and `contractspec release edit` instead of editing capsules by hand.

    Packages: @lssm-tech/bundle.workspace, @lssm-tech/app.cli-contractspec, @lssm-tech/action.version, @lssm-tech/app.web-landing

    1. Run `contractspec release prepare` for new published-package release work.
    2. Run `contractspec release edit <slug>` to revise an existing release entry safely.

  • Publish canonical release artifacts

    assisted

    Stable release automation now uploads the release manifest, upgrade manifest, customer guide, and agent prompts, and uses generated patch notes as the GitHub Release body.

    Packages: @lssm-tech/bundle.workspace, @lssm-tech/app.cli-contractspec, @lssm-tech/action.version, @lssm-tech/app.web-landing

    1. Review `generated/releases/*` as part of release preparation.
    2. Use the attached release artifacts instead of scraping package CHANGELOG files or generic changelog JSON.

Unique release changes

  • - `@lssm-tech/action.version` no longer runs the generic changelog generator during bump mode.

    3 packages · 3 occurrences

  • - `contractspec changelog generate` is no longer the supported release-authoring flow.

    3 packages · 3 occurrences

  • - `contractspec changelog show` is no longer the supported public release surface.

    3 packages · 3 occurrences

  • - Create and revise release metadata through `contractspec release prepare` and `contractspec release edit` instead of editing capsules by hand.

    3 packages · 3 occurrences

  • - Stable release automation now uploads the release manifest, upgrade manifest, customer guide, and agent prompts, and uses generated patch notes as the GitHub Release body.

    3 packages · 3 occurrences

  • - Stop invoking `contractspec changelog` for release preparation and use `contractspec release prepare`, `contractspec release build`, or `contractspec release brief` instead.

    3 packages · 3 occurrences

  • - Unify release authoring around guided capsules, canonical generated artifacts, and manifest-backed changelog surfaces.

    3 packages · 3 occurrences

Impacted packages

  • @lssm-tech/app.cli-contractspec

    Layer: apps · 7 changes

  • @lssm-tech/app.web-landing

    Layer: apps · 7 changes

  • @lssm-tech/bundle.workspace

    Layer: bundles · 7 changes