Promotes a build output into a new immutable release WITHOUT serving it — the…
Promotes a build output into a new immutable release WITHOUT serving it — the staged half of publishing, for when you want to check a release before it…
POST /v1/projects/{slug}/releases
| Address | https://api.hanzo.ai/v1/projects/{slug}/releases |
| Method | POST |
| Operation | post_projects_by_slug_releases |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Promotes a build output into a new immutable release WITHOUT serving it — the staged half of publishing, for when you want to check a release before it goes live. Answers 201.
source is a path RELATIVE to your org's own storage space: the org segment
is prepended server-side from the validated principal and the bucket is never
in the request at all, so a server-side copy can only ever reach bytes your
org already owns. The prefix is listed, content-addressed (SHA-256 over the
sorted manifest of key/size/etag), and copied into an immutable
<org>/.releases/<slug>/<id>/ prefix; the row is written LAST, so a partial
copy is unreachable rather than merely unlikely. Re-publishing an unchanged
source is idempotent BY CONSTRUCTION — same bytes, same id, no copy at all.
The source must contain index.html at its root and stay under the same file and byte caps an artifact deploy does (413 past them); a source that changes mid-copy is a 409 and the release is abandoned. Each publish also reclaims releases past the retention depth, so a site's release space stays bounded. This is the billable half — the hosting gate runs before any copy, and the debit lands once the release exists.
Scope: a validated principal is required (403 without one) and the site is resolved within that principal's org, so another tenant's slug is a 404.
Request
3 fields, body application/json (required).
| Field | In | Type | Required | Description |
|---|---|---|---|---|
slug | path | string | yes | Slug is the site to publish, from the path. |
slug | body | string | — | Slug is the site to publish, from the path. |
source | body | string | — | Source is the build output to promote, as a path RELATIVE to your org's own storage space — never a URL and never a bucket. |
Response
| Status | Body | Meaning |
|---|---|---|
201 | projectsRelease | created |
201 body — 8 fields.
| Field | In | Type | Always | Description |
|---|---|---|---|---|
active | body | boolean | — | Active is whether this is the release the site is SERVING right now. |
bytes | body | integer | — | Bytes is their total size in bytes. |
createdAt | body | integer | — | CreatedAt is when the release was cut, as Unix seconds — not when it was last activated. |
objects | body | integer | — | Objects is how many files the release holds. |
releaseId | body | string | — | ReleaseID is derived from a DIGEST of the release's own manifest, so identical content is the same release and a release can never be confused with another… |
slug | body | string | — | Slug is the site this release belongs to. |
source | body | string | — | Source is what the release was cut from — the build output or upload it was promoted out of. |
url | body | string | — | URL is where the site serves. |
Failure carries the platform error shape — see Errors.
Examples
hanzo has no subcommand for this operation — the CLI serves only what cloud's live route table confirms. Use HTTP or an SDK.
import { Configuration, ProjectsApi } from 'hanzoai';
const api = new ProjectsApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.postProjectsBySlugReleases({ slug: 'slug', slug: "<slug>", source: "<source>" });from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import ProjectsApi
client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = ProjectsApi(client).post_projects_by_slug_releases(slug='slug', slug="<slug>", source="<source>")cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.ProjectsAPI.PostProjectsBySlugReleases(context.Background()).Execute()
if err != nil {
return err
}use hanzo_cloud::apis::{configuration::Configuration, projects_api};
let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();
let result = projects_api::post_projects_by_slug_releases(&cfg, Default::default()).await?;import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.ProjectsApi;
ApiClient client = new ApiClient();
client.setRequestInterceptor(b -> b.header("Authorization", "Bearer " + System.getenv("HANZO_API_KEY")));
var result = new ProjectsApi(client).postProjectsBySlugReleases();The method above is the one at the current release of the document. [email protected] (npm) and [email protected] (PyPI) were generated from an earlier release, where this operation carried a different id, so it spells the method differently — regenerating the clients is what makes the two agree. SDKs →
curl -X POST https://api.hanzo.ai/v1/projects/<slug>/releases \
-H "Authorization: Bearer $HANZO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"slug": "<slug>",
"source": "<source>"
}'The door reaches projects through the projects tool, which names its 48 operations with its own verbs — this one among them, under a name only the door declares. describe explains any of them:
curl -X POST https://api.hanzo.ai/v1/mcp \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "describe",
"arguments": {
"op": "list_projects"
}
}
}'How is this guide?