chore(deps): update dependency dagger/dagger to v0.14.0 #42
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-approve[bot]](https://avatars.githubusercontent.com/in/7394?s=60&v=4){kind=small}
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/dagger-dagger-0.x
branch
from
78562ef to
5f17c72
Compare
renovate
bot
force-pushed
the
renovate/dagger-dagger-0.x
branch
from
5f17c72 to
6bd0d8b
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/dagger-dagger-0.x
branch
from
6bd0d8b to
8e51691
Compare
renovate
bot
force-pushed
the
renovate/dagger-dagger-0.x
branch
2 times, most recently
from
04fe044 to
4785a3a
Compare
| datasource | package | from | to | | ----------- | ------------- | ------- | ------- | | github-tags | dagger/dagger | v0.13.5 | v0.14.0 | Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
renovate
bot
force-pushed
the
renovate/dagger-dagger-0.x
branch
from
4785a3a to
d0fb100
Compare
leonardoce
approved these changes
Dec 5, 2024
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:
0.13.5->0.14.0Release Notes
dagger/dagger (dagger/dagger)
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?
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.