chore(deps): update dependency dagger/dagger to v0.18.17

[renovate]

Coming soon: The Renovate bot (GitHub App) will be renamed to Mend. PRs from Renovate will soon appear from 'Mend'. Learn more here.

This PR contains the following updates:

Package	Update	Change
dagger/dagger	patch	0.18.5 -> 0.18.17

---

Release Notes

dagger/dagger (dagger/dagger)

v0.18.17

Compare Source

🔥 Breaking Changes

• Automatically apply .gitignore patterns on directory loading for module call by @​TomChv and @​jedevc in #​10883 \

  • Apply when loading contextual directory argument.
  • Apply when a directory is sent as an argument to a module function.
  • Apply when a local module is loaded.

  Add NoGitAutoIgnore argument to Host.Directory to disable this behavior.

Added

• New Host.containerImage API to load images from the host container image store by @​jedevc in #​10810
• New Container.combined API to get both standard output and standard error after withExec by @​eunomie #​10924
• New GitRepository.url API to get the fully resolved URL of a git repository by @​jedevc in #​10959
• New assorted filesystem APIs for searching/replacing by @​vito in #​10937
• Allow entering terminals from the TUI for Containers, Directorys and running Services by @​jedevc in #​10867
• Allow reading git credentials from client's .netrc file by @​jedevc in #​10957

Fixed

