@reventlessdev/reventless-infra 3.0.0-alpha.84 → 3.0.0-alpha.86

package/CHANGELOG.md

@@ -3,6 +3,20 @@
 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.86 (2026-07-05)
+
+### Features
+
+* **reventless-aws:** opt-in [@aws](https://github.com/aws)_iam dual-auth for deploy-time AppSync callers ([94037f1](https://github.com/ReventlessDev/reventless-core/commit/94037f17ae48a33415b02e8e7b178906be8b59a4))
+
+
+# 3.0.0-alpha.85 (2026-07-05)
+
+### Features
+
+* **postgres:** add reventless-postgres backend + local-platform integration ([6913200](https://github.com/ReventlessDev/reventless-core/commit/69132001f9271e832a5af33416acd5b645feaf47))
+
+
 # 3.0.0-alpha.84 (2026-07-03)
 
 **Note:** Version bump only for package @reventlessdev/reventless-infra

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@reventlessdev/reventless-infra",
-  "version": "3.0.0-alpha.84",
+  "version": "3.0.0-alpha.86",
   "description": "Infrastructure types for Reventless framework",
   "license": "Apache-2.0",
   "dependencies": {

package/src/components/Api.res

@@ -45,6 +45,16 @@ type mutationSchemaEntry = {
       `docs/plans/host-ui-login-core.md`). In-memory enforcement still happens
       at the resolver layer via the same `commandAuthorization` function. */
   fieldPermissions?: dict<Reventless.Authorization.permission>,
+  /** Opt a mutation field into deploy-time IAM (SigV4) invocation in addition to
+      its Cognito authorization. When `true`, the AWS provider emits the
+      multi-auth directive form `@aws_cognito_user_pools(cognito_groups: [...])
+      @aws_iam` on the field instead of the single-mode `@aws_auth(...)`, so a
+      deploy-time system caller signing with ambient AWS credentials
+      (`Util_AppSync_Caller`) is authorized alongside the console UI. Opt-in per
+      field — only fields a system caller actually invokes should set this, and
+      the IAM principal must be scoped by the API resource policy / deploy-role
+      policy (see `docs/guides/appsync-iam-system-caller.md`). Default `false`. */
+  iamCallable?: bool,
   description?: string,
   linkedViews?: array<string>,
   consistencyRead?: string,
@@ -76,6 +86,11 @@ type querySchemaEntry = {
       `docs/plans/host-ui-login-core.md`). In-memory enforcement happens at
       the QueryDb resolver via the same field. */
   permission?: Reventless.Authorization.permission,
+  /** Opt the single-id and list query fields into deploy-time IAM (SigV4)
+      invocation in addition to their Cognito authorization. See
+      `mutationSchemaEntry.iamCallable` for the emitted directive form and
+      scoping requirements. Default `false`. */
+  iamCallable?: bool,
   excludeFields?: array<string>,
   description?: string,
   includeIdParam?: bool,

package/src/components/DcbEventLog.res

@@ -59,16 +59,31 @@ type read = (
   ~after: Reventless.DcbTag.sequencePosition=?,
 ) => promise<readResult>
 
+/**
+Typed DCB append outcome — mirrors `EventLog.appendError`. `Conflict` is the
+optimistic-concurrency sentinel (the append-condition failed: a matching event
+was written since `condition.after`), which the slice callback retries by
+re-reading and re-deciding. Every other failure is a `StorageFailure` carrying
+its message. Replaces the former string sentinel that conflated the two — a
+storage error whose text happened to contain "conflict" would have been retried
+forever, and backends disagreed on the sentinel's casing so conflict metrics were
+misclassified across backends.
+*/
+type appendError =
+  | Conflict
+  | StorageFailure(string)
+
 /**
 Appends raw events to the DCB log with optional optimistic-concurrency checking.
 
-Returns `Ok(position)` on success or `Error(reason)` if the append condition
-was violated (i.e. the log was modified since `condition.after`).
+Returns `Ok(position)` on success or `Error(Conflict)` if the append condition
+was violated (i.e. the log was modified since `condition.after`), or
+`Error(StorageFailure(_))` on any other failure.
 */
 type append = (
   array<rawEvent>,
   ~condition: Reventless.DcbTag.appendCondition=?,
-) => promise<result<Reventless.DcbTag.sequencePosition, string>>
+) => promise<result<Reventless.DcbTag.sequencePosition, appendError>>
 
 /**
 Streams events from the DCB log matching the given query.
@@ -91,7 +106,7 @@ Use for high-throughput batch imports.
 type appendStream = (
   Stream.t<rawEvent, string, unit>,
   ~condition: Reventless.DcbTag.appendCondition=?,
-) => Effect.t<result<Reventless.DcbTag.sequencePosition, string>, string, unit>
+) => Effect.t<result<Reventless.DcbTag.sequencePosition, appendError>, string, unit>
 
 /**
 Runtime operations exposed by a `DcbEventLog` component.