Skip to content
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.

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

chore(deps): update dependency dagger/dagger to v0.13.6 #118

Merged
merged 1 commit into from
Oct 25, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 25, 2024

This PR contains the following updates:

Package Update Change
dagger/dagger patch 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
Fixed
  • Allow custom enums that include ambiguous names (such as true/false) by @​jedevc in https://github.com/dagger/dagger/pull/8682

  • Optimize Container.from for image refs with digests by @​sipsma in https://github.com/dagger/dagger/pull/8736
    Previously, 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, or refs/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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

| datasource  | package       | from    | to      |
| ----------- | ------------- | ------- | ------- |
| github-tags | dagger/dagger | v0.13.5 | v0.13.6 |


Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate renovate bot merged commit d7f41fd into main Oct 25, 2024
5 checks passed
@renovate renovate bot deleted the renovate/dagger-dagger-0.x branch October 25, 2024 17:17
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.

0 participants