Skip to content
← Back to changelog index

7.1.4

Oct 27, 2026 · 3 packages · 8 unique changes · 4 release entries

integrationsmodules

This release affects the integrations, solutions families.

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

Release summaries

  • control-plane-definer-execute-grants

    Grant control-plane and Forms SECURITY DEFINER RLS predicates to their callers only, never PUBLIC

    maintainer

    Re-applying the channel runtime control-plane schema no longer reopens control_plane_runtime_has_scope to PUBLIC (and so to the Supabase anon/authenticated roles). EXECUTE goes to service_role and bound runtime roles only. New Forms scope-hardening runs no longer leave their definer predicates executable by PUBLIC.

    integrator

    A NOBYPASSRLS control-plane runtime role must be bound with control_plane_bind_runtime_workspace, which now grants it EXECUTE on the RLS predicate. A role that queries the control_plane_* or forms_* tables without being bound, owning them or being service_role now gets a permission error instead of relying on PUBLIC.

  • github-app-pkcs1-private-key

    GitHubAppHandler signs App JWTs with the PKCS#1 private keys GitHub downloads, and unreadable keys fail with GitHubAppError before any request. This is a patch fix: PKCS#1 keys never worked, and PKCS#8 keys behave as before.

    integrator

    Pass the .pem file GitHub generates for an App (BEGIN RSA PRIVATE KEY) as GitHubAppConfig.privateKey without converting it to PKCS#8 first. A key stored on one line with literal \n escapes, as in an environment variable, is accepted too. A malformed key now rejects getInstallationToken, createInstallationToken and listInstallations with GitHubAppError instead of a WebCrypto DataError.

  • notion-delta-owning-port

    Preserve Notion delta behavior through an owning adapter port

    integrator

    Existing Notion providers remain assignable without a reverse SDK dependency.

  • slack-oauth-events-users-fixes

    Slack OAuth sends the code exchange form-encoded, returns the user token and fails closed on revoke errors and token-less exchanges, channel_unarchived reaches the archived handler, and Slack user display names come from the profile. The runtime package is a minor release because SlackOAuth2TokenState.accessToken and tokenType are now optional, which matches what Slack returns for a user-scope-only install. No valid prior behavior is removed: the JSON exchange body could not obtain a token, the old routing passed a channel-id event to a handler typed for a channel object, and revoke failures were reported as success.

    integrator

    SlackOAuth2Handler.exchangeCode now posts client_id, client_secret, code and redirect_uri to oauth.v2.access as application/x-www-form-urlencoded params. Slack does not read JSON bodies for OAuth methods, so the previous JSON request could not complete a real install. The result adds an optional authedUser (id, scope, accessToken, tokenType, refreshToken) from Slack's authed_user, mapped only when it names a user, and fills refreshToken when Slack returns one. accessToken and tokenType are optional because a user-scope-only install has no bot token. exchangeCodeForBotToken returns SlackOAuth2BotTokenState, where both stay required, and rejects a user-only install with SlackOAuthError('missing_bot_token'). An exchange with neither a bot nor a user token rejects with missing_access_token. revokeToken sends a form-encoded request with the bearer token and throws SlackOAuthError with Slack's error code on an ok: false answer. SlackWebhookReceiver sends channel_unarchived events to handleChannelArchived (or handleEvent when it is absent). SlackMessagingProvider user lookups return profile.display_name, or an empty string when Slack has none. The user token is a new bearer credential in the exchange result: store it only through a SecretProvider that encrypts at rest and never log, trace or serialize the result. Token rotation is not supported yet, because the messaging.slack secret schema declares no refresh-token field. SlackOAuthError messages carry Slack's error code only, never the client secret, the authorization code or a token.

Migration guide

  • Re-apply the control-plane schema with the fixed runtime

    Required

    Databases where the old bootstrap ran keep control_plane_runtime_has_scope at PUBLIC EXECUTE until the fixed bootstrap runs once; it revokes PUBLIC and grants the real callers.

    1. Run the control-plane schema bootstrap (PostgresChannelRuntimeStore.initializeSchema, for example through the control-plane CLI runtime context) with this runtime version against each affected database.
    2. Verify read-only that no public SECURITY DEFINER function has PUBLIC EXECUTE and that anon and authenticated cannot execute control_plane_runtime_has_scope, while service_role and bound runtime roles can.

