Upload a Function Release

An upload creates an immutable function release in a project. It does not schedule work or change an existing executable.

thyme login
thyme upload update-value --tag v1

To select the destination explicitly:

thyme upload update-value --workspace WORKSPACE_ID --project PROJECT_ID --tag v1

Use the API base URL for your environment; see authentication. The supported short flags are -w, -p, and -t.

What is uploaded

The CLI bundles the TypeScript module and dependencies into bundle.js, packages the original source as source.ts, extracts the args schema, and includes optional permissions.json. The backend derives the release's callback metadata from the uploaded code. It computes the archive checksum and sends the bundle to /api/task/upload using authenticated multipart upload.

.env, local args.json, and local storage.json are not executable configuration. Set cloud inputs and bindings when creating the executable.

Tags and retry behavior

Tags are 1–32 lowercase letters, digits, dots, underscores, or hyphens, beginning with a letter or digit. latest is reserved. The first release defaults to v1; later uploads suggest an unused vN or accept an explicit tag.

The same active tag and archive checksum returns the existing release. Reusing a tag for different content conflicts. Deprecated and deleted tags remain reserved. The console's Latest label means most recently uploaded active version, not the highest semantic version.

An executable pins one function ID. Uploading v2 leaves users of v1 unchanged until they switch releases.

Inspect and use the release

The console's Functions catalog shows uploaded versions and their source, schema, callbacks, and permission details. Authorized users can also copy a release into another project in the workspace; that creates a separate destination function, not a shared executable.

Use the executable wizard, management CLI, or API to bind the release to a profile and schedule. See upload reference for flags and noninteractive behavior.