Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: dagger/python-sdk
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: main
Choose a base ref
...
head repository: dagger/python-sdk
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: fix/workspace-root-module-source
Choose a head ref
Checking mergeability… Don’t worry, you can still create the pull request.
  • 1 commit
  • 2 files changed
  • 1 contributor

Commits on Jun 24, 2026

  1. Resolve SDK-managed module paths from workspace root 

    SDK-managed module entries store their module path relative to the workspace root. The helper APIs were passing that path directly to moduleSource, where a relative path is interpreted from the current working directory.

That breaks generate flows from nested workspace directories such as .dagger or .dagger/modules: .dagger/modules/myapp is resolved as .dagger/.dagger/modules/myapp, and generate fails while computing changeset paths.

Prefix SDK-managed paths with / before calling the sdk-sdk polyfill. The polyfill already treats /path as a workspace-root-relative module source, which matches the meaning of Mod.path. This updates generateAll and direct mod generate.

Signed-off-by: Guillaume de Rouville <guillaume@dagger.io>
    @grouville
    grouville committed Jun 24, 2026
    Configuration menu
    Copy the full SHA
    da2ed28 View commit details
    Browse the repository at this point in the history
Loading