kjuulh/dagger-components
1
0
Fork 0
Code Issues 1 Pull Requests 2 Packages Projects Releases 3 Wiki Activity

chore(deps): update all dependencies #65

Merged
kjuulh merged 1 commits from renovate/all into main 2025-02-21 02:35:46 +01:00
Conversation 0 Commits 1 Files Changed 2 +6 -6
kjuulh commented 2025-02-20 02:37:10 +01:00
Owner
Copy Link

This PR contains the following updates:

Package Type Update Change
dagger-sdk workspace.dependencies minor 0.15.0 -> 0.16.0
serde_json workspace.dependencies patch 1.0.138 -> 1.0.139

Release Notes

dagger/dagger (dagger-sdk)

v0.16.1

Compare Source

Fixed
What to do next?

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
What to do next?
serde-rs/json (serde_json)

v1.0.139

Compare Source

  • Documentation improvements

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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

  • 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) | workspace.dependencies | minor | `0.15.0` -> `0.16.0` | | [serde_json](https://github.com/serde-rs/json) | workspace.dependencies | patch | `1.0.138` -> `1.0.139` | --- ### 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 [@&#8203;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 [@&#8203;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 [@&#8203;jedevc](https://github.com/jedevc) in https://github.com/dagger/dagger/pull/9513 - Module load performance is improved and related API refactored by [@&#8203;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 [@&#8203;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> <details> <summary>serde-rs/json (serde_json)</summary> ### [`v1.0.139`](https://github.com/serde-rs/json/releases/tag/v1.0.139) [Compare Source](https://github.com/serde-rs/json/compare/v1.0.138...v1.0.139) - Documentation improvements </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. 👻 **Immortal**: This PR will be recreated if closed unmerged. Get [config help](https://github.com/renovatebot/renovate/discussions) if that's undesired. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy40MjQuMyIsInVwZGF0ZWRJblZlciI6IjM3LjQyNC4zIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->
kjuulh added 1 commit 2025-02-20 02:37:10 +01:00
chore(deps): update rust crate dagger-sdk to 0.16.0
All checks were successful
continuous-integration/drone/push Build is passing
Details
continuous-integration/drone/pr Build is passing
Details
45b59096ee
kjuulh changed title from chore(deps): update rust crate dagger-sdk to 0.16.0 to chore(deps): update all dependencies 2025-02-20 06:32:47 +01:00
kjuulh force-pushed renovate/all from 45b59096ee to c79cc1da81 2025-02-20 06:32:48 +01:00 Compare
kjuulh merged commit c79cc1da81 into main 2025-02-21 02:35:46 +01:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: kjuulh/dagger-components#65
No description provided.
Delete Branch "renovate/all"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?