Back to changelog index

7.8.0

Jun 01, 2026 · 3 packages · 9 unique changes · 5 release entries

appsbundleslibs

This release affects the sharedLibs, solutions familyies.

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

Release summaries

  • atomic-marketing-design-components

    Add design-system-owned marketing CTA, hero, prose, icon-grid, proof, CTA-band, and landing-page section sequence components; keep bundle.marketing section subpaths as compatibility shims.

    integrator

    Consumers can import full-page marketing composition primitives from the design-system root or focused marketing subpaths. Existing bundle.marketing section subpaths continue to render via thin wrappers.

    agent

    Marketing story/copy stays in bundle.marketing; generic atoms, molecules, sections, and the closed landing-page section union now belong in lib.design-system. Do not add runtime personalization or bundle imports to DS marketing components.

  • atomic-marketing-design-foundation

    Add design-system-owned full-page marketing sections and route CompanyOS landing composition through bundle compatibility shims.

    maintainer

    Generic marketing page primitives, sections, and a typed landing-page renderer now live in the design system while bundle.marketing retains content ownership.

    integrator

    Existing bundle marketing section subpaths remain compatible while new pages can compose design-system MarketingPageSection objects.

  • atomic-marketing-design-system-foundation

    Add a design-system-owned full-page marketing component foundation and keep bundle.marketing CompanyOS section imports compatible through thin adapters.

    maintainer

    lib.design-system now owns generic marketing CTA, hero, prose, icon-grid, proof-strip, CTA-band, and typed landing page section composition exports. bundle.marketing keeps public section subpaths available as compatibility adapters from LandingCta/content models into generic DS models.

    integrator

    Existing bundle.marketing section imports continue to resolve. New DS marketing exports are additive and should be used for product-neutral full marketing page composition.

  • companyos-marketing-narrative-atomic

    Improve the CompanyOS marketing surface with clearer governed-execution positioning and a reusable atomic, prop-driven section component set for hero, CTA, button row, and prose sections. CompanyOsLandingPage now composes those shared sections and renders the previously hidden built-on/studio block with Vision and Platform up-links.

    maintainer

    design-system owns the prop-driven marketing section primitives: CtaButtonRow, MarketingHero, MarketingCtaBand, ProseSection, and IconGridSection. bundle.marketing keeps compatibility subpath re-exports from @lssm-tech/bundle.marketing/components/marketing/sections. CompanyOsLandingPage is recomposed from the shared sections and external CTAs render with target="_blank" rel="noopener noreferrer".

    integrator

    The change is additive. Existing bundle.marketing imports continue to resolve; the preferred neutral imports now come from @lssm-tech/lib.design-system and the bundle subpaths remain optional compatibility shims and intended for composing CompanyOS marketing surfaces with the refreshed governed-execution narrative.

  • mega-menu-duplicate-link-keys

    Prevent duplicate React keys in design-system mega-menu panels with repeated link destinations.

    maintainer

    MegaMenuPanel now keys repeated destination links by column, position, href, and label fallback instead of href alone.

    integrator

    Marketing navigation menus can include multiple entries that intentionally route to the same page without React duplicate-key warnings.

    customer

    Marketing menu rendering is more stable when several solution cards link to the same page.

Migration guide

  • Existing bundle section subpaths continue to work

    CtaButtonRow, MarketingHero, MarketingCtaBand, ProseSection, and IconGridSection remain available from bundle.marketing and delegate to design-system components.

    1. Existing imports may remain unchanged.
    2. New generic marketing UI should prefer @lssm-tech/lib.design-system.
  • Compose generic landing pages with design-system marketing sections

    Keep product copy and content mapping in bundles/apps, then pass generic CTA, icon-grid, prose, summary, hero, and CTA-band sections to the design-system renderer.

    1. Import `MarketingLandingPage` and `MarketingPageSection` from `@lssm-tech/lib.design-system` for new generic marketing pages.
    2. Keep bundle-local compatibility wrappers in place for public `@lssm-tech/bundle.marketing/components/marketing/sections/*` subpaths.
    3. Do not import bundle content, app modules, or personalization runtime APIs from design-system marketing components.

Upgrade steps

  • Adopt design-system marketing components for generic landing pages

    manual

    Use the new @lssm-tech/lib.design-system marketing exports for generic full-page marketing structure while keeping story/content mapping in host bundles or applications.

    Packages: @lssm-tech/lib.design-system

    1. Import MarketingLandingPage and MarketingPageSection when rendering a known, typed sequence of marketing sections.
    2. Keep product-specific content, icon mapping, and LandingCta conversion outside lib.design-system; DS must not import bundle.marketing or app runtime personalization modules.
  • Adopt the shared CompanyOS marketing section components

    manual

    Use the exported section primitives when composing new CompanyOS marketing pages so narrative, CTA behavior, and layout stay consistent.

    Packages: @lssm-tech/lib.design-system, @lssm-tech/bundle.marketing

    1. Import CtaButtonRow, MarketingHero, MarketingCtaBand, ProseSection, and IconGridSection from @lssm-tech/lib.design-system for new surfaces. Existing @lssm-tech/bundle.marketing/components/marketing/sections imports remain valid.
    2. Keep the refreshed "AI proposes, your team approves" governed-execution narrative in content tokens rather than duplicating old AI-hype copy in components.

Unique release changes

  • - Add design-system-owned full-page marketing sections and route CompanyOS landing composition through bundle compatibility shims.

    3 packages · 3 occurrences

  • - Keep product copy and content mapping in bundles/apps, then pass generic CTA, icon-grid, prose, summary, hero, and CTA-band sections to the design-system renderer.

    3 packages · 3 occurrences

  • - Add a design-system-owned full-page marketing component foundation and keep bundle.marketing CompanyOS section imports compatible through thin adapters.

    2 packages · 2 occurrences

  • - Add design-system-owned marketing CTA, hero, prose, icon-grid, proof, CTA-band, and landing-page section sequence components; keep bundle.marketing section subpaths as compatibility shims.

    2 packages · 2 occurrences

  • - CtaButtonRow, MarketingHero, MarketingCtaBand, ProseSection, and IconGridSection remain available from bundle.marketing and delegate to design-system components.

    2 packages · 2 occurrences

  • - Improve the CompanyOS marketing surface with clearer governed-execution positioning and a reusable atomic, prop-driven section component set for hero, CTA, button row, and prose sections. CompanyOsLandingPage now composes those shared sections and renders the previously hidden built-on/studio block with Vision and Platform up-links.

    2 packages · 2 occurrences

  • - Use the exported section primitives when composing new CompanyOS marketing pages so narrative, CTA behavior, and layout stay consistent.

    2 packages · 2 occurrences

  • - Use the new @lssm-tech/lib.design-system marketing exports for generic full-page marketing structure while keeping story/content mapping in host bundles or applications.

    2 packages · 2 occurrences

  • - Prevent duplicate React keys in design-system mega-menu panels with repeated link destinations.

    1 packages · 1 occurrences

Impacted packages

  • @lssm-tech/app.web-application-monolith

    Layer: apps · 2 changes

  • @lssm-tech/bundle.marketing

    Layer: bundles · 2 changes

  • @lssm-tech/lib.design-system

    Layer: libs · 2 changes