current-cli 0.1.19__tar.gz → 0.1.21__tar.gz

{current_cli-0.1.19 → current_cli-0.1.21}/.gitignore

@@ -21,3 +21,6 @@ uv.lock
 # Node
 node_modules/
 dist/
+
+# Storybook build output
+storybook-static/

{current_cli-0.1.19 → current_cli-0.1.21}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: current-cli
-Version: 0.1.19
+Version: 0.1.21
 Summary: Command line interface for the Current API, generated from its OpenAPI schema at runtime
 Author-email: Orin <your-email@example.com>
 License-Expression: MIT

{current_cli-0.1.19 → current_cli-0.1.21}/current_cli/schema.yml

@@ -1568,7 +1568,13 @@ paths:
       description: |-
         Upsert a rendered workflow definition into a workspace and seed its
         record types (from the definition's ``emits[]`` plus the built-ins).
-        Existing workspace schemas are never overwritten.
+
+        A definition owns the schemas of the types it declares, so re-applying
+        updates them: the schema lives in the workflow repo and evolves with
+        the steps that stage the records, and a workspace pinned to the schema
+        of the *first* apply 422s every staged record the moment the two
+        drift (a renamed required property is enough). Built-in types and
+        emits that carry no schema never overwrite anything.
       tags:
       - workflows
       requestBody:
@@ -4291,6 +4297,9 @@ components:
         has_admin_gate:
           type: boolean
           readOnly: true
+        takes_project_input:
+          type: boolean
+          readOnly: true
         last_run:
           allOf:
           - $ref: '#/components/schemas/WorkflowRun'
@@ -4315,6 +4324,7 @@ components:
       - last_run
       - name
       - run_counts
+      - takes_project_input
       - trigger
       - updated_at
       - workspace

{current_cli-0.1.19 → current_cli-0.1.21}/llms.txt

@@ -535,7 +535,13 @@ Options:
 
 Upsert a rendered workflow definition into a workspace and seed its
 record types (from the definition's ``emits[]`` plus the built-ins).
-Existing workspace schemas are never overwritten.
+
+A definition owns the schemas of the types it declares, so re-applying
+updates them: the schema lives in the workflow repo and evolves with
+the steps that stage the records, and a workspace pinned to the schema
+of the *first* apply 422s every staged record the moment the two
+drift (a renamed required property is enough). Built-in types and
+emits that carry no schema never overwrite anything.
 
 POST /api/workflows/definitions/apply/
 

{current_cli-0.1.19 → current_cli-0.1.21}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "current-cli"
-version = "0.1.19"
+version = "0.1.21"
 description = "Command line interface for the Current API, generated from its OpenAPI schema at runtime"
 readme = "README.md"
 requires-python = ">=3.10"