@reventlessdev/reventless-infra 3.0.0-alpha.153 → 3.0.0-alpha.155

package/CHANGELOG.md

@@ -3,6 +3,28 @@
 All notable changes to this project will be documented in this file.
 See [Conventional Commits](https://conventionalcommits.org) for commit guidelines.
 
+# 3.0.0-alpha.155 (2026-09-02)
+
+* feat(aws)!: the messaging sender is configuration, and a stack can choose to only log ([23b8b4b](https://github.com/ReventlessDev/reventless-core/commit/23b8b4bfe9c70555de4d74266ca686cb427485ca))
+
+### BREAKING CHANGES
+
+* `Capability_Messaging_Ses.make` is replaced by
+`Capability_Messaging.make(~name)`, which reads the transport and the address
+from config; the SES module keeps only `emailSender`. A deployment that named its
+sender in code must move it to `platform:messagingEmailSender` or the deploy is
+refused.
+
+
+
+# 3.0.0-alpha.154 (2026-09-01)
+
+**Note:** Version bump only for package @reventlessdev/reventless-infra
+
+
+
+
+
 # 3.0.0-alpha.153 (2026-09-01)
 
 ### Bug Fixes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@reventlessdev/reventless-infra",
-  "version": "3.0.0-alpha.153",
+  "version": "3.0.0-alpha.155",
   "description": "Infrastructure types for Reventless framework",
   "license": "Apache-2.0",
   "jest": {
@@ -17,9 +17,9 @@
     "sury-ppx": "11.0.0-rc.2",
     "uuid": "^13.0.0",
     "@reventlessdev/rescript-effect": "0.1.0-alpha.32",
-    "@reventlessdev/reventless-spec": "3.0.0-alpha.125",
+    "@reventlessdev/rescript-pulumi-pulumi": "2.3.0-alpha.19",
     "@reventlessdev/rescript-uuid": "2.0.0-alpha.0",
-    "@reventlessdev/rescript-pulumi-pulumi": "2.3.0-alpha.19"
+    "@reventlessdev/reventless-spec": "3.0.0-alpha.127"
   },
   "devDependencies": {
     "rescript": "12.3.0",

package/src/components/Api.res

@@ -19,16 +19,6 @@ let noApiVariantsId: S.Metadata.Id.t<Set.t<string>> =
 let noApiVariantId: S.Metadata.Id.t<bool> =
   S.Metadata.Id.make(~namespace="api", ~name="noApiVariant")
 
-/** Internal sury metadata ID storing per-variant allowed-state lists for AutoUI command filtering.
-    Maps variant name → set of status values under which the command is meaningful. */
-let allowedStatesId: S.Metadata.Id.t<dict<array<string>>> =
-  S.Metadata.Id.make(~namespace="api", ~name="allowedStates")
-
-/** Internal sury metadata ID storing per-variant target-state values for AutoUI board
-    transitions. Maps variant name → the single status the command's handler writes. */
-let targetStateId: S.Metadata.Id.t<dict<string>> =
-  S.Metadata.Id.make(~namespace="api", ~name="targetState")
-
 /** PPX helper: attaches the noApi flag to a command schema. Called by generated code. */
 let markNoApi = (schema: S.t<'a>): S.t<'a> =>
   schema->S.Metadata.set(~id=noApiId, true)
@@ -88,20 +78,6 @@ let markNoApiVariants = (schema: S.t<'a>, variants: array<string>): S.t<'a> => {
   marked->S.Metadata.set(~id=noApiVariantsId, excluded)
 }
 
-/** PPX helper: attaches per-variant allowedStates to a command schema. Called by generated code
-    emitted from the from-set of an @transition attribute. Each entry is (variantName, allowedStateNames). */
-let markAllowedStates = (
-  schema: S.t<'a>,
-  entries: array<(string, array<string>)>,
-): S.t<'a> => schema->S.Metadata.set(~id=allowedStatesId, Dict.fromArray(entries))
-
-/** PPX helper: attaches per-variant targetState to a command schema. Called by generated code
-    emitted from the target of an @transition attribute. Each entry is (variantName, targetStateName). */
-let markTargetState = (
-  schema: S.t<'a>,
-  entries: array<(string, string)>,
-): S.t<'a> => schema->S.Metadata.set(~id=targetStateId, Dict.fromArray(entries))
-
 /** Type alias for schema fragments (re-exports Plugin.apiSchemaFragment). */
 type schemaFragment = Reventless.Plugin.apiSchemaFragment
 

package/src/components/Api.res.mjs

@@ -9,10 +9,6 @@ let noApiVariantsId = Sury.$Metadata_Id_make("api", "noApiVariants");
 
 let noApiVariantId = Sury.$Metadata_Id_make("api", "noApiVariant");
 
-let allowedStatesId = Sury.$Metadata_Id_make("api", "allowedStates");
-
-let targetStateId = Sury.$Metadata_Id_make("api", "targetState");
-
 function markNoApi(schema) {
   return Sury.$Metadata_set(schema, noApiId, true);
 }
@@ -54,24 +50,12 @@ function markNoApiVariants(schema, variants) {
   return Sury.$Metadata_set(marked, noApiVariantsId, excluded);
 }
 
-function markAllowedStates(schema, entries) {
-  return Sury.$Metadata_set(schema, allowedStatesId, Object.fromEntries(entries));
-}
-
-function markTargetState(schema, entries) {
-  return Sury.$Metadata_set(schema, targetStateId, Object.fromEntries(entries));
-}
-
 export {
   noApiId,
   noApiVariantsId,
   noApiVariantId,
-  allowedStatesId,
-  targetStateId,
   markNoApi,
   variantNameOf,
   markNoApiVariants,
-  markAllowedStates,
-  markTargetState,
 }
 /* noApiId Not a pure module */

package/src/types/Platform.res

@@ -189,12 +189,33 @@ capability helper.
 `emailSender` is the verified address messages are sent *from* — a provider-side
 identity, not something an application picks per message, which is why it is a
 deploy-time handle rather than a field on `Messaging.message`. Absent when the
-deployment provisions no email channel.
+deployment provisions no email channel. It carries the whole `From:` header, so
+a deployment that configured a display name has it here rather than at the send.
 
 The channel set is derived from which senders are present rather than declared
 beside them, so a handle carrying no sender at all cannot claim a channel.
+
+`smsSender` is the origination number or sender id, on the same terms — with the
+difference that **no transport reads it yet**. It is carried so a stack can state
+the number where the other senders live, and so the field exists before the
+backend that needs it; the SMS channel appears when that backend does, not when
+this is set. A channel claimed ahead of its transport would collect preferences
+that silently deliver nothing, which is the failure the derived channel set above
+exists to prevent.
+
+`emailProvider` names the transport behind the email sender — the value a runtime
+reads to decide which backend to build. Per channel, like the senders themselves:
+an SMS transport is a separate choice, and one key for both would make choosing a
+mail sink also choose how texts go out. On the handle rather than resolved separately at
+each end, so the address and the thing that will send it are provisioned as one
+answer: a platform that read the choice from config itself could disagree with
+the helper that read the address.
 */
-type messagingSender = {emailSender?: Pulumi.Input.t<string>}
+type messagingSender = {
+  emailSender?: Pulumi.Input.t<string>,
+  smsSender?: Pulumi.Input.t<string>,
+  emailProvider?: Pulumi.Input.t<string>,
+}
 
 // Options for the shell's map view mode. Written to config.json flat, beside
 // `viewModes`, because that is where the shell reads them; carried on the arm