@remit/api-http-client 0.0.75 → 0.0.77

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@remit/api-http-client",
-  "version": "0.0.75",
+  "version": "0.0.77",
   "type": "module",
   "exports": {
     ".": "./index.ts",

package/types.gen.ts

@@ -984,6 +984,10 @@ export type RemitImapCalendarSuggestionResponse = {
      * Projection of the VEVENT's effective end as an ISO 8601 date-time with zone offset, resolved from DTEND or from DTSTART + DURATION. An event with neither ends when it starts (RFC 5545 3.6.1).
      */
     dtEnd: String64;
+    /**
+     * The UTC instant (ISO 8601, `Z` suffix) after which nothing of this event remains to attend: the end of the last occurrence of a bounded series, `9999-12-31T23:59:59Z` for an open-ended one. Unlike `dtEnd` it compares correctly as a string across offsets, which is what lets a list drop events that are over.
+     */
+    endsAtUtc: String64;
     /**
      * Whether DTSTART is a DATE rather than a DATE-TIME (RFC 5545 3.3.4) — an all-day or multi-day event, whose end is exclusive.
      */
@@ -7243,9 +7247,18 @@ export type MessageOperationsDescribeMessageErrors = {
      */
     401: ApiError;
     /**
-     * Nothing answers to this address, or the caller may not learn that something does. `code` is `not_found`.
+     * No message answers to this id, or the caller may not learn that one does.
+     * `code` is `not_found`, or `message_gone_from_server` when the mail server no
+     * longer holds the message at its UID — another client expunged it or moved it
+     * away before its body was stored. That answer carries `details.messageId`.
      */
     404: ApiError;
+    /**
+     * The same flat 409 body, for a message whose folder and uid do not name the same message.
+     *
+     * `code: "message_placement_unsettled"` — the message is mid-move, so its row names the destination folder while its uid still belongs to the source; acting on that pair would hit whatever the destination holds at that uid. `details` carries `accountId`, `messageId` and `reason`, one of: `in_flight` (the move is still running, and the same request succeeds once it confirms) or `unverified` (the move gave up without confirming, so where the message sits is unknown until the folder is resynced).
+     */
+    409: ApiError;
     /**
      * The request is well-formed but the thing it names cannot be produced. `code` is `unprocessable_entity`.
      */
@@ -7371,9 +7384,18 @@ export type MessageOperationsGetRawMessageErrors = {
      */
     401: ApiError;
     /**
-     * Nothing answers to this address, or the caller may not learn that something does. `code` is `not_found`.
+     * No message answers to this id, or the caller may not learn that one does.
+     * `code` is `not_found`, or `message_gone_from_server` when the mail server no
+     * longer holds the message at its UID — another client expunged it or moved it
+     * away before its body was stored. That answer carries `details.messageId`.
      */
     404: ApiError;
+    /**
+     * The same flat 409 body, for a message whose folder and uid do not name the same message.
+     *
+     * `code: "message_placement_unsettled"` — the message is mid-move, so its row names the destination folder while its uid still belongs to the source; acting on that pair would hit whatever the destination holds at that uid. `details` carries `accountId`, `messageId` and `reason`, one of: `in_flight` (the move is still running, and the same request succeeds once it confirms) or `unverified` (the move gave up without confirming, so where the message sits is unknown until the folder is resynced).
+     */
+    409: ApiError;
 };
 
 export type MessageOperationsGetRawMessageError = MessageOperationsGetRawMessageErrors[keyof MessageOperationsGetRawMessageErrors];