• git now automatically determines the protocol when using a scheme-less URL (instead of defaulting to https://) by @​jedevc in #​10960
• Ensure HTTP auth is propagated to git submodules by @​grouville in #​10855
• Detect more telemetry from github environment by @​jedevc in ...

What to do next?

• Read the documentation
• Join our Discord server
• Follow us on Twitter

v0.18.16

Compare Source

What to do next?

• Read the documentation
• Join our Discord server
• Follow us on Twitter

v0.18.15

Compare Source

Added

• New container.Exists and directory.Exists API for testing if a file exists, and optionally type (e.g. file or directory) by @​alexcb in #​10449
• Allow starting dagger engines in alternative container runtimes, including: by @​jedevc in #​10714 \
  • Apple's container
  • podman
  • nerdctl
  • finch
• cli: add support for passing build arguments to a docker build by @​helderco in #​10779
• Added new gitRef.commonAncestor API to find the common ancestor between two references by @​jedevc in #​10849

Fixed

• Prompt mode now handles interrupts more gracefully, continuing from where the agent left off rather than completely forgetting the prompt by @​vito in #​10765
• Switching to prompt mode now properly initializes and displays the model, logging an error if initialization fails by @​vito in #​10765
• shell: Fixed passing objects on http and git stdlib commands by @​helderco in #​10845
• shell: fix state mutability issue when chaining function by @​helderco in #​10857
• Ensure that introspection methods support includeDeprecated arg by @​jedevc in #​10889

Contributors

Special thanks to our external contributors this release!

• @​alexcb

What to do next?

• Read the documentation
• Join our Discord server
• Follow us on Twitter

v0.18.14

Compare Source

Fixed a regression causing the LLM to see malformed non-string scalar responses.

What to do next?

• Read the documentation
• Join our Discord server
• Follow us on Twitter

v0.18.13

Compare Source

Added

• New Container.exportImage API to load images to host container image store by @​jedevc in #​10662
• New GitRepository.latestVersion field to get a git ref of the latest semver tag by @​jedevc in #​10679

Fixed

• WithSymlink now returns "file exists" error when attempting to overwrite an existing symlink by @​alexcb in #​10664
• Fix dockerfile builds with optional secrets by @​jedevc in #​10675
• Module import resolution now supports repository paths containing tilde characters (~), commonly used in Bitbucket Server for user-scoped repositories (e.g., extranet.example.com/bitbucket/scm/~user/repo.git) by @​grouville in #​10692
• Fix memory leak in engine by @​sipsma in #​10708

What to do next?

• Read the documentation
• Join our Discord server
• Follow us on Twitter

v0.18.12

Compare Source

Changed

• Ignore default OrbStack CA cert for automatic installation by @​sipsma in #​10648
  OrbStack users were by default ending up with a custom CA in their engine and automatically installed in each container, adding overhead. We now ignore that CA cert by default to improve performance in the default case.

Fixed

• Fixed a deadlock caused by concurrent schema introspection and modification by @​vito in #​10643
• Fixed an issue where old dagger versions would create an invalid typedef when the enum name equaled the enum value by @​jedevc in #​10647
• Fixed an issue where an issue where --help for enum default values was incorrect @​jedevc in #​10647

What to do next?

• Read the documentation
• Join our Discord server
• Follow us on Twitter

v0.18.11

Compare Source

🔥 Breaking Changes

• The dagger CLI and shell must now be passed enums by name (instead of by
  value) for SDKs that support enum members (see SDK-specific release notes).
• Default arguments are now validated on registration by @​jedevc in #​9518
  This may break loading modules (including in compat mode) that were
  previously setting enum default values in function signatures, if those values
  weren't valid - these would only trigger an error on calling that function,
  while now it's triggered during module initialization.
• Remove namespace argument from CacheVolume by @​sipsma in #​10586
  This arg was only ever meant for internal usage within the API's
  implementation, but previously couldn't be hidden from the public API. Now it
  is properly internal-only and thus not accessible to external clients. Any use
  of the arg should just be removed.
• Changed incorrect sweep engine option name to sweepSize by @​jedevc in #​10560
  This option was previously incorrectly named - the docs were correct, but the
  code was not properly updated.

Added

• New top-level cloud API for getting information about the dagger cloud session by @​marcosnils in #​10580
  This includes the cloud.traceURL field for getting the current trace URL.

• Allow --no-mod/-M flag in more places to disable automatic module loading by @​jedevc in #​10595

• Propagate exit codes properly in shell by @​helderco in #​10438
  The .exit builtin was added.

  The .wait builtin now accepts a list of job ids to wait for. For example:

  container | from alpine | with-exec false | stdout &
  job1=$!
  container | from alpine | with-exec echo ok | stdout &
  job2=$!
  .echo ".wait $job1 $job2"
  .wait $job1 $job2

  The above example should exit with status code 1 because .wait returns
  the exit of the first command that failed. This is different from Bash
  which returns the exit status of the last command in the list, even if
  it succeeded when others have failed.

• Add httpAuthUsername parameter to git to allow basic auth with usernames by @​grouville in #​10605
  Additionally this field is populated from the client's git credential helper,
  similarly to passwords.

• You can now set $DAGGER_PROGRESS to configure your preferred progress format globally, instead of passing the --progress flag every time by @​vito in #​10617

• Added a new dots progress format, which is a much quieter alternative to plain suitable for use in CI by @​vito in #​10617
  This format focuses on printing logs and reduces everything else to just
  green dots and red Xes for success/failure, similar to test runners like RSpec.
  Demo

Changed

• shell: use main object description as the fallback in .help <module> by @​helderco in #​10487
• When a service fails to start, the API will now return a proper ExecError so you can see the stdout/stderr and exit code programmatically by @​vito in #​10585

Fixed

• Fixed high engine memory usage exacerbated by high log volume and composing multiple modules by @​vito in #​10578
  In one scenario this reduced heap usage from 14GB to 7GB.
• Schema introspection is now cached, as long as the schema doesn't change by @​vito in #​10579
  In the same scenario as the high log volume fix, this further reduced heap usage from 7GB to 1.4GB.
• shell: fixed arguments with pipelines to interpreter builtins not being resolved by @​helderco in #​10635
• Fixed the plain progress format being way more verbose than intended by @​vito in #​10636
• Fixed Directory.withSymlink accidentally escaping from the selected sub-directory by @​alexcb in #​10563

What to do next?

• Read the documentation
• Join our Discord server
• Follow us on Twitter

v0.18.10

Compare Source

Added

• Improved TUI progress visualizer by @​vito in #​10468

• Added E hotkey in TUI for -E/--no-exit at runtime by @​vito in #​10511

• Add support for using engine-wide default GC policy when triggering manual local cache prunes by @​sipsma in #​10505
  The manual prune API now supports an optional arg to enable honoring the engine-wide default automatic GC configuration. e.g.

  dagger core engine local-cache prune --use-default-policy
  

• New container.WithSymlink and directory.WithSymlink API for creating symbolic links by @​alexcb in #​10435

• Unbundle the SDK interface to support partial implementation by @​TomChv in #​10525
  When you implement a custom SDK, you can now choose to just implement part of the SDK interface depending on your needs.
  That means:

  • dagger develop no longer fails if your SDK just implement the Runtime interface, it will simply not call Codegen if not defined.
  • dagger call and dagger functions give a clear error message if it's not supported by the SDK.

  See #​7707 for more information.

Fixed

• Fix occasional "no such file or directory" errors during filesync caused by concurrent syncs by @​sipsma in #​10541

Dependencies

• Update go to 1.24.4 by @​jedevc in #​10553

What to do next?

• Read the documentation
• Join our Discord server
• Follow us on Twitter

v0.18.9

Compare Source

Added

• New gc.sweepSize setting for engine.json by @​jedevc in #​10420
  This setting allows controlling how much data to clear in a single GC sweep.

Changed

• Add noCache arg to Host.directory to auto reload contextual directories in persistent shell/prompt sessions by @​cwlbraa in #​10342

Fixed

• shell: fixed _ prefix not being reserved for interpreter builtins by @​helderco in #​10452
• shell: fixed parsing arguments with list of objects by @​helderco in #​10441

What to do next?

• Read the documentation
• Join our Discord server
• Follow us on Twitter

v0.18.8

Compare Source

Fixed

• llm: static tool scheme by @​vito in #​10366

What to do next?

• Read the documentation
• Join our Discord server
• Follow us on Twitter

v0.18.7

Compare Source

Fixed

• Ensure git API calls consistently respect proxy settings by @​jedevc in #​10352
• Lazily load LLM API keys by @​cwlbraa in #​10357

Added

• Add new optional parameters to Query.http by @​jedevc in #​10317
  • name allows overriding the filename to download
  • permissions allows setting the permissions on the resulting file
  • authHeader allows passing a secret in the Authorization HTTP header

What to do next?

• Read the documentation
• Join our Discord server
• Follow us on Twitter

v0.18.6

Compare Source

🔥 Breaking Changes

• Cache URI-based secrets based on their plaintext value rather than the URI by @​sipsma in #​10311
  Previously, the "cache key" for URI-based secrets (e.g. env://FOO, file:///some/path, etc.) was the URI string. This meant that operations including the secret (e.g. as an environment variable in a Container) would be cached based on the URI value. If two secrets from different clients had the same URI but different plaintext values, cache for operations that include them would be shared.

  In many cases, even when URIs were the same, the plaintext of secrets could be meaningfully different, which made this behavior surprising and lead to unexpected results.

  Now, URI-based secrets are cached based on secure hashes of their plaintext value. Two secrets that have the same URI but different plaintext values will be cached separately, and operations that include them will not share cache.

  However, there are cases where users do want secrets with different plaintexts to share cache, e.g. secrets that rotate in plaintext value frequently but aren't meaningfully different and thus shouldn't bust the cache of operations that include them.

  To continue supporting those use cases, there is a new optional cacheKey argument to Secret that can be used to specify a custom cache key. If provided, the cache key will be used instead of the default plaintext-based cache key, allowing any secrets sharing that cache-key to be cached together.

  SDKs can provide this as an optional argument to the Secret constructor. Other example usages:

  dagger shell:

  • dagger shell -c "some-function --secret-arg $(secret env://FOO --cache-key my-cache-key)"

  dagger call (supports a special syntax that sets the cache key via a query param in the URI):

  • dagger call some-function --secret-arg env://FOO?cacheKey=my-cache-key

Added

• New GitRepository.branches API by @​jedevc in #​10250
• New File top-level field added to allow easier creation of File objects by @​jedevc in #​10290

Fixed

• GitRepository.tags patterns arg is now respected for local git repositories by @​jedevc in #​10250
• Return an error when a function argument conflicts with a persistent flag in dagger call by @​helderco in #​10305
• Fix "failed to return error" and "failed to emit telemetry" errors when two identical functions execute at the same time and one client cancels the request by @​sipsma in #​10264
• Fix panic in vault secret provider when path exists but secret doesn't by @​sipsma in #​10311
• Fix panic when using Container.build with a Dockerfile that is FROM scratch by @​sipsma in #​10332

What to do next?

• Read the documentation
• Join our Discord server
• Follow us on Twitter

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Never, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.