chore(deps): update dependency dagger/dagger to v0.13.6 #118
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:
0.13.5
->0.13.6
Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
dagger/dagger (dagger/dagger)
v0.13.6
Compare 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 init
defaults to use.dagger
folder during if current directory.
is not empty by @rajatjindal in https://github.com/dagger/dagger/pull/8557dagger install
now preserves the original source input, and tracks a separatepin
field 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.from
for image refs with digests by @sipsma in https://github.com/dagger/dagger/pull/8736Previously, if
Container.from
was 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?
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.
This PR was generated by Mend Renovate. View the repository job log.