Upgrade steps

  • Guard the now-optional Slack bot token

    manual

    SlackOAuth2TokenState.accessToken and tokenType are optional, so strict TypeScript callers that read them from exchangeCode as string no longer compile.

    Packages: @lssm-tech/integration.runtime, @lssm-tech/integration.provider-messaging

    1. Call exchangeCodeForBotToken when the host needs a bot install; its result keeps accessToken and tokenType as string and it rejects a user-only install with SlackOAuthError('missing_bot_token').
    2. Otherwise check accessToken before use and read the user token from authedUser.accessToken.
  • Review Slack unarchive handlers and revoke callers

    manual

    Hosts that worked around the old routing by handling channel_unarchived inside handleChannelCreated should move that logic to handleChannelArchived, which receives the event with channel as a channel id. Callers of revokeToken should check that they handle the SlackOAuthError it now raises when Slack rejects the revocation.

    Packages: @lssm-tech/integration.runtime, @lssm-tech/integration.provider-messaging

    1. Move channel_unarchived handling from handleChannelCreated to handleChannelArchived and branch on event.type.
    2. Catch SlackOAuthError around revokeToken and retry or surface the error code.
  • Store Slack user tokens as encrypted secrets and keep token rotation off

    manual

    exchangeCode now returns the installing user's token (authedUser.accessToken, xoxp-). The user token acts as that person with every granted user scope, so a host that persists the whole exchange result would now store a second, user-scoped credential. Keep every Slack token in a secret store that encrypts at rest and out of logs, telemetry, errors, URLs and plaintext columns. The messaging.slack secret schema declares no refresh-token field and no runtime refreshes Slack tokens, so token rotation is not supported yet.

    Packages: @lssm-tech/integration.runtime, @lssm-tech/integration.provider-messaging

    1. Persist accessToken and authedUser.accessToken only through a SecretProvider that encrypts at rest (for example GcpSecretManagerProvider), as the botToken and userToken fields of the messaging.slack secret payload.
    2. Keep token rotation off for Slack apps that use this handler. If an exchange still returns refreshToken or authedUser.refreshToken, discard them; do not persist them in another secret field, a column or a configuration object until the contract declares refresh fields.
    3. Keep only the secret reference in database rows; never store a Slack token in a plaintext column or configuration object.
    4. Never log, trace or serialize the exchange result, and never copy a token into an error message, URL or telemetry attribute.
    5. Discard the authedUser tokens when the host requests no user scopes or has no user-scoped feature.
    6. Revoke both the bot token and any stored user token with revokeToken when a workspace disconnects.

Unique release changes

  • exchangeCode now returns the installing user's token (authedUser.accessToken, xoxp-). The user token acts as that person with every granted user scope, so a host that persists the whole exchange result would now store a second, user-scoped credential. Keep every Slack token in a secret store that encrypts at rest and out of logs, telemetry, errors, URLs and plaintext columns. The messaging.slack secret schema declares no refresh-token field and no runtime refreshes Slack tokens, so token rotation is not supported yet.

    2 packages · 2 occurrences

  • SlackOAuth2TokenState.accessToken and tokenType are optional, so strict TypeScript callers that read them from exchangeCode as string no longer compile.

    2 packages · 2 occurrences

  • Databases where the old bootstrap ran keep control_plane_runtime_has_scope at PUBLIC EXECUTE until the fixed bootstrap runs once; it revokes PUBLIC and grants the real callers.

    2 packages · 2 occurrences

  • Grant control-plane and Forms SECURITY DEFINER RLS predicates to their callers only, never PUBLIC

    2 packages · 2 occurrences

  • Hosts that worked around the old routing by handling channel_unarchived inside handleChannelCreated should move that logic to handleChannelArchived, which receives the event with channel as a channel id. Callers of revokeToken should check that they handle the SlackOAuthError it now raises when Slack rejects the revocation.

    2 packages · 2 occurrences

  • Slack OAuth sends the code exchange form-encoded, returns the user token and fails closed on revoke errors and token-less exchanges, channel_unarchived reaches the archived handler, and Slack user display names come from the profile. The runtime package is a minor release because SlackOAuth2TokenState.accessToken and tokenType are now optional, which matches what Slack returns for a user-scope-only install. No valid prior behavior is removed: the JSON exchange body could not obtain a token, the old routing passed a channel-id event to a handler typed for a channel object, and revoke failures were reported as success.

    2 packages · 2 occurrences

  • GitHubAppHandler signs App JWTs with the PKCS#1 private keys GitHub downloads, and unreadable keys fail with GitHubAppError before any request. This is a patch fix: PKCS#1 keys never worked, and PKCS#8 keys behave as before.

    1 package · 1 occurrence

  • Preserve Notion delta behavior through an owning adapter port

    1 package · 1 occurrence

Impacted packages

  • @lssm-tech/integration.provider-messaging

    Layer: integrations · 4 changes

  • @lssm-tech/integration.runtime

    Layer: integrations · 1 change

  • @lssm-tech/module.forms

    Layer: modules · 2 changes