Back to changelog index

4.2.8

May 25, 2026 · 18 packages · 3 unique changes · 1 release entry

appsintegrations

This release affects the integrations, solutions familyies.

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

Release summaries

  • split-provider-impls-targeted-packages

    Split provider implementations into targeted integration packages while preserving the legacy providers-impls facade.

    integrator

    Consumers can now install the provider implementation domain they need instead of the broad compatibility package.

    maintainer

    The legacy providers-impls package remains a compatibility facade and all-provider factory, with concrete implementation files owned by targeted packages.

Migration guide

  • Import concrete providers from targeted packages

    Required

    Replace direct provider imports such as `@lssm-tech/integration.providers-impls/impls/gmail-inbound` with targeted packages such as `@lssm-tech/integration.provider-email/impls/gmail-inbound`.

  • Keep the all-provider factory on providers-impls

    Required

    Continue importing `IntegrationProviderFactory` from `@lssm-tech/integration.providers-impls/impls/provider-factory` when you need broad provider routing.

Unique release changes

  • - Continue importing `IntegrationProviderFactory` from `@lssm-tech/integration.providers-impls/impls/provider-factory` when you need broad provider routing.

    18 packages · 18 occurrences

  • - Replace direct provider imports such as `@lssm-tech/integration.providers-impls/impls/gmail-inbound` with targeted packages such as `@lssm-tech/integration.provider-email/impls/gmail-inbound`.

    18 packages · 18 occurrences

  • - Split provider implementations into targeted integration packages while preserving the legacy providers-impls facade.

    18 packages · 18 occurrences

Impacted packages

  • @lssm-tech/app.api-library

    Layer: apps · 3 changes

  • @lssm-tech/integration.provider-analytics

    Layer: integrations · 3 changes

  • @lssm-tech/integration.provider-calendar

    Layer: integrations · 3 changes

  • @lssm-tech/integration.provider-database

    Layer: integrations · 3 changes

  • @lssm-tech/integration.provider-email

    Layer: integrations · 3 changes

  • @lssm-tech/integration.provider-embedding

    Layer: integrations · 3 changes

  • @lssm-tech/integration.provider-health

    Layer: integrations · 3 changes

  • @lssm-tech/integration.provider-llm

    Layer: integrations · 3 changes

  • @lssm-tech/integration.provider-meeting-recorder

    Layer: integrations · 3 changes

  • @lssm-tech/integration.provider-messaging

    Layer: integrations · 3 changes

  • @lssm-tech/integration.provider-openbanking

    Layer: integrations · 3 changes

  • @lssm-tech/integration.provider-payments

    Layer: integrations · 3 changes

  • @lssm-tech/integration.provider-project-management

    Layer: integrations · 3 changes

  • @lssm-tech/integration.provider-sms

    Layer: integrations · 3 changes

  • @lssm-tech/integration.provider-storage

    Layer: integrations · 3 changes

  • @lssm-tech/integration.provider-vector-store

    Layer: integrations · 3 changes

  • @lssm-tech/integration.provider-voice

    Layer: integrations · 3 changes

  • @lssm-tech/integration.providers-impls

    Layer: integrations · 3 changes