fix(deps): update rust crate dagger-sdk to 0.16.0 #58

kjuulh · 2025-02-21T02:34:17+01:00

kjuulh commented

2025-02-21 02:34:17 +01:00

This PR contains the following updates:

Package	Type	Update	Change
dagger-sdk	dependencies	minor	`0.15.0` -> `0.16.0`

Release Notes

dagger/dagger (dagger-sdk)

`v0.16.1`

Compare Source

Fixed

Fix typescript modules on arm64 using tsx for wrong platform by @sipsma in https://github.com/dagger/dagger/pull/9633
Fix internal error cannot sub-select 1th item from *dagql.PostCallTyped by @sipsma in https://github.com/dagger/dagger/pull/9634

What to do next?

Read the documentation
Join our Discord server
Follow us on Twitter

`v0.16.0`

Compare Source

🔥 Breaking Changes

To match automatic configuration, insecure-entitlements now includes security.insecure when configuring the engine manually by @jedevc in https://github.com/dagger/dagger/pull/9513
Module load performance is improved and related API refactored by @sipsma in https://github.com/dagger/dagger/pull/9505
Loading of modules (the load module step shown in progress output) is faster now in many cases. In particular:
- Cache utilization of module loading is greatly improved, which can decrease load times by up to a factor of 10 when re-calling functions after changing source code in a Daggerized repo.
- Less extraneous files are loaded from the source repository
Users of modules with large numbers of dependencies or in large git repositories are expected to see the most immediate benefit.

For some concrete numbers, here are load module times for the dagger-dev's module in Dagger's repository under different scenarios:
- dagger call --help on new engines with an empty cache
  - v0.15.4: 1m20s
  - v0.16.0: 1m1s
  - ~23% faster
- re-running dagger call --help with no file changes in the repo:
  - v0.15.4: 10.9s
  - v0.16.0: 2.8s
  - ~74% faster
- re-running dagger call --help after making a change to a random source code file in the repo:
  - v0.15.4: 32.1s
  - v0.16.0: 2.8s
  - ~91% faster
These improvements in cache utilization are also setup for future improvements not only in load module times but function call times more generally.

This improvement comes with a few breaking changes that are not expected to impact most users. However, the changes require that users upgrade their CLI to v0.16.0 in order to connect to v0.16.0 engines. Older CLIs will error when connecting to newer engines.

In terms of the breaking changes, impacted users are those who:
- have function code that imports local libraries outside of the dagger module source directory
- rely on a package manager configuration file (e.g. go.mod) that exists in a parent directory of the dagger module source directory
They may need to update their dagger.json configuration file to add an explicit "include" setting to ensure those extra files or directories are loaded with the module. This is because numerous files previously implicitly loaded are now skipped by default, which contributes to the performance improvements.

For example, if your module code is in .dagger and relies on the go.mod file in the parent directory, you would add the following to your dagger.json file:
```
{
  "include": ["../go.mod", "../go.sum"]
}
```
The values in the "include" array are relative to the directory containing dagger.json. They can be also be glob patterns (e.g. "**/*.txt"). To explicitly exclude some files matched by a previous include pattern, you can prepend the include pattern with a ! character (e.g. "!**/foo.txt").
- Previously, the exclude setting existed but has now been superseded by prefixing an include pattern with a ! character. However, this is backwards-compatible, so existing exclude settings will be automatically turned into equivalent !-prefixed include settings when running dagger develop. No user intervention is needed.
The core API's ModuleSource and Module types have also undergone some cleanup that includes breaking changes. Most users do not interact with these APIs, but any that do may need some minor adjustments to their code. In particular:
- Module.initialize no longer needs to be called; the module is initialized on creation
- ResolveFromCaller no longer needs to be called for local module sources; context is automatically loaded and resolved efficiently as needed by other API calls

Added

Allow tilde home expansion in dag.Host operations by @jedevc in https://github.com/dagger/dagger/pull/9610

What to do next?

Read the documentation
Join our Discord server
Follow us on Twitter

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ 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.

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

This PR has been generated by Renovate Bot.

