Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jul 12, 2024

Note: This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Update Change
dagger/dagger minor v0.11.9v0.19.9

Release Notes

dagger/dagger (dagger/dagger)

v0.19.9

Compare Source

Added
Fixed
  • fix TypeScript cache setting type error by @​TomChv in #​11539
  • Disable Git askpass prompts to prevent unexpected IDE credential dialogs (e.g., VS Code popups that appear even when credentials are already configured). Credentials still work via helpers or .netrc. For the rare case where no credentials are configured, Dagger now fails early with a clear error instead of triggering a subtle prompt that users sometimes miss by @​sleiner-v in #​11437
  • fix invalid overlay mount creation race condition by @​sipsma in #​11545
  • template in module name when initializing typescript modules by @​kpenfound in #​11551
  • fix incorrect file contents caching race condition bug by @​alexcb in #​11575
  • allow use of git module sources in Java SDK by @​eunomie in #​11570
  • improve determinism of generate Go code by @​kpenfound in #​11579
  • preserve shell exit codes in TUI mode by @​grouville in #​11586
  • ensure typescript SDK correctly uses lockfile in modules by @​TomChv in #​11592
  • fix chained calls across different depths in progress output by @​vito in #​11596
  • correct spelling in withAnnotation doc by @​hugginsio in #​11598
  • fix missing ignores of xattr copy failures by @​sipsma in #​11606
Contributors

Special thanks to our external contributors this release!

What to do next?

v0.19.8

Compare Source

Added
  • Optimize WithDirectory and WithFile to avoid copying file data on disk in more cases by @​sipsma in #​11497
    These APIs now avoid copying data on disk in all cases except when an owner, permission or timestamp is modified as part of the operation.
  • Add support for host environment variable expansion in .env files by @​alexcb in #​11442
  • Add VCS support for on-premises Azure DevOps by @​nilune in #​11500
  • Add ability to set app role mount path in Vault secret provider by @​nilune in #​11471
  • Add toolchain customization configuration by @​kpenfound in #​11480
  • Add configuration to ignore checks in a toolchain by @​kpenfound in #​11489
  • TypeScript SDK: Add live telemetry support by @​TomChv in #​11486
  • TypeScript SDK: Add tracing for tests using @otr/mocha-test lib by @​TomChv in #​11508
  • Add File.AsJSON() to simplify handling JSON file contents by @​suprjinx in #​11408
Changed
Fixed
Contributors

Special thanks to our external contributors this release!

What to do next?

v0.19.7

Compare Source

Added
Fixed
Contributors

Special thanks to our external contributors this release!

What to do next?

v0.19.6

Compare Source

Fixed
  • Fix dagger develop --recursive to use correct dependency name even when top-level module has a custom name for the dependency by @​sipsma in #​11365
  • Fix "failed to update rootfs: session not found" errors caused by incorrect use of stale client metadata by @​sipsma in #​11295
  • fix panic in filesync telemetry by @​ in #​11371
Contributors

Special thanks to our external contributors this release!

What to do next?

v0.19.5

Compare Source

Fixed
  • Significantly improve engine performance by reducing disk syncing and associated lock contention by @​sipsma in #​11336
  • Fixed directory+file not found errors when using cached function calls with contextual arguments involved by @​sipsma in #​11350
Contributors

Special thanks to our external contributors this release!

What to do next?

v0.19.4

Compare Source

Added
Fixed
Dependencies
Contributors

Special thanks to our external contributors this release!

What to do next?

v0.19.3

Compare Source

Added
  • allow modules to call their own functions through the engine (self calls) by @​eunomie in #​10584
  • Allow to raise errors using withError by @​eunomie in #​11222
    This is for instance really useful from inside self-chainable blocks (using with) where an error can't be returned.
  • New Changeset.isEmpty API by @​jedevc in #​11237
Fixed
Dependencies
What to do next?

v0.19.2

Compare Source

Fixed
  • Fixed engine crash when container sourced from private image was used with terminal or as a service (and was not already cached in the engine) by @​sipsma in #​11198
What to do next?

v0.19.1

Compare Source

