Skip to content

Module content/en/docs/04/solution - Update dependency dagger/dagger to v0.18.14 #139

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
wants to merge 1 commit into from
Closed

Module content/en/docs/04/solution - Update dependency dagger/dagger to v0.18.14 #139

wants to merge 1 commit into from

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Jul 21, 2025

This PR contains the following updates:

Package Update Change
dagger/dagger patch v0.18.0 -> v0.18.14

Release Notes

dagger/dagger (dagger/dagger)

v0.18.14

Compare Source

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

What to do next?

v0.18.13

Compare Source

Added
Fixed
What to do next?

v0.18.12

Compare Source

Changed
  • Ignore default OrbStack CA cert for automatic installation by @​sipsma in https://github.com/dagger/dagger/pull/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
What to do next?

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 https://github.com/dagger/dagger/pull/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 https://github.com/dagger/dagger/pull/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 https://github.com/dagger/dagger/pull/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 https://github.com/dagger/dagger/pull/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 https://github.com/dagger/dagger/pull/10595

  • Propagate exit codes properly in shell by @​helderco in https://github.com/dagger/dagger/pull/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 https://github.com/dagger/dagger/pull/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 https://github.com/dagger/dagger/pull/10617

  • Added a new dots progress format, which is a much quieter alternative to plain suitable for use in CI by @​vito in https://github.com/dagger/dagger/pull/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
Fixed
What to do next?

v0.18.10

Compare Source

Added
Fixed
Dependencies
What to do next?

v0.18.9

Compare Source

Added
Changed
Fixed
What to do next?

v0.18.8

Compare Source

Fixed
What to do next?

v0.18.7

Compare Source

Fixed
Added
  • Add new optional parameters to Query.http by @​jedevc in https://github.com/dagger/dagger/pull/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?

v0.18.6

Compare Source

🔥 Breaking Changes

  • Cache URI-based secrets based on their plaintext value rather than the URI by @​sipsma in https://github.com/dagger/dagger/pull/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
Fixed
What to do next?

v0.18.5

Compare Source

Added
Fixed
What to do next?

v0.18.4

Compare Source

Fixed
Experimental
What to do next?

v0.18.3

Compare Source

Added
Fixed
Experimental
What to do next?

v0.18.2

Compare Source

Changed
Fixed
What to do next?

v0.18.1

Compare Source

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

What to do next?

Configuration

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

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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 has been generated by Renovate Bot.

@github-actions
Copy link
Contributor Author

github-actions bot commented Jul 28, 2025

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.

@chrira
Copy link
Member

chrira commented Sep 1, 2025

no module needed in solution

@chrira chrira closed this Sep 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@chrira