ContractSpec
ContractSpecOpen spec system
Menu

Choose your entry point

ProductTemplatesPricingDocsChangelogGitHub
Start with OSSExplore Studio
Back to changelog index

3.8.14

May 25, 2026 · 1 packages · 5 unique changes · 2 release entries

modules

This release affects the solutions family.

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

Release summaries

  • notifications-template-locale-hardening

    Normalize notification template locale resolution and merge partial locale channel overrides without dropping base channel content.

    maintainer

    Notification template rendering now resolves regional locales like `fr-CA` through the shared locale resolver and allows locale overrides to override only the fields that changed.

    integrator

    Localized notification templates no longer fall back to English for supported regional locale variants, and partial localized channel overrides retain the default title/action payload.

  • omnichannel-notifications

    Add concrete omnichannel notification channels for email, SMS, Telegram, and WhatsApp.

    maintainer

    Maintainers can wire provider-backed notification channels directly from the module instead of supplying their own email or messaging adapter layer.

    integrator

    Integrators can register ready-made email, SMS, Telegram, and WhatsApp channels and keep notification contracts aligned with those delivery targets.

Migration guide

  • Replace custom omnichannel notification wrappers

    Prefer the built-in provider-backed channels for email, SMS, Telegram, and WhatsApp.

    1. Import `ProviderEmailChannel`, `ProviderSmsChannel`, `TelegramChannel`, and `WhatsappChannel` from `@lssm-tech/module.notifications/channels`.
    2. Register those channels with `createChannelRegistry(...)` alongside any existing in-app, push, or webhook channels.
    3. Use the expanded notification channel enums when persisting or validating delivery targets.

Upgrade steps

  • Verify localized notification templates for regional locales

    manual

    Check that supported regional locales now reuse their base locale template content and that partial locale overrides retain default channel fields.

    Packages: @lssm-tech/module.notifications

    1. Upgrade to the patched `@lssm-tech/module.notifications` release.
    2. Exercise a localized template with a regional locale such as `fr-CA` or `es-MX`.
    3. Confirm that localized templates still preserve default title/action fields when only part of the channel content is overridden.

  • Update notification channel allowlists

    manual

    Add the new omnichannel values anywhere channel enums are mirrored outside the module.

    Packages: @lssm-tech/module.notifications

    1. Add `SMS`, `TELEGRAM`, and `WHATSAPP` to any application-level channel allowlists or validation layers that mirror the module enums.

Unique release changes

  • - Add concrete omnichannel notification channels for email, SMS, Telegram, and WhatsApp.

    1 packages · 1 occurrences

  • - Add the new omnichannel values anywhere channel enums are mirrored outside the module.

    1 packages · 1 occurrences

  • - Check that supported regional locales now reuse their base locale template content and that partial locale overrides retain default channel fields.

    1 packages · 1 occurrences

  • - Normalize notification template locale resolution and merge partial locale channel overrides without dropping base channel content.

    1 packages · 1 occurrences

  • - Prefer the built-in provider-backed channels for email, SMS, Telegram, and WhatsApp.

    1 packages · 1 occurrences

Impacted packages

  • @lssm-tech/module.notifications

    Layer: modules · 3 changes