Skip to content

Add Go module collection support#14

Draft
dagger-codex[bot] wants to merge 1 commit into
mainfrom
codex/go-collections
Draft

Add Go module collection support#14
dagger-codex[bot] wants to merge 1 commit into
mainfrom
codex/go-collections

Conversation

@dagger-codex
Copy link
Copy Markdown

@dagger-codex dagger-codex Bot commented Jun 1, 2026

Summary

  • change Go.modules to return a GoModules collection keyed by discovered module paths
  • keep Go.module as the direct lookup entry point for path/find-up behavior
  • update e2e expectations at the call sites that previously projected module paths from a list

Dependency

Draft until dagger/dagger#13299, or equivalent Dagger collection support, lands. This intentionally uses the new Dang @keys/@get directives and does not bump engineVersion to a release that does not contain them yet.

Verification

  • git diff --check
  • (cd helpers/go-includes && go test ./...)
  • dagger functions -m . currently reaches module loading and fails only because the installed engine reports @keys/@get as undeclared directives.

Signed-off-by: Solomon Hykes <solomon@dagger.io>
@dagger-codex dagger-codex Bot force-pushed the codex/go-collections branch from d24d89a to 50ad694 Compare June 1, 2026 21:54
@dagger-codex dagger-codex Bot changed the title Add collection support to the Go module Add Go module collection support Jun 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant