chore(deps): update dependency dagger to v0.15.3 #201
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/dagger-0.x
branch
2 times, most recently
from
6e2116d to
1fd8999
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/dagger-0.x
branch
from
1fd8999 to
c503162
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/dagger-0.x
branch
from
c503162 to
4e8d71d
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/dagger-0.x
branch
from
4e8d71d to
a3f9e10
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/dagger-0.x
branch
from
a3f9e10 to
d57f0ec
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/dagger-0.x
branch
from
d57f0ec to
1c80c80
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/dagger-0.x
branch
2 times, most recently
from
f966c9c to
18acac0
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/dagger-0.x
branch
from
18acac0 to
c8f0372
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/dagger-0.x
branch
from
c8f0372 to
4fae54f
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/dagger-0.x
branch
from
4fae54f to
068e06d
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/dagger-0.x
branch
from
068e06d to
5c054a5
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/dagger-0.x
branch
from
5c054a5 to
c568116
Compare
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/dagger-0.x
branch
from
c568116 to
c259bd7
Compare
renovate
bot
force-pushed
the
renovate/dagger-0.x
branch
from
c259bd7 to
626e8e0
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/dagger-0.x
branch
from
cd6d0f5 to
617ec68
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/dagger-0.x
branch
from
617ec68 to
9d17888
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/dagger-0.x
branch
from
9d17888 to
0b15314
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/dagger-0.x
branch
from
0b15314 to
baaa689
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/dagger-0.x
branch
from
baaa689 to
bd53ede
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/dagger-0.x
branch
from
bd53ede to
4bef113
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/dagger-0.x
branch
from
4bef113 to
3ed41ee
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/dagger-0.x
branch
from
3ed41ee to
4b31fa1
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/dagger-0.x
branch
from
4b31fa1 to
c8c2f51
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/dagger-0.x
branch
from
c8c2f51 to
0b9f5f4
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/dagger-0.x
branch
from
0b9f5f4 to
d2ef30d
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/dagger-0.x
branch
from
d2ef30d to
efb69e8
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/dagger-0.x
branch
from
efb69e8 to
e6f298d
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/dagger-0.x
branch
from
e6f298d to
a795f5c
Compare
renovate
bot
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v0.5.1->v0.15.3Release Notes
dagger/dagger (dagger)
v0.15.3Compare Source
Added
Note: the precision of float is limited to float64 inside the engine.
Fixed
Container.WithFilesby @jedevc in https://github.com/dagger/dagger/pull/9457Dependencies
What to do next?
v0.15.2Compare Source
Added
dagger updatecommand to update dependencies indagger.jsonby @rajatjindal in https://github.com/dagger/dagger/pull/8839$schemaproperty indagger.jsonby @JacobLey in https://github.com/dagger/dagger/pull/9069Changed
CacheVolumesare now namespaced between different modules by @rajatjindal in https://github.com/dagger/dagger/pull/8724CACHEDoperations for--progress=plainoutput by @marcosnils in https://github.com/dagger/dagger/pull/9344Fixed
AsServiceby @marcosnils in https://github.com/dagger/dagger/pull/9247Container.terminalby @jedevc in https://github.com/dagger/dagger/pull/9338Container.upbehaves as identically as possible toContainer.AsService.upby @jedevc in https://github.com/dagger/dagger/pull/9231dagger installalways inserts dependencies in the right order by @jedevc in https://github.com/dagger/dagger/pull/9052What to do next?
v0.15.1Compare Source
Fixed
What to do next?
v0.15.0Compare Source
🔥 Breaking Changes
Container.asServicenow uses the command specified bywithDefaultArgsinstead of the lastwithExeccommand by @rajatjindal in https://github.com/dagger/dagger/pull/8865Users can override the args by providing the
argsoption toasService.They can also configure the container to use the container entrypoint by using
useEntrypointoption.Added
Better TUI errors, new cached/pending states, duration accounting and fewer spans by @vito in https://github.com/dagger/dagger/pull/8442
Custom dagger
engine.jsonconfig file by @jedevc in https://github.com/dagger/dagger/pull/8800This new config file format is intended to eventually replace the old
buildkit-style
engine.tomlfile that's currently used for configuration.This file can be either mounted directly into a manually started engine at
/etc/dagger/engine.toml, or it will automatically mounted from theuser's
~/.config/dagger/engine.jsonwhen the engine is started.Filesync performance is improved by @sipsma in https://github.com/dagger/dagger/pull/8818
The engine now re-uses previously loaded data more reliably and in more
cases, which speeds up repeated reloads of the same or similar (i.e.
overlapping data).
Uncached filesyncs of large amounts of data is also faster and uses less
memory in the engine.
Added
dagger uninstallcommand to remove a dependency by @rajatjindal in https://github.com/dagger/dagger/pull/8745Added memory and network telemetry for execs by @cwlbraa in https://github.com/dagger/dagger/pull/8880 https://github.com/dagger/dagger/pull/8902
Added
DAGGER_LEAVE_OLD_ENGINEenvironment variable to optionally prevent removal of old engine containers during upgrades by devin in https://github.com/dagger/dagger/pull/8195Fixed
Directory.terminalAPI works now by @sipsma in https://github.com/dagger/dagger/pull/8952Container.withExecexpectto catch exit code 128 by @jedevc in https://github.com/dagger/dagger/pull/9027Directory.digestby @jedevc in https://github.com/dagger/dagger/pull/8946What to do next?
v0.14.0Compare Source
🔥 Breaking Changes
dagger-enginecore GraphQL query toengineby @marcosnils in https://github.com/dagger/dagger/pull/8568Container.withFocusandContainer.withoutFocusby @jedevc in https://github.com/dagger/dagger/pull/8647Added
Fixed
What to do next?
v0.13.7Compare Source
Added
expectarg forContainer.withExecby @jedevc in https://github.com/dagger/dagger/pull/8466This enum arg allows specifying valid return statuses for which the command
can return without failing immediately.
Container.exitCodefield to get the exit code of the lastwithExecby @jedevc in https://github.com/dagger/dagger/pull/8466Changed
The new policies attempt to co-operate with other applications using the disk
and will adjust its cache usage accordingly.
Previously, when a function chain in
dagger callended in an object, we'dprint all functions that return a simple value and don't have any arguments.
Now, only object fields will be included, not all functions.
Fixed
withExecs using theExperimentalPrivilegedNestingflag by @sipsma in https://github.com/dagger/dagger/pull/8776What to do next?
v0.13.6Compare Source
Added
Show metrics for execs in TUI by @sipsma in https://github.com/dagger/dagger/pull/8506
The engine now supports collecting metrics from individual execs and publishing them as OTel metrics.
To start, just disk read/write byte totals and CPU/IO pressure time are supported, but more like memory/network/etc, will be added soon.
Currently, metrics will be displayed in the TUI at verbosity level 4 (
-vvv).Changed
dagger initdefaults to use.daggerfolder during if current directory.is not empty by @rajatjindal in https://github.com/dagger/dagger/pull/8557dagger installnow preserves the original source input, and tracks a separatepinfield for the exact remote commit by @jedevc in https://github.com/dagger/dagger/pull/8587Fixed
Allow custom enums that include ambiguous names (such as
true/false) by @jedevc in https://github.com/dagger/dagger/pull/8682Optimize
Container.fromfor image refs with digests by @sipsma in https://github.com/dagger/dagger/pull/8736Previously, if
Container.fromwas given an image ref with a digest and that image already existed in the local cache, the engine would still waste time resolving metadata over the network from the registry.Now, if a digested image ref already exists locally, the network requests are skipped entirely.
Allow cloning hidden commits that are not fetched as part of a normal clone by @jedevc in https://github.com/dagger/dagger/pull/8747
For example,
refs/pull/<pr>/head, orrefs/pull/<pr>/merge.Speed up fully cached initialize time by caching more internal SDK operations by @sipsma in https://github.com/dagger/dagger/pull/8735
Dagger wasn't caching as many SDK operations as it could. With this change Dagger's own CI modules initialize ~1s faster when fully cached.
Speed up initialization of modules with lots of dependencies using the Go SDK in engines with no cache by @sipsma in https://github.com/dagger/dagger/pull/8761
Various dependencies of Go SDK modules are now pre-cached in the engine image, which avoids significant CPU pressure when building Go SDK modules in parallel with no cache.
The engine image size increase is expected to be offset by these improvements.
What to do next?
v0.13.5Compare Source
Fixed
MarshalJSONerror ingitAPI when called by older module versions by @jedevc in https://github.com/dagger/dagger/pull/8667What to do next?
v0.13.4Compare Source
🔥 Breaking Changes
.gitdirectory by @jedevc in https://github.com/dagger/dagger/pull/8318This can be disabled with
tree's newdiscardGitDiroption. Modules witholder
engineVersions will keep the old behavior.git'skeepGitDirargument by @jedevc in https://github.com/dagger/dagger/pull/8318Added
Services can now be given an explicit hostname via
Service.withHostnameby @vito in https://github.com/dagger/dagger/pull/8641Previously, you could only express a DAG of services, because each service
hostname was derived from the service's configuration, and changing a service
to point to another service would inherently change that service's
configuration.
Now you can set your own hostnames ahead of time, tell your services about
each other's hostnames, and start they manually.
Services with custom hostnames are namespaced to the module that starts them, to prevent conflicts.
Allow expanding environment variables in more
Containerfunctions by @rajatjindal in https://github.com/dagger/dagger/pull/8427Apply
ignorefunction parameter metadata on Directory passed from the CLI by @TomChv in https://github.com/dagger/dagger/pull/8436This extends the usage of
ignoreto not only dir loaded withdefaultPathbut directory passed as function's param from the CLI.
Note: ignore patterns are not applied for module to module calls.
Enabled
Container.withMountedTempsize configuration by @cwlbraa in https://github.com/dagger/dagger/pull/8652Add
noInitoption toContainer.withExecto support disabling automatic init process by @sipsma in https://github.com/dagger/dagger/pull/8656Use cases that strictly require the user exec is PID 1 of the container are
now supported by setting
noInitto true.Fixed
ExportandAsTarballby @jedevc in https://github.com/dagger/dagger/pull/8543What to do next?
v0.13.3Compare Source
Fixed
What to do next?
v0.13.2Compare Source
Added
Container.upAPI by @rajatjindal in https://github.com/dagger/dagger/pull/8479This is an alias to
.AsService().Up().Fixed
What to do next?
v0.13.1Compare Source
Added
Container.withoutFilesandDirectory.withoutFilesby @jedevc in https://github.com/dagger/dagger/pull/8216Container.withAnnotationto set OCI annotations by @aluzzardi in https://github.com/dagger/dagger/pull/8409ignorecombined withdefaultPathnow works if the module is fetch from git instead of local by @TomChv in https://github.com/dagger/dagger/pull/8430Directory.withoutFilesandContainer.withoutFilescore APIs by @jedevc in https://github.com/dagger/dagger/pull/8216These can be used to remove multiple files from a filesystem in one call.
Fixed
Directory.digeston scratch directory by @jedevc in https://github.com/dagger/dagger/pull/8445dagger.Secretby @helderco in https://github.com/dagger/dagger/pull/8468What to do next?
v0.13.0Compare Source
🔥 Breaking Changes
Container.withExec'sskipEntrypointargument - this is now the default (seeuseEntrypoint)pipeline,Container.pipelineandDirectory.pipelineGitModuleSource.cloneURL(seeGitModuleSource.cloneRef)Added
Directory.digestandModuleSource.digestfields by @jedevc in https://github.com/dagger/dagger/pull/8282These fields mirror the behavior of the
File.digestfield, computing aunique cryptographic digest over the contents of the object.
--no-exit/-Eso you can poke around after the call completes by @vito in https://github.com/dagger/dagger/pull/8389Changed
Also, the url will be printed only for a subset of dagger commands to reduce noise.
Connecting to a distant remote engine could otherwise fail if it was not reachable in 1s.
Fixed
Previously, if a field access was made immediately after the default constructor was called, then the access would fail.
Carriage returns could previously render weirdly in the output, displaying empty lines, and similar visual glitches.
Platformflag by @helderco in https://github.com/dagger/dagger/pull/8360What to do next?
v0.12.7Compare Source
Fixed
Git.tagsURL parsing consistent withGit.treeby @jedevc in https://github.com/dagger/dagger/pull/8298phporelixirsdk by @rajatjindal in https://github.com/dagger/dagger/pull/8297What to do next?
v0.12.6Compare Source
Added
This allows accessing their own source directory, without needing to
explicitly pass directories around.
--interactive-commandfor overriding the default command used in interactive mode by @samalba in https://github.com/dagger/dagger/pull/8171Fixed
The file-not-found errors were previously silently ignored for the top-level
module passed in the CLI.
failed to get repo HEADCLI error by @jedevc in https://github.com/dagger/dagger/pull/8189Container.withExecafter usingwithMountedTemporwithMountedSecretby @jedevc in https://github.com/dagger/dagger/pull/8180What to do next?
v0.12.5Compare Source
Added
cli: allow calling core functions directly by @helderco in https://github.com/dagger/dagger/pull/7310
Usage:
dagger core <function>Example:
dagger core container from --address=alpine terminalWorks the same as
dagger call, but instead of loading a user module,it only uses functions from the core API.
Run
dagger core --helpfor available functions.Note that this command is experimental and the DX for calling core functions
in the CLI may change in the future.
New SDK aliases for
elixirandphpby @jedevc in https://github.com/dagger/dagger/pull/8067SDKs with experimental module support (elixir and php) can now be accessed
using
--sdk=<sdk>(such as--sdk=elixirand--sdk=phprespectively)instead of the full form
--sdk=github.com/dagger/dagger/sdk/<sdk>@​<version>.Add
File.digestmethod by @TomChv in https://github.com/dagger/dagger/pull/8114This method provides an efficient way to compute a file's digest, which
unlock optimized file comparison or check for file changes.
Bundle CLI in the Engine image so that both parts of Dagger (CLI+Engine) ship as a single artefact by @gerhard in https://github.com/dagger/dagger/pull/8147
Changed
Fixed
Directory.globto correctly handle globs with subdir prefixes by @jedevc in https://github.com/dagger/dagger/pull/8110Previously, attempting to glob with a prefix subdir in a pattern like
<subdir>/*would not match any files. This should now be fixed, and filesin
<subdir>will now be correctly matched.failed to collect IDs from parent fieldserror when module objects contain fields with nil values by @jedevc/@sipsma in https://github.com/dagger/dagger/pull/8132Previously, modules would fail to launch if they declared a constructor that
contained a reference to a type from it's own module in it's args.
Previously, function calls that defined an optional argument would not be
callable.
What to do next?
v0.12.4Compare Source
Changed
pipelineAPIs by @jedevc in https://github.com/dagger/dagger/pull/8064These operations have been no-ops since v0.11.0, and will be removed in v0.13.0.
Fixed
terminalprompt with debian-based images by @vmaffet in https://github.com/dagger/dagger/pull/7960--progress=plainoutput by @jedevc in https://github.com/dagger/dagger/pull/7956Our support for Azure refs was broken on monorepos. We special-case Azure
DevOps since it doesn't work with the go standard convention of discovering
the root of a git repository
What to do next?
v0.12.3Compare Source
Added
Fixed
What to do next?
v0.12.2Compare Source
Changed
dagger initnow generates files in the current directory by default and no longer in./daggerby @TomChv in https://github.com/dagger/dagger/pull/7824Fixed
What to do next?
v0.12.1Compare Source
Added
Sockets as arguments from the CLI to Functions by @sipsma in https://github.com/dagger/dagger/pull/7804--compatflag for develop to target a specific api version by @jedevc in https://github.com/dagger/dagger/pull/7948Changed
dagger version/dagger login/dagger logout/etc by @jedevc in https://github.com/dagger/dagger/pull/7928Fixed
@in local module name by @grouville in https://github.com/dagger/dagger/pull/7891dagger versionsometimes disappearing by @jedevc in https://github.com/dagger/dagger/pull/7919What to do next?
v0.12.0Compare Source
This release is significant. All details (including videos & code examples)
are captured in this blog post.
🔥 Breaking Changes
See the SDK-specific release notes for more information.
Container.withNewFilesignature withDirectory.withNewFileby @helderco in https://github.com/dagger/dagger/pull/7293Callers of
Container.withNewFilewill need to changecontentsfrom optional to required argument.withExecby @helderco in https://github.com/dagger/dagger/pull/7136Callers relying on a
Container's entrypoint will need to be updatedto opt-in with
useEntrypoint.Container.stdoutandContainer.stderrby @helderco in https://github.com/dagger/dagger/pull/7857Callers of
stdoutandstderrwithout a previouswithExecwill need toinsert an explicit empty
withExec.Container.terminalnow returns aContainerby @aluzzardi in https://github.com/dagger/dagger/pull/7586Callers of
terminalwill need be updated to handle the updated type.Callers expecting a boolean return will need to be updated to instead
handle a string path.
sshAuthSocketandsshKnownHostsargs fromGitRef.treeby @jedevc in https://github.com/dagger/dagger/pull/6934Callers should instead attach these arguments onto the top-level
gitcall.idparameters forcontainer,directoryandsocketby @jedevc in https://github.com/dagger/dagger/pull/6934Users of these parameters should instead use the standalone
loadContainerFromID,loadDirectoryFromIDandloadSocketFromIDrespectively.
checkVersionCompatibilityfield (versioning checks are now automatically performed on all connections) by @jedevc in https://github.com/dagger/dagger/pull/7751Versioning checks are now all automatically performed on all connections, and
never need to be manually performed through the API.
Upgrade Instructions
Thanks to the new compatibility mode feature, these breaking changes should not
impact any existing Modules immediately.
dagger callshould still work onv0.12.0 without any changes to your Module code (any compat issues for modules
are likely a bug, please report!)
After upgrading to Engine v0.12.0, you can upgrade your Module to use the
latest v0.12.0 APIs by running
dagger develop. That will update theengineVersionfield of your module'sdagger.jsonconfiguration file tov0.12.0and enable the new APIs.After that, if your code is impacted by any of the breaking changes, you will
see errors when running
dagger call. Once the errors are fixed,dagger callwill work again and your module can be updated in Daggerverse if desired.
More detailed instructions on addressing the individual API incompatible
changes can be found in the PR descriptions linked above.
Added
terminalcan be inserted into the middle ofContainerandDirectorypipelines to pop an interactive shell by @aluzzardi in https://github.com/dagger/dagger/pull/7586-qflag andDAGGER_QUIET=1to restore previous verbosity default by @vito in https://github.com/dagger/dagger/pull/7822~) in file, directory and secret file argument by @wingyplus in https://github.com/dagger/dagger/pull/7818Changed
dagger callby @helderco in https://github.com/dagger/dagger/pull/7479Fixed
LICENSEonly if--sdkis set ondagger developby @TomChv in https://github.com/dagger/dagger/pull/7719What to do next?
v0.11.9Compare Source
Fixed
What to do next?
v0.11.8Compare Source
🔥Breaking Changes
Added
Changed
Fixed
Dependencies
What to do next?
v0.11.7Compare Source
🔥 Breaking Changes
Fileinstead of string for improved performance by @sipsma in https://github.com/dagger/dagger/pull/7549Changed
Fixed
File.exportto local Windows client by @wingyplus in https://github.com/dagger/dagger/pull/7564What to do next?
v0.11.6Compare Source
Added
withNamemethod to File by @TomChv in https://github.com/dagger/dagger/pull/7491Fixed
--helpby @helderco in https://github.com/dagger/dagger/pull/7417What to do next?
v0.11.5Compare Source
Added
dagger logincloud traces support by @aluzzardi in https://github.com/dagger/dagger/pull/7125--progress=plainimplementation for better visibility by @jedevc in https://github.com/dagger/dagger/pull/7272Changed
Fixed
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.