This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [dagger-sdk](https://github.com/dagger/dagger) | dependencies | minor | `0.15.0` -> `0.16.0` | --- ### Release Notes <details> <summary>dagger/dagger (dagger-sdk)</summary> ### [`v0.16.1`](https://github.com/dagger/dagger/blob/HEAD/CHANGELOG.md#v0161---2025-02-19) [Compare Source](https://github.com/dagger/dagger/compare/v0.16.0...v0.16.1) ##### Fixed - Fix typescript modules on arm64 using tsx for wrong platform by [@sipsma](https://github.com/sipsma) in https://github.com/dagger/dagger/pull/9633 - Fix internal error `cannot sub-select 1th item from *dagql.PostCallTyped` by [@sipsma](https://github.com/sipsma) in https://github.com/dagger/dagger/pull/9634 ##### What to do next? - Read the [documentation](https://docs.dagger.io) - Join our [Discord server](https://discord.gg/dagger-io) - Follow us on [Twitter](https://twitter.com/dagger_io) ### [`v0.16.0`](https://github.com/dagger/dagger/blob/HEAD/CHANGELOG.md#v0160---2025-02-19) [Compare Source](https://github.com/dagger/dagger/compare/v0.15.4...v0.16.0) ##### 🔥 Breaking Changes - To match automatic configuration, `insecure-entitlements` now includes `security.insecure` when configuring the engine manually by [@jedevc](https://github.com/jedevc) in https://github.com/dagger/dagger/pull/9513 - Module load performance is improved and related API refactored by [@sipsma](https://github.com/sipsma) in https://github.com/dagger/dagger/pull/9505 \ Loading of modules (the `load module` step shown in progress output) is faster now in many cases. In particular: - Cache utilization of module loading is greatly improved, which can decrease load times by up to a factor of 10 when re-calling functions after changing source code in a Daggerized repo. - Less extraneous files are loaded from the source repository Users of modules with large numbers of dependencies or in large git repositories are expected to see the most immediate benefit. For some concrete numbers, here are `load module` times for the `dagger-dev`'s module in Dagger's repository under different scenarios: - `dagger call --help` on new engines with an empty cache - v0.15.4: 1m20s - v0.16.0: 1m1s - \~23% faster - re-running `dagger call --help` with no file changes in the repo: - v0.15.4: 10.9s - v0.16.0: 2.8s - \~74% faster - re-running `dagger call --help` after making a change to a random source code file in the repo: - v0.15.4: 32.1s - v0.16.0: 2.8s - \~91% faster These improvements in cache utilization are also setup for future improvements not only in `load module` times but function call times more generally. This improvement comes with a few breaking changes that are not expected to impact most users. However, the changes require that users upgrade their CLI to v0.16.0 in order to connect to v0.16.0 engines. Older CLIs will error when connecting to newer engines. In terms of the breaking changes, impacted users are those who: - have function code that imports local libraries outside of the dagger module source directory - rely on a package manager configuration file (e.g. go.mod) that exists in a parent directory of the dagger module source directory They may need to update their dagger.json configuration file to add an explicit `"include"` setting to ensure those extra files or directories are loaded with the module. This is because numerous files previously implicitly loaded are now skipped by default, which contributes to the performance improvements. For example, if your module code is in `.dagger` and relies on the `go.mod` file in the parent directory, you would add the following to your `dagger.json` file: ```json { "include": ["../go.mod", "../go.sum"] } ``` The values in the `"include"` array are relative to the directory containing `dagger.json`. They can be also be glob patterns (e.g. `"**/*.txt"`). To explicitly exclude some files matched by a previous include pattern, you can prepend the include pattern with a `!` character (e.g. `"!**/foo.txt"`). - Previously, the `exclude` setting existed but has now been superseded by prefixing an include pattern with a `!` character. However, this is backwards-compatible, so existing `exclude` settings will be automatically turned into equivalent `!`-prefixed include settings when running `dagger develop`. No user intervention is needed. The core API's `ModuleSource` and `Module` types have also undergone some cleanup that includes breaking changes. Most users do not interact with these APIs, but any that do may need some minor adjustments to their code. In particular: - `Module.initialize` no longer needs to be called; the module is initialized on creation - `ResolveFromCaller` no longer needs to be called for local module sources; context is automatically loaded and resolved efficiently as needed by other API calls ##### Added - Allow tilde home expansion in `dag.Host` operations by [@jedevc](https://github.com/jedevc) in https://github.com/dagger/dagger/pull/9610 ##### What to do next? - Read the [documentation](https://docs.dagger.io) - Join our [Discord server](https://discord.gg/dagger-io) - Follow us on [Twitter](https://twitter.com/dagger_io) </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Enabled. ♻ **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. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).

kjuulh added 1 commit 2025-02-21 02:34:17 +01:00

fix(deps): update rust crate dagger-sdk to 0.16.0

renovate/artifacts Artifact file update failure

continuous-integration/drone/push Build is failing

Details

continuous-integration/drone/pr Build is failing

Details

eaf57adaa5

kjuulh scheduled this pull request to auto merge when all checks succeed 2025-02-21 02:34:18 +01:00

kjuulh commented

2025-02-21 02:34:18 +01:00

⚠️ Artifact update problem

Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: Cargo.lock

Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path crates/cuddle-rust-service-plan/Cargo.toml --package dagger-sdk@0.15.4 --precise 0.16.1
    Updating crates.io index
error: failed to select a version for the requirement `dagger-sdk = "^0.15.0"`
candidate versions found which didn't match: 0.16.1
location searched: crates.io index
required by package `cuddle-ci v0.3.0 (https://git.front.kjuulh.io/kjuulh/dagger-components?branch=main#11326924)`
    ... which satisfies git dependency `cuddle-ci` (locked to 0.3.0) of package `cuddle-rust-service-plan v0.1.0 (/tmp/renovate/repos/gitea/kjuulh/cuddle-rust-service-plan/crates/cuddle-rust-service-plan)`

File name: Cargo.lock

Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path ci/Cargo.toml --package dagger-sdk@0.15.4 --precise 0.16.1
    Updating crates.io index
error: failed to select a version for the requirement `dagger-sdk = "^0.15.0"`
candidate versions found which didn't match: 0.16.1
location searched: crates.io index
required by package `cuddle-ci v0.3.0 (https://git.front.kjuulh.io/kjuulh/dagger-components?branch=main#11326924)`
    ... which satisfies git dependency `cuddle-ci` (locked to 0.3.0) of package `cuddle-rust-service-plan v0.1.0 (/tmp/renovate/repos/gitea/kjuulh/cuddle-rust-service-plan/crates/cuddle-rust-service-plan)`

### ⚠️ Artifact update problem Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is. ♻ Renovate will retry this branch, including artifacts, only when one of the following happens: - any of the package files in this branch needs updating, or - the branch becomes conflicted, or - you click the rebase/retry checkbox if found above, or - you rename this PR's title to start with "rebase!" to trigger it manually The artifact failure details are included below: ##### File name: Cargo.lock ``` Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path crates/cuddle-rust-service-plan/Cargo.toml --package dagger-sdk@0.15.4 --precise 0.16.1 Updating crates.io index error: failed to select a version for the requirement `dagger-sdk = "^0.15.0"` candidate versions found which didn't match: 0.16.1 location searched: crates.io index required by package `cuddle-ci v0.3.0 (https://git.front.kjuulh.io/kjuulh/dagger-components?branch=main#11326924)` ... which satisfies git dependency `cuddle-ci` (locked to 0.3.0) of package `cuddle-rust-service-plan v0.1.0 (/tmp/renovate/repos/gitea/kjuulh/cuddle-rust-service-plan/crates/cuddle-rust-service-plan)` ``` ##### File name: Cargo.lock ``` Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path ci/Cargo.toml --package dagger-sdk@0.15.4 --precise 0.16.1 Updating crates.io index error: failed to select a version for the requirement `dagger-sdk = "^0.15.0"` candidate versions found which didn't match: 0.16.1 location searched: crates.io index required by package `cuddle-ci v0.3.0 (https://git.front.kjuulh.io/kjuulh/dagger-components?branch=main#11326924)` ... which satisfies git dependency `cuddle-ci` (locked to 0.3.0) of package `cuddle-rust-service-plan v0.1.0 (/tmp/renovate/repos/gitea/kjuulh/cuddle-rust-service-plan/crates/cuddle-rust-service-plan)` ```

kjuulh added 1 commit 2025-02-21 02:34:18 +01:00

fix(deps): update rust crate dagger-sdk to 0.16.0

renovate/artifacts Artifact file update failure

continuous-integration/drone/push Build is failing

Details

continuous-integration/drone/pr Build is failing

Details

eaf57adaa5

renovate/artifacts Artifact file update failure

continuous-integration/drone/push Build is failing

Details

continuous-integration/drone/pr Build is failing

Details

This pull request can be merged automatically.

You are not authorized to merge this pull request.

View command line instructions.

Checkout

From your project repository, check out a new branch and test the changes.

git fetch -u origin renovate/all:renovate/all

git checkout renovate/all

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: kjuulh/cuddle-rust-service-plan#58