@myapihq/sdk 2.16.4 → 2.17.0

package/dist/container.d.ts

@@ -50,6 +50,31 @@ export interface DeployResponse {
 export declare function createContainer(apiKey: string, orgId: string, payload: CreatePayload): Promise<CreateResponse>;
 export declare function listContainers(apiKey: string, orgId: string): Promise<Container[]>;
 export declare function getContainer(apiKey: string, orgId: string, containerId: string): Promise<Container>;
+/** The result of an environment change. `env` is the RESULT of the merge, so a
+ *  caller never has to GET afterwards to see what a PATCH did. */
+export interface EnvUpdate {
+    set: string[];
+    removed: string[];
+    /** Whether a new revision was rolled. False when the container has never been
+     *  deployed — the values are stored and apply on the first deploy. */
+    applied: boolean;
+    env: Record<string, string>;
+    revision?: string;
+    url?: string;
+    message?: string;
+}
+/**
+ * Change environment variables on an existing container.
+ *
+ * A MERGE: pass only what changes, and `null` to delete one. Everything else
+ * keeps its value — which matters, because replace semantics would mean
+ * resending every secret correctly to add one variable.
+ *
+ * Rolls a new revision on the SAME image; the container keeps its URL, its
+ * scoped key and its custom domain. Until 2026-08-19 this was impossible and
+ * the documented answer was to recreate the container.
+ */
+export declare function updateContainerEnv(apiKey: string, orgId: string, containerId: string, env: Record<string, string | null>): Promise<EnvUpdate>;
 export declare function deleteContainer(apiKey: string, orgId: string, containerId: string): Promise<void>;
 export interface SmokeCheck {
     path?: string;

package/dist/container.js

@@ -4,6 +4,7 @@ exports.EXPOSES = void 0;
 exports.createContainer = createContainer;
 exports.listContainers = listContainers;
 exports.getContainer = getContainer;
+exports.updateContainerEnv = updateContainerEnv;
 exports.deleteContainer = deleteContainer;
 exports.deployContainer = deployContainer;
 exports.listRevisions = listRevisions;
@@ -23,6 +24,7 @@ exports.EXPOSES = [
     'GET /container/orgs/{org_id}/containers',
     'GET /container/orgs/{org_id}/containers/{id}',
     'DELETE /container/orgs/{org_id}/containers/{id}',
+    'PATCH /container/orgs/{org_id}/containers/{id}',
     'POST /container/orgs/{org_id}/containers/{id}/deploy',
     'GET /container/orgs/{org_id}/containers/{id}/revisions',
     'POST /container/orgs/{org_id}/containers/{id}/promote',
@@ -40,6 +42,20 @@ async function listContainers(apiKey, orgId) {
 async function getContainer(apiKey, orgId, containerId) {
     return (0, client_1.request)('GET', `${config_1.CONTAINER_BASE}/container/orgs/${encodeURIComponent(orgId)}/containers/${encodeURIComponent(containerId)}`, apiKey);
 }
+/**
+ * Change environment variables on an existing container.
+ *
+ * A MERGE: pass only what changes, and `null` to delete one. Everything else
+ * keeps its value — which matters, because replace semantics would mean
+ * resending every secret correctly to add one variable.
+ *
+ * Rolls a new revision on the SAME image; the container keeps its URL, its
+ * scoped key and its custom domain. Until 2026-08-19 this was impossible and
+ * the documented answer was to recreate the container.
+ */
+async function updateContainerEnv(apiKey, orgId, containerId, env) {
+    return (0, client_1.request)('PATCH', `${config_1.CONTAINER_BASE}/container/orgs/${encodeURIComponent(orgId)}/containers/${encodeURIComponent(containerId)}`, apiKey, { env });
+}
 async function deleteContainer(apiKey, orgId, containerId) {
     return (0, client_1.request)('DELETE', `${config_1.CONTAINER_BASE}/container/orgs/${encodeURIComponent(orgId)}/containers/${encodeURIComponent(containerId)}`, apiKey);
 }

package/dist/version.d.ts

@@ -1 +1 @@
-export declare const SDK_VERSION = "2.16.4";
+export declare const SDK_VERSION = "2.17.0";

package/dist/version.js

@@ -8,4 +8,4 @@ exports.SDK_VERSION = void 0;
 // Why a constant and not a package.json read: the SDK runs inside edge
 // functions (Cloudflare Workers), so it must not import node:fs. A literal
 // is the only version source that works in every runtime we ship to.
-exports.SDK_VERSION = '2.16.4';
+exports.SDK_VERSION = '2.17.0';

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@myapihq/sdk",
   "license": "Apache-2.0",
-  "version": "2.16.4",
+  "version": "2.17.0",
   "description": "TypeScript SDK for the MyAPI ecosystem",
   "repository": {
     "type": "git",