Update dagger-io requirement from ~=0.9.7 to ~=0.16.1 in /dbt-spark

[dependabot]

Updates the requirements on dagger-io to permit the latest version.

Release notes

Sourced from dagger-io's releases.

helm/chart/v0.16.1

v0.16.1 - 2025-02-19

Dependencies

• Bump Engine to v0.16.1 by @​sipsma in dagger/dagger#9634

What to do next?

• Read the documentation
• Join our Discord server
• Follow us on Twitter

Changelog

Sourced from dagger-io's changelog.

v0.16.1 - 2025-02-19

Fixed

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

What to do next?

• Read the documentation
• Join our Discord server
• Follow us on Twitter

v0.16.0 - 2025-02-19

🔥 Breaking Changes

• To match automatic configuration, insecure-entitlements now includes security.insecure when configuring the engine manually by @​jedevc in dagger/dagger#9513

• Module load performance is improved and related API refactored by @​sipsma in dagger/dagger#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:

  {

... (truncated)

Commits

• b152c15 chore: prep for v0.16.1 (#9634)
• 191842e Revert "bundle tsx in the engine image to speed up the TS sdk's node-runtime ...
• 9282e31 chore: prep for v0.16.0 (#9629)
• b6e0cb7 bundle tsx in the engine image to speed up the TS sdk's node-runtime module i...
• abe35c5 fix module source cache invalidation + cleanup api (#9505)
• 7aabd50 telemetry: handle log records with no trace/span (#9616)
• 29ef4bc sdk/java: check object definition (#9604)
• 295bf8b chore(sdk/php): use DefaultPath to SDK source directory in dev module (#9424)
• 4aa667e chore(deps): bump the sdk-java group in /sdk/java with 2 updates (#9602)
• 5430c55 sdk/java: @​DefaultPath and @​Ignore (#9532)
• Additional commits viewable in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #854.