mainsequence 6.0.24__tar.gz → 6.0.26__tar.gz

{mainsequence-6.0.24/mainsequence.egg-info → mainsequence-6.0.26}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: mainsequence
-Version: 6.0.24
+Version: 6.0.26
 Summary: Main Sequence SDK 
 Author-email: Main Sequence GmbH <dev@main-sequence.io>
 License-Expression: LicenseRef-MainSequence-Proprietary
@@ -85,28 +85,21 @@ Main package areas:
 
 Repository areas:
 
-- `docs/`: tutorials, knowledge guides, CLI docs, and generated reference docs
-- `examples/`: worked examples and usage patterns
+- `docs/`: knowledge guides, CLI docs, and generated reference docs
 - `tests/`: automated tests
 
 ## Documentation map
 
-The documentation is organized into four reading modes:
+The documentation is organized into three reading modes:
 
-1. **Tutorial**: the guided learning path
-2. **Knowledge**: deeper conceptual guides
-3. **CLI**: command-focused operational documentation
-4. **Reference**: generated API reference
+1. **Knowledge**: deeper conceptual guides
+2. **CLI**: command-focused operational documentation
+3. **Reference**: generated API reference
 
 Recommended entry points:
 
-- Tutorial:
-  - [Setting a Project (CLI)](docs/tutorial/setting_a_project.md)
-  - [Working With MetaTables](docs/tutorial/working_with_meta_tables.md)
-  - [Creating a Data Node](docs/tutorial/creating_a_simple_data_node.md)
-  - [Role-Based Access Control](docs/tutorial/role_based_access_control.md)
-  - [Create Your First API](docs/tutorial/create_your_first_api.md)
-  - [Turn Your Project Into an Agent](docs/tutorial/project_to_agent.md)
+- Beginner tutorial:
+  - [MainSequence SDK tutorial Project](https://github.com/mainsequence-projects/mainsequence-sdk-tutorial)
 - Knowledge:
   - [Data Nodes](docs/knowledge/data_nodes.md)
   - [MetaTables](docs/knowledge/meta_tables/index.md)
@@ -220,7 +213,7 @@ black .
 
 If you are evaluating the platform:
 
-- start with the tutorial in `docs/tutorial/`
+- start with the separate canonical tutorial Project linked above
 
 If you are building a feature and already know the area:
 

{mainsequence-6.0.24 → mainsequence-6.0.26}/README.md

@@ -40,28 +40,21 @@ Main package areas:
 
 Repository areas:
 
-- `docs/`: tutorials, knowledge guides, CLI docs, and generated reference docs
-- `examples/`: worked examples and usage patterns
+- `docs/`: knowledge guides, CLI docs, and generated reference docs
 - `tests/`: automated tests
 
 ## Documentation map
 
-The documentation is organized into four reading modes:
+The documentation is organized into three reading modes:
 
-1. **Tutorial**: the guided learning path
-2. **Knowledge**: deeper conceptual guides
-3. **CLI**: command-focused operational documentation
-4. **Reference**: generated API reference
+1. **Knowledge**: deeper conceptual guides
+2. **CLI**: command-focused operational documentation
+3. **Reference**: generated API reference
 
 Recommended entry points:
 
-- Tutorial:
-  - [Setting a Project (CLI)](docs/tutorial/setting_a_project.md)
-  - [Working With MetaTables](docs/tutorial/working_with_meta_tables.md)
-  - [Creating a Data Node](docs/tutorial/creating_a_simple_data_node.md)
-  - [Role-Based Access Control](docs/tutorial/role_based_access_control.md)
-  - [Create Your First API](docs/tutorial/create_your_first_api.md)
-  - [Turn Your Project Into an Agent](docs/tutorial/project_to_agent.md)
+- Beginner tutorial:
+  - [MainSequence SDK tutorial Project](https://github.com/mainsequence-projects/mainsequence-sdk-tutorial)
 - Knowledge:
   - [Data Nodes](docs/knowledge/data_nodes.md)
   - [MetaTables](docs/knowledge/meta_tables/index.md)
@@ -175,7 +168,7 @@ black .
 
 If you are evaluating the platform:
 
-- start with the tutorial in `docs/tutorial/`
+- start with the separate canonical tutorial Project linked above
 
 If you are building a feature and already know the area:
 

{mainsequence-6.0.24 → mainsequence-6.0.26}/agent_scaffold/skills/platform_operations/orchestration_and_releases/SKILL.md

@@ -253,6 +253,7 @@ The SDK surface also accepts:
 Do not claim there is a CLI command for `deploy_current_version` unless the local CLI actually exposes one. In this SDK, the manual detail action is available through the client model.
 
 Inspect the unified run's `state`, `phase`, `outcome`, `steps`, `logs`, and `error` fields. Do not use legacy resource-release deployment status fields or filters.
+Detail responses also expose `builder_image` and `builder_runtime`; these are empty strings when the run has no static-site builder metadata.
 
 ## Review Rules
 

{mainsequence-6.0.24 → mainsequence-6.0.26}/mainsequence/client/models_helpers.py

@@ -1292,6 +1292,8 @@ class DeploymentRun(BaseObjectOrm, BasePydanticModel):
     artifact_context: dict[str, Any] = Field(default_factory=dict)
     cleanup_context: dict[str, Any] = Field(default_factory=dict)
     result: dict[str, Any] = Field(default_factory=dict)
+    builder_image: str = ""
+    builder_runtime: str = ""
     steps: list[DeploymentRunStep] = Field(default_factory=list)
     logs: DeploymentRunLogReference
     error: DeploymentRunError | None = None

{mainsequence-6.0.24 → mainsequence-6.0.26/mainsequence.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: mainsequence
-Version: 6.0.24
+Version: 6.0.26
 Summary: Main Sequence SDK 
 Author-email: Main Sequence GmbH <dev@main-sequence.io>
 License-Expression: LicenseRef-MainSequence-Proprietary
@@ -85,28 +85,21 @@ Main package areas:
 
 Repository areas:
 
-- `docs/`: tutorials, knowledge guides, CLI docs, and generated reference docs
-- `examples/`: worked examples and usage patterns
+- `docs/`: knowledge guides, CLI docs, and generated reference docs
 - `tests/`: automated tests
 
 ## Documentation map
 
-The documentation is organized into four reading modes:
+The documentation is organized into three reading modes:
 
-1. **Tutorial**: the guided learning path
-2. **Knowledge**: deeper conceptual guides
-3. **CLI**: command-focused operational documentation
-4. **Reference**: generated API reference
+1. **Knowledge**: deeper conceptual guides
+2. **CLI**: command-focused operational documentation
+3. **Reference**: generated API reference
 
 Recommended entry points:
 
-- Tutorial:
-  - [Setting a Project (CLI)](docs/tutorial/setting_a_project.md)
-  - [Working With MetaTables](docs/tutorial/working_with_meta_tables.md)
-  - [Creating a Data Node](docs/tutorial/creating_a_simple_data_node.md)
-  - [Role-Based Access Control](docs/tutorial/role_based_access_control.md)
-  - [Create Your First API](docs/tutorial/create_your_first_api.md)
-  - [Turn Your Project Into an Agent](docs/tutorial/project_to_agent.md)
+- Beginner tutorial:
+  - [MainSequence SDK tutorial Project](https://github.com/mainsequence-projects/mainsequence-sdk-tutorial)
 - Knowledge:
   - [Data Nodes](docs/knowledge/data_nodes.md)
   - [MetaTables](docs/knowledge/meta_tables/index.md)
@@ -220,7 +213,7 @@ black .
 
 If you are evaluating the platform:
 
-- start with the tutorial in `docs/tutorial/`
+- start with the separate canonical tutorial Project linked above
 
 If you are building a feature and already know the area:
 

{mainsequence-6.0.24 → mainsequence-6.0.26}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "mainsequence"
-version = "6.0.24"
+version = "6.0.26"
 description = "Main Sequence SDK "
 readme = "README.md"
 requires-python = ">=3.13"

{mainsequence-6.0.24 → mainsequence-6.0.26}/tests/test_filter_normalization.py

@@ -2224,6 +2224,8 @@ def test_resource_release_deploy_current_version_posts_detail_action(monkeypatch
                 "artifact_context": {},
                 "cleanup_context": {},
                 "result": {},
+                "builder_image": "",
+                "builder_runtime": "",
                 "steps": [],
                 "logs": {
                     "state": "available",
@@ -2250,6 +2252,8 @@ def test_resource_release_deploy_current_version_posts_detail_action(monkeypatch
     assert run.state == "succeeded"
     assert run.phase == "completed"
     assert run.outcome == "deployed"
+    assert run.builder_image == ""
+    assert run.builder_runtime == ""
     assert run.logs.state == "available"
     assert run.error is None
     assert captured == {
@@ -2287,6 +2291,8 @@ def test_deployment_run_collection_and_detail_use_unified_resource_release_contr
         "artifact_context": {},
         "cleanup_context": {},
         "result": {},
+        "builder_image": "",
+        "builder_runtime": "",
         "steps": [],
         "logs": {
             "state": "available",
@@ -2296,6 +2302,22 @@ def test_deployment_run_collection_and_detail_use_unified_resource_release_contr
         "error": None,
     }
 
+    collection_payload = {
+        key: value
+        for key, value in response_payload.items()
+        if key
+        not in {
+            "revision_context",
+            "trigger_context",
+            "artifact_context",
+            "cleanup_context",
+            "result",
+            "builder_image",
+            "builder_runtime",
+            "steps",
+        }
+    }
+
     class FakeResponse:
         status_code = 200
 
@@ -2308,7 +2330,7 @@ def test_deployment_run_collection_and_detail_use_unified_resource_release_contr
     def _fake_make_request(*, s, loaders, r_type, url, payload, time_out=None):
         captured.append({"r_type": r_type, "url": url, "payload": payload})
         if url.rstrip("/") == models_helpers_mod.DeploymentRun.get_object_url():
-            return FakeResponse({"results": [dict(response_payload)], "next": None})
+            return FakeResponse({"results": [dict(collection_payload)], "next": None})
         return FakeResponse(dict(response_payload))
 
     monkeypatch.setattr(
@@ -2329,6 +2351,8 @@ def test_deployment_run_collection_and_detail_use_unified_resource_release_contr
     assert detail.state == "succeeded"
     assert detail.phase == "completed"
     assert detail.outcome == "deployed"
+    assert detail.builder_image == ""
+    assert detail.builder_runtime == ""
     assert detail.logs.state == "available"
     assert detail.error is None
     assert captured[0]["payload"] == {
@@ -2358,6 +2382,8 @@ def test_unified_deployment_run_models_and_filters(monkeypatch):
             "created_at": "2026-07-19T12:00:00Z",
             "started_at": "2026-07-19T12:00:01Z",
             "finished_at": None,
+            "builder_image": "us-docker.pkg.dev/platform/static-builder:latest",
+            "builder_runtime": "nodejs22",
             "logs": {
                 "state": "available",
                 "url": f"/api/v1/deployment-runs/{run_uid}/logs/",
@@ -2377,6 +2403,8 @@ def test_unified_deployment_run_models_and_filters(monkeypatch):
 
     assert run.target.uid == target_uid
     assert run.steps == []
+    assert run.builder_image == "us-docker.pkg.dev/platform/static-builder:latest"
+    assert run.builder_runtime == "nodejs22"
     assert normalized == {
         "project_branch_uid": project_branch_uid,
         "target_type__in": ["resource_release", "static_site"],