Added
  • User defaults: persist any dagger function argument to .env by @​shykes in #​11034
    This feature allows user to save arguments to their dagger functions to a local file, instead of re-typing them at every call. This way, the sandboxing of functions is preserved without sacrificing end-user convenience.

    To use this feature, simply add variables to a local .env file reachable from your working directory. The format of the variables should be as follows:

v0.19.0

Compare Source

🔥 Breaking Changes
  • GitRepository.branch/GitRepository.tag/GitRepository.commit now only accept valid branches/tags/commits by @​jedevc in #​11038
  • GitRepository's withAuthToken and withAuthHeader are now no-ops by @​jedevc in #​11032
    Instead authentication should only be provided at the top-level git query, since it's now queried immediately.
  • Remove deprecated Host.setSecretFile method by @​jedevc in #​11115
    Use the file:// secret provider instead.
  • Remove LocalCache.keepBytes field by @​jedevc in #​11115
    Instead use the more specific LocalCache.reservedSpace, which it was an alias for.
  • Removed deprecated Container.build API by @​jedevc in #​11118
    Use Directory.dockerBuild instead.
Added
Fixed
What to do next?

v0.18.19

Compare Source

Added
  • New address API: a unified address to load containers, directories, secrets, etc by @​shykes in #​10770
  • New Changeset.export function to allow exporting changesets from the API by @​jedevc in #​11064
Fixed
  • Fixes a regression in Directory.withFiles which set the wrong path by @​jedevc in #​11087
What to do next?

v0.18.18

Compare Source

Added
  • Add new EnvFile type by @​shykes in #​10949
  • Mount client ~/.config/dagger/ca-certificates to engine by @​jedevc and @​matipan in #​11019
  • Add new Changeset type by @​vito in #​10946
  • Add APIs for "find-up search": search up the directory tree for a file or directory, and return its path by @​shykes in #​10956
    • Directory.findUp performs a find-up search in a directory snapshot
    • Host.findUp(): performs a find-up search in the host filesystem
Fixed
What to do next?

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?

v0.18.16

Compare Source

What to do next?

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!

What to do next?

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
  • 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?

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?

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?

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
What to do next?

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
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 #​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 #​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
  • 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?

v0.18.5

Compare Source

Added
  • New depth arg to GitRef.tree to control the depth of a clone by @​jedevc in #​9980
  • New GitRef.ref field for resolving the full ref string for a reference by @​jedevc in #​9980
Fixed
What to do next?

v0.18.4

Compare Source

Fixed
  • shell: fixed relative paths in Directory and File flags by @​helderco in #​10169
  • Fix re-use of LLM config from other concurrently running dagger sessions by @​sipsma in #​10184
  • Fix "session not found" errors when invoking modules by @​sipsma in #​10168
  • Fix errors using CurrentModule API during SDK module initialization by @​sipsma in #​10213
  • Fix caching of contextual directory args when multiple clients invoking the same function by @​sipsma in #​10187
  • Fix "client not found" errors when loading cached modules from private repos by @​sipsma in #​10223
  • Fix API authentication errors when calling llm.withModel from a module function by @​sipsma in #​10230
  • Fix "buildkit session not found" errors when calling .plaintext on a URI-based secret from a module w/ cache hit by @​sipsma in #​10223
  • Fixed error when setSecret provided empty plaintext value and passed between function calls by @​sipsma in #​10223
Experimental
What to do next?

v0.18.3

Compare Source

Added
Fixed
Experimental
What to do next?

v0.18.2

Compare Source

Changed
  • shell: skip CSV flag parsing when spreading with-exec positional arguments by @​helderco in #​10063
Fixed
What to do next?

v0.18.1

Compare Source

Added
  • New address API: a unified address to load containers, directories, secrets, etc by @​shykes in #​10770
  • New Changeset.export function to allow exporting changesets from the API by @​jedevc in #​11064
Fixed
  • Fixes a regression in Directory.withFiles which set the wrong path by @​jedevc in #​11087
