@cloudflare/kumo 1.0.0 → 1.1.0

package/CHANGELOG.md

@@ -1,5 +1,15 @@
 # @cloudflare/kumo
 
+## 1.1.0
+
+### Minor Changes
+
+- 001f9e7: fixes to figma plugin init + zod v4 in kumo
+
+### Patch Changes
+
+- 6dc9a73: Fix `kumo` CLI bin resolution in repo checkouts so `pnpm install` doesn't warn when `dist/` hasn't been built yet.
+
 ## 1.0.0
 
 ### Major Changes

package/README.md

@@ -312,36 +312,32 @@ pnpm test:coverage
 
 ## Beta Releases
 
-Beta releases allow you to test changes before publishing to production. Beta versions are automatically created for merge requests and include the commit hash for identification.
+Beta releases allow you to test changes before publishing to production. Beta versions are automatically created for pull requests and include the commit hash for identification.
 
 ### Automated Beta Releases
 
-Beta releases are automatically triggered for merge requests through the CI pipeline configured in the root `.gitlab-ci.yml`:
+Beta releases are automatically triggered for pull requests through GitHub Actions (`.github/workflows/preview.yml`):
 
-**CI Job Configuration:**
+**Workflow Configuration:**
 
-- **Job Name**: `version-and-publish-beta`
-- **Stage**: `beta-release` (runs after build, checks, and tests)
-- **Triggers**: Automatically on merge requests with changes to `packages/kumo/**/*`
-- **Dependencies**: Requires `validate-changeset-run` job to pass
-- **Environment**: Node.js container with pnpm, jq, and git configured
-- **Authentication**: Uses Vault secrets for npm and GitLab API tokens
+- **Workflow**: `preview.yml`
+- **Triggers**: Pull requests with changes to `packages/kumo/**` or `.changeset/**`
+- **Dependencies**: Requires changeset to exist for `@cloudflare/kumo`
 
 **Process Flow:**
 
 1. **Validate**: Ensures changeset exists for `@cloudflare/kumo`
-2. **Version**: Runs `pnpm run version:beta` (executes `./ci/versioning/version-beta.sh`)
+2. **Version**: Runs `pnpm run version:beta`
    - Consumes pending changesets
    - Appends `-beta.{commit-hash}` to version number
-3. **Build**: Runs `pnpm run build` in `packages/kumo`
-4. **Publish**: Runs `pnpm run release:beta` to publish with `beta` tag
-5. **Verify**: Waits 45s for npm propagation and verifies publication
-6. **Notify**: Posts MR comment with installation instructions
+3. **Build**: Runs `pnpm --filter @cloudflare/kumo build`
+4. **Publish**: Publishes to npm with `beta` tag
+5. **Notify**: Posts PR comment with installation instructions
 
 **Secrets Required:**
 
 - `NPM_TOKEN`: Authentication for npm registry
-- `GITLAB_API_TOKEN`: For posting MR comments
+- `GITHUB_TOKEN`: For posting PR comments (built-in)
 
 ### Beta Version Format
 
@@ -355,7 +351,7 @@ For example: `0.1.0-beta.a1b2c3d`
 
 ### Installing Beta Versions
 
-When a beta is published, the MR will include a comment with installation instructions:
+When a beta is published, the PR will include a comment with installation instructions:
 
 ```bash
 # Install the specific beta version
@@ -367,15 +363,15 @@ pnpm add @cloudflare/kumo@0.1.0-beta.a1b2c3d
 
 ### Testing Beta Releases
 
-1. **Create MR**: Submit your changes with a changeset
+1. **Create PR**: Submit your changes with a changeset
 2. **Wait for Beta**: The beta job runs automatically after changeset validation passes
-3. **Install Beta**: Use the version from the MR comment
+3. **Install Beta**: Use the version from the PR comment
 4. **Test Changes**: Verify functionality in your project
-5. **Merge**: Once tested, merge the MR for production release
+5. **Merge**: Once tested, merge the PR for production release
 
 ### Changeset Validation
 
-All merge requests with changes to `packages/kumo/` must include a changeset:
+All pull requests with changes to `packages/kumo/` must include a changeset:
 
 ```bash
 # Create a changeset
