@theholocron/holocron-plugin-netlify 5.0.0-alpha.112 → 5.0.0-alpha.114

package/README.md

@@ -75,11 +75,6 @@ builder, poll to `ready`, fetch the live URL) using this plugin's own
 built `createPlugin()` output.
 
 - `listProjects` / `ensureProject` → `sites.list` / `sites.create`
-- `deployFunction` → `deploys.createFromZip` — Netlify runs no build
-  step for a raw zip upload, so the caller (Sentinel's own stage-deploy
-  script) is responsible for already having resolved dependencies into
-  the file set, the same discipline Vercel's `deployFunction` path
-  requires via its own trimmed/pinned `package.json`.
 - `getDeployment` → `deploys.get`
 - `listEnvVars` / `setEnvVar` → `env.list` / `env.set`
 - `ensureCustomDomain` → `sites.update({ custom_domain })`; returns a
@@ -96,7 +91,18 @@ current consumer** (best-effort, see inline comments in
 - `triggerDeployment` → `sites.triggerBuild`, untested against a real
   git-linked Netlify site.
 
-Not implemented: `listPreviewDeployments` / `deletePreviewDeployments`
+Not implemented: `deployFunction` — the capability interface's
+`DeployFunctionConfig.files` is `Record<string, string>` (text only,
+matching Vercel's model: upload source, let the platform's own build
+step install dependencies server-side). Netlify's real function-deploy
+API runs no install step at all for a raw upload — a function needs
+its real `node_modules` (binary native addons, wasm) zipped in
+alongside it, which a text-only files map structurally cannot carry.
+Sentinel's own stage-deploy script calls
+`@theholocron/netlify-client`'s `deploys.create()` directly instead of
+going through `holocron deploy` / this capability for that reason.
+Same precedent as Cloudflare Pages omitting this method. Also not
+implemented: `listPreviewDeployments` / `deletePreviewDeployments`
 (both optional on the interface) — no current consumer needs
 branch-preview listing/cleanup.
 

package/dist/index.d.mts

@@ -1,5 +1,5 @@
 import { NetlifyClient } from "@theholocron/netlify-client";
-import { AuthError, DeployFunctionConfig, DeployFunctionResult, Deployment, DeploymentProject, DeploymentProjectSettings, DeploymentRecord, DeploymentTarget, DeploymentTrigger, DnsRecordRequest, ResolveTokenInput } from "@theholocron/cli";
+import { AuthError, Deployment, DeploymentProject, DeploymentProjectSettings, DeploymentRecord, DeploymentTarget, DeploymentTrigger, DnsRecordRequest, ResolveTokenInput } from "@theholocron/cli";
 //#region src/auth.d.ts
 declare const resolveToken: (input?: ResolveTokenInput) => string;
 //#endregion
@@ -54,15 +54,6 @@ declare class NetlifyDeployment implements Deployment {
     target?: DeploymentTrigger;
   }): Promise<DeploymentRecord>;
   getDeployment(deploymentId: string): Promise<DeploymentRecord>;
-  /**
-   * Zips `config.files` (plain text, per the interface contract) and
-   * uploads it as a one-shot deploy. Netlify runs no build step for a
-   * raw zip upload — the caller (Sentinel's own stage-deploy script) is
-   * responsible for having already resolved dependencies into the file
-   * set, the same discipline Vercel's `deployFunction` path already
-   * requires via its own trimmed/pinned package.json.
-   */
-  deployFunction(projectId: string, config: DeployFunctionConfig): Promise<DeployFunctionResult>;
   /**
    * Idempotent: PATCHing the same `custom_domain` twice is a no-op on
    * Netlify's side. Unlike Vercel, Netlify's API has no DNS-misconfiguration

package/dist/index.mjs

@@ -98,21 +98,6 @@ var NetlifyDeployment = class {
 		return toDeploymentRecord(await this.client().deploys.get(deploymentId));
 	}
 	/**
-	* Zips `config.files` (plain text, per the interface contract) and
-	* uploads it as a one-shot deploy. Netlify runs no build step for a
-	* raw zip upload — the caller (Sentinel's own stage-deploy script) is
-	* responsible for having already resolved dependencies into the file
-	* set, the same discipline Vercel's `deployFunction` path already
-	* requires via its own trimmed/pinned package.json.
-	*/
-	async deployFunction(projectId, config) {
-		const deploy = await this.client().deploys.createFromZip(projectId, config.files, { draft: config.target === void 0 });
-		return {
-			deploymentId: deploy.id,
-			url: deploy.ssl_url || deploy.url
-		};
-	}
-	/**
 	* Idempotent: PATCHing the same `custom_domain` twice is a no-op on
 	* Netlify's side. Unlike Vercel, Netlify's API has no DNS-misconfiguration
 	* check to consult — it's returned unconditionally once set, which is

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@theholocron/holocron-plugin-netlify",
-  "version": "5.0.0-alpha.112",
+  "version": "5.0.0-alpha.114",
   "description": "Holocron plugin for Netlify. Implements the deployment capability against Netlify's REST API, plus exports verifyToken + AUTH_HINT for `holocron auth`.",
   "keywords": [
     "deployment",
@@ -41,11 +41,11 @@
     "tsx": "4.23.12",
     "typescript": "^5.9.3",
     "vitest": "^4.1.11",
-    "@theholocron/cli": "5.0.0-alpha.112"
+    "@theholocron/cli": "5.0.0-alpha.114"
   },
   "peerDependencies": {
     "@theholocron/netlify-client": "^1.36.0",
-    "@theholocron/cli": "5.0.0-alpha.112"
+    "@theholocron/cli": "5.0.0-alpha.114"
   },
   "peerDependenciesMeta": {
     "@theholocron/netlify-client": {}