Migrate to Dagger 1.0

.dagger/config.toml

@@ -0,0 +1,2 @@
+[modules.dang-sdk]
+source = "github.com/dagger/dang-sdk"

.dagger/migration-report.md

@@ -0,0 +1,10 @@
+# Migration Report
+
+## Root module requires explicit loading
+
+The root `dagger.json` is still a valid module, but it must be loaded explicitly.
+
+- **This works**: `dagger -m . call --help`
+- **This no longer works**: `dagger call --help`
+
+ACTION: If your scripts rely on implicit loading of the root module, change them to use explicit loading.

tests/log_output_toolchain_local/.dagger/config.toml

@@ -0,0 +1,7 @@
+[modules.pytest]
+source = "../../.."
+legacy-default-path = true
+# Optional: The source directory containing your Python project
+# settings.source = "./path"
+# Optional: A custom container with Python and uv installed.
+# settings.container = "alpine:latest"

tests/log_output_toolchain_local/.dagger/migration-report.md

@@ -0,0 +1,20 @@
+# Migration Report
+
+Dagger migrated `dagger.json`, but some old settings need a manual check.
+
+ACTION: Review each item below. If your project still relies on it, add the setting back manually.
+
+Legacy config: `dagger.json`
+
+## 1. `pytest` needs a manual check
+
+Dagger could not migrate this setting automatically: constructor arg "source" has 'defaultPath', which workspace settings do not support
+
+Original setting:
+
+```json
+{
+  "argument": "source",
+  "defaultPath": "/tests/log_output_toolchain_local"
+}
+```