What to do next?
  • Read

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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/dagger-dagger-0.x branch from dda7222 to c84af5b Compare July 18, 2024 22:49
@renovate renovate bot changed the title Update dependency dagger/dagger to v0.12.0 Update dependency dagger/dagger to v0.12.1 Jul 18, 2024
@renovate renovate bot force-pushed the renovate/dagger-dagger-0.x branch from c84af5b to 46da94d Compare July 22, 2024 21:32
@renovate renovate bot changed the title Update dependency dagger/dagger to v0.12.1 Update dependency dagger/dagger to v0.12.2 Jul 22, 2024
@renovate renovate bot force-pushed the renovate/dagger-dagger-0.x branch from 46da94d to 2d2454b Compare July 25, 2024 19:15
@renovate renovate bot changed the title Update dependency dagger/dagger to v0.12.2 Update dependency dagger/dagger to v0.12.3 Jul 25, 2024
@renovate renovate bot force-pushed the renovate/dagger-dagger-0.x branch from 2d2454b to 8f8eb0b Compare August 2, 2024 13:11
@renovate renovate bot changed the title Update dependency dagger/dagger to v0.12.3 Update dependency dagger/dagger to v0.12.4 Aug 2, 2024
@renovate renovate bot force-pushed the renovate/dagger-dagger-0.x branch from 8f8eb0b to 0fd0c03 Compare August 7, 2024 14:44
@renovate renovate bot force-pushed the renovate/dagger-dagger-0.x branch from 0fd0c03 to f6aa0b6 Compare August 15, 2024 15:19
@renovate renovate bot changed the title Update dependency dagger/dagger to v0.12.4 Update dependency dagger/dagger to v0.12.5 Aug 15, 2024
@renovate renovate bot force-pushed the renovate/dagger-dagger-0.x branch from f6aa0b6 to d1b000d Compare August 30, 2024 12:19
@renovate renovate bot changed the title Update dependency dagger/dagger to v0.12.5 Update dependency dagger/dagger to v0.12.6 Aug 30, 2024
@renovate renovate bot force-pushed the renovate/dagger-dagger-0.x branch from d1b000d to 89c9d45 Compare September 2, 2024 15:35
@renovate renovate bot changed the title Update dependency dagger/dagger to v0.12.6 Update dependency dagger/dagger to v0.12.7 Sep 2, 2024
@renovate renovate bot force-pushed the renovate/dagger-dagger-0.x branch from 89c9d45 to f23b8d8 Compare September 11, 2024 16:52
@renovate renovate bot changed the title Update dependency dagger/dagger to v0.12.7 Update dependency dagger/dagger to v0.13.0 Sep 11, 2024
@renovate renovate bot force-pushed the renovate/dagger-dagger-0.x branch from f23b8d8 to 97b943f Compare September 18, 2024 21:52
@renovate renovate bot changed the title Update dependency dagger/dagger to v0.13.0 Update dependency dagger/dagger to v0.13.1 Sep 18, 2024
@renovate renovate bot force-pushed the renovate/dagger-dagger-0.x branch from 97b943f to 8bb4c45 Compare September 20, 2024 18:44
@renovate renovate bot changed the title Update dependency dagger/dagger to v0.13.1 Update dependency dagger/dagger to v0.13.2 Sep 20, 2024
@renovate renovate bot force-pushed the renovate/dagger-dagger-0.x branch from 8bb4c45 to a93226d Compare September 21, 2024 01:28
@renovate renovate bot changed the title Update dependency dagger/dagger to v0.13.2 Update dependency dagger/dagger to v0.13.3 Sep 21, 2024
@renovate renovate bot changed the title Update dependency dagger/dagger to v0.13.3 Update dependency dagger/dagger to v0.13.4 Oct 9, 2024
@renovate renovate bot force-pushed the renovate/dagger-dagger-0.x branch 2 times, most recently from 2c7148c to 3298d83 Compare October 11, 2024 01:11
@renovate renovate bot changed the title Update dependency dagger/dagger to v0.13.4 Update dependency dagger/dagger to v0.13.5 Oct 11, 2024
@renovate renovate bot changed the title Update dependency dagger/dagger to v0.13.5 Update dependency dagger/dagger to v0.13.6 Oct 25, 2024
@renovate renovate bot force-pushed the renovate/dagger-dagger-0.x branch from 3298d83 to dd68756 Compare October 25, 2024 14:12
@renovate renovate bot changed the title Update dependency dagger/dagger to v0.18.12 Update dependency dagger/dagger to v0.18.13 Jul 18, 2025
@renovate renovate bot force-pushed the renovate/dagger-dagger-0.x branch from 829fcec to deee288 Compare July 19, 2025 01:36
@renovate renovate bot changed the title Update dependency dagger/dagger to v0.18.13 Update dependency dagger/dagger to v0.18.14 Jul 19, 2025
@renovate renovate bot force-pushed the renovate/dagger-dagger-0.x branch from deee288 to afbdddd Compare August 18, 2025 22:38
@renovate renovate bot changed the title Update dependency dagger/dagger to v0.18.14 Update dependency dagger/dagger to v0.18.15 Aug 18, 2025
@renovate renovate bot force-pushed the renovate/dagger-dagger-0.x branch from afbdddd to 3351643 Compare August 19, 2025 22:47
@renovate renovate bot changed the title Update dependency dagger/dagger to v0.18.15 Update dependency dagger/dagger to v0.18.16 Aug 19, 2025
@renovate renovate bot force-pushed the renovate/dagger-dagger-0.x branch from 3351643 to 3336c05 Compare September 19, 2025 16:03
@renovate renovate bot changed the title Update dependency dagger/dagger to v0.18.16 Update dependency dagger/dagger to v0.18.19 Sep 19, 2025
@renovate renovate bot force-pushed the renovate/dagger-dagger-0.x branch from 3336c05 to ecefbbe Compare September 30, 2025 15:07
@renovate renovate bot changed the title Update dependency dagger/dagger to v0.18.19 Update dependency dagger/dagger to v0.19.0 Sep 30, 2025
@renovate renovate bot force-pushed the renovate/dagger-dagger-0.x branch from ecefbbe to cd3613b Compare October 8, 2025 04:43
@renovate renovate bot changed the title Update dependency dagger/dagger to v0.19.0 Update dependency dagger/dagger to v0.19.1 Oct 8, 2025
@renovate renovate bot force-pushed the renovate/dagger-dagger-0.x branch from cd3613b to 42c99fa Compare October 8, 2025 17:41
@renovate renovate bot changed the title Update dependency dagger/dagger to v0.19.1 Update dependency dagger/dagger to v0.19.2 Oct 8, 2025
@renovate renovate bot force-pushed the renovate/dagger-dagger-0.x branch from 42c99fa to b77983c Compare October 23, 2025 23:11
@renovate renovate bot changed the title Update dependency dagger/dagger to v0.19.2 Update dependency dagger/dagger to v0.19.3 Oct 23, 2025
@renovate renovate bot force-pushed the renovate/dagger-dagger-0.x branch from b77983c to 64bb30e Compare October 31, 2025 00:12
@renovate renovate bot changed the title Update dependency dagger/dagger to v0.19.3 Update dependency dagger/dagger to v0.19.4 Oct 31, 2025
@renovate renovate bot force-pushed the renovate/dagger-dagger-0.x branch from 64bb30e to 4a02ca8 Compare November 5, 2025 20:53
@renovate renovate bot changed the title Update dependency dagger/dagger to v0.19.4 Update dependency dagger/dagger to v0.19.5 Nov 5, 2025
@renovate renovate bot force-pushed the renovate/dagger-dagger-0.x branch from 4a02ca8 to 5debe0a Compare November 7, 2025 18:10
@renovate renovate bot changed the title Update dependency dagger/dagger to v0.19.5 Update dependency dagger/dagger to v0.19.6 Nov 7, 2025
@renovate renovate bot force-pushed the renovate/dagger-dagger-0.x branch from 5debe0a to cee065c Compare November 21, 2025 01:31
@renovate renovate bot changed the title Update dependency dagger/dagger to v0.19.6 Update dependency dagger/dagger to v0.19.7 Nov 21, 2025
@renovate renovate bot force-pushed the renovate/dagger-dagger-0.x branch from cee065c to 8813f21 Compare December 5, 2025 21:25
@renovate renovate bot changed the title Update dependency dagger/dagger to v0.19.7 Update dependency dagger/dagger to v0.19.8 Dec 5, 2025
@renovate renovate bot force-pushed the renovate/dagger-dagger-0.x branch from 8813f21 to 1a6bc4c Compare January 8, 2026 02:07
@renovate renovate bot changed the title Update dependency dagger/dagger to v0.19.8 Update dependency dagger/dagger to v0.19.9 Jan 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant