build(deps): update dagger-io requirement from ~=0.14 to ~=0.15 in /.dagger-ci/daggerci

[dependabot]

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

Release notes

Sourced from dagger-io's releases.

helm/chart/v0.15.1

v0.15.1 - 2024-12-12

Dependencies

• Bump Engine to v0.15.1 by @​cwlbraa in dagger/dagger#9183

What to do next?

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

Changelog

Sourced from dagger-io's changelog.

v0.15.1 - 2024-12-12

Fixed

• Metrics display in the TUI is fixed to display for all executed containers, rather than just services by @​sipsma in dagger/dagger#9171

What to do next?

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

v0.15.0 - 2024-12-11

🔥 Breaking Changes

• Container.asService now uses the command specified by withDefaultArgs instead of the last withExec command by @​rajatjindal in dagger/dagger#8865
  Users can override the args by providing the args option to asService. They can also configure the container to use the container entrypoint by using useEntrypoint option.

Added

• Better TUI errors, new cached/pending states, duration accounting and fewer spans by @​vito in dagger/dagger#8442

• Custom dagger engine.json config file by @​jedevc in dagger/dagger#8800
  This new config file format is intended to eventually replace the old buildkit-style engine.toml file that's currently used for configuration.

  This file can be either mounted directly into a manually started engine at /etc/dagger/engine.toml, or it will automatically mounted from the user's ~/.config/dagger/engine.json when the engine is started.

• Filesync performance is improved by @​sipsma in dagger/dagger#8818
  The engine now re-uses previously loaded data more reliably and in more cases, which speeds up repeated reloads of the same or similar (i.e. overlapping data).

  Uncached filesyncs of large amounts of data is also faster and uses less memory in the engine.

• Added dagger uninstall command to remove a dependency by @​rajatjindal in dagger/dagger#8745

• Added memory and network telemetry for execs by @​cwlbraa in dagger/dagger#8880 dagger/dagger#8902

• Added DAGGER_LEAVE_OLD_ENGINE environment variable to optionally prevent removal of old engine containers during upgrades by devin in dagger/dagger#8195

Fixed

• Directory.terminal API works now by @​sipsma in dagger/dagger#8952
• Fix resource leaks in the engine that occurred after each debug terminal was opened by @​sipsma in dagger/dagger#9013
• Fix cache mounts not being included in interactive debug containers by @​sipsma in dagger/dagger#9034
• Allow Container.withExec expect to catch exit code 128 by @​jedevc in dagger/dagger#9027
• Correctly apply ignore pattern when pulling a directory from git by @​TomChv in dagger/dagger#8931
• Fix panic on null Directory.digest by @​jedevc in dagger/dagger#8946

What to do next?

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

... (truncated)

Commits

• 196f232 chore: prep for v0.15.1 (#9183)
• c4f683f upgrade golang.org/x/crypto dep to avoid CVE (#9172)
• 796de0f chore: update release date for v0.15.0 (#9166)
• 8b9fbf5 chore: prep for v0.15.0 (#9158)
• 2fbc7df shell: reimplement module loading and execution according to new model (#9097)
• 521708b python: remove deprecated index-url in tool.uv (#9127)
• da0726e chore(deps): bump the sdk-python group across 1 directory with 2 updates (#9139)
• eb738eb feat: decouple provisioning & refactor ts sdk architecture (#9031)
• fdc7f3f fix(engine): use default args for starting container as service (#8865)
• 55fce3d docs(sdk/python): improve PyPI example with better error handling and clarity...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually 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)

[AtomicFS]

I would not merge on its own because of golang.org/x/crypto vulnerability