From df336203fa96680a3f8f4f19c956bea71ce40277 Mon Sep 17 00:00:00 2001
From: "dagger-codex[bot]" <dagger-codex[bot]@users.noreply.github.com>
Date: Fri, 22 May 2026 18:02:04 +0000
Subject: [PATCH] migrate to Dagger 1.0

---
 .dagger/config.toml         |  2 ++
 .dagger/migration-report.md | 28 ++++++++++++++++++++++++++++
 2 files changed, 30 insertions(+)
 create mode 100644 .dagger/config.toml
 create mode 100644 .dagger/migration-report.md

diff --git a/.dagger/config.toml b/.dagger/config.toml
new file mode 100644
index 0000000..9c12bf4
--- /dev/null
+++ b/.dagger/config.toml
@@ -0,0 +1,2 @@
+[modules.dang-sdk]
+source = "github.com/dagger/dang-sdk"
diff --git a/.dagger/migration-report.md b/.dagger/migration-report.md
new file mode 100644
index 0000000..33c9297
--- /dev/null
+++ b/.dagger/migration-report.md
@@ -0,0 +1,28 @@
+# 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.
+
+## mod-test requires explicit loading
+
+`mod-test` is still a valid module, but it must be loaded explicitly.
+
+- **This works**: `dagger -m mod-test call --help`
+- **This no longer works**: `cd mod-test; dagger call --help`
+
+ACTION: If your scripts rely on implicit loading of `mod-test`, change them to use explicit loading.
+
+## polyfill requires explicit loading
+
+`polyfill` is still a valid module, but it must be loaded explicitly.
+
+- **This works**: `dagger -m polyfill call --help`
+- **This no longer works**: `cd polyfill; dagger call --help`
+
+ACTION: If your scripts rely on implicit loading of `polyfill`, change them to use explicit loading.