@@ -416,9 +412,9 @@ This package uses [Changesets](https://github.com/changesets/changesets) for ver
 
 1. **Development**: Make changes to components or blocks
 2. **Changeset**: Create changeset describing the changes
-3. **Review**: Submit MR with changes and changeset
-4. **Beta Test**: Test the beta version published to the MR
-5. **Merge**: Merge MR to main branch
+3. **Review**: Submit PR with changes and changeset
+4. **Beta Test**: Test the beta version published to the PR
+5. **Merge**: Merge PR to main branch
 6. **Release**: Run the production release process
 
 ### Production Release Process
@@ -509,7 +505,7 @@ If the beta release job fails:
 1. **Check build**: Ensure `pnpm build` succeeds locally
 2. **Check npm token**: Verify npm authentication is configured in CI
 3. **Check version format**: Ensure version follows semver format
-4. **Review CI logs**: Check GitLab CI logs for specific error messages
+4. **Review CI logs**: Check GitHub Actions logs for specific error messages
 
 **Import Errors After Release**
 

package/ai/schemas.ts

@@ -7,6 +7,11 @@
 
 import { z } from "zod";
 
+// SafeParseReturnType was removed in Zod v4, but we still want stable typing.
+export type SafeParseResult<T> =
+  | { success: true; data: T; error?: never }
+  | { success: false; error: z.ZodError<any>; data?: never };
+
 // =============================================================================
 // Dynamic Value Schema (for data binding)
 // =============================================================================
@@ -573,7 +578,7 @@ export type UITree = z.infer<typeof UITreeSchema>;
 /**
  * Validate an element's props against its component schema
  */
-export function validateElementProps(element: UIElement): z.SafeParseReturnType<unknown, unknown> {
+export function validateElementProps(element: UIElement): SafeParseResult<unknown> {
   const schema = ComponentPropsSchemas[element.type as keyof typeof ComponentPropsSchemas];
   if (!schema) {
     return { success: false, error: new z.ZodError([{ code: 'custom', message: `Unknown component type: ${element.type}`, path: ['type'] }]) };
@@ -584,7 +589,7 @@ export function validateElementProps(element: UIElement): z.SafeParseReturnType<
 /**
  * Validate a complete UI tree
  */
-export function validateUITree(tree: unknown): z.SafeParseReturnType<unknown, UITree> {
+export function validateUITree(tree: unknown): SafeParseResult<UITree> {
   return UITreeSchema.safeParse(tree);
 }
 

package/bin/kumo.js

@@ -0,0 +1,32 @@
+#!/usr/bin/env node
+import { existsSync } from "node:fs";
+import path from "node:path";
+import { spawnSync } from "node:child_process";
+import { fileURLToPath, pathToFileURL } from "node:url";
+
+const __filename = fileURLToPath(import.meta.url);
+const __dirname = path.dirname(__filename);
+
+const distCliPath = path.resolve(__dirname, "../dist/command-line/cli.js");
+if (existsSync(distCliPath)) {
+  await import(pathToFileURL(distCliPath).href);
+  process.exit(0);
+}
+
+// In a repo checkout, the CLI may not be built yet. If `tsx` is available,
+// run the TypeScript entrypoint directly.
+const srcCliPath = path.resolve(__dirname, "../src/command-line/cli.ts");
+if (existsSync(srcCliPath)) {
+  const result = spawnSync(
+    process.execPath,
+    ["--import", "tsx", srcCliPath, ...process.argv.slice(2)],
+    { stdio: "inherit" },
+  );
+
+  process.exit(result.status ?? 1);
+}
+
+console.error(
+  "Kumo CLI entrypoint not found. If you're in the repo, run: pnpm --filter @cloudflare/kumo build",
+);
+process.exit(1);

package/dist/.build-complete

@@ -0,0 +1 @@
+1770420370035

package/dist/catalog.js

@@ -1,7 +1,7 @@
 "use client";
 let c = null, h = null;
 async function y() {
-  return c || h || (h = import("./schemas-BSdA0fz-.js").then((t) => (c = t, c)), h);
+  return c || h || (h = import("./schemas-Cbid4MwW.js").then((t) => (c = t, c)), h);
 }
 function l() {
   if (!c)