kjuulh/cuddle-rust-service-plan
1
0
Fork 0
Code Issues 1 Pull Requests 2 Packages Projects Releases Wiki Activity

fix(deps): update all dependencies #59

Open
kjuulh wants to merge 1 commits from renovate/all into main
pull from: renovate/all
merge into: kjuulh:main
Conversation 1 Commits 1 Files Changed 3 +52 -22
kjuulh commented 2025-02-25 06:31:58 +01:00
Owner
Copy Link

This PR contains the following updates:

Package Type Update Change
anyhow workspace.dependencies patch 1.0.96 -> 1.0.97
async-trait dependencies patch 0.1.86 -> 0.1.88
clap workspace.dependencies patch 4.5.31 -> 4.5.34
dagger-sdk dependencies minor 0.15.0 -> 0.17.0
tokio (source) workspace.dependencies minor 1.43.0 -> 1.44.1

Release Notes

dtolnay/anyhow (anyhow)

v1.0.97

Compare Source

  • Documentation improvements
dtolnay/async-trait (async-trait)

v0.1.88

Compare Source

  • Fix lifetime bounding on generic parameters that have cfg (#​289)

v0.1.87

Compare Source

  • Documentation improvements
clap-rs/clap (clap)

v4.5.34

Compare Source

Fixes
  • (help) Don't add extra blank lines with flatten_help(true) and subcommands without arguments

v4.5.33

Compare Source

Fixes
  • (error) When showing the usage of a suggestion for an unknown argument, don't show the group

v4.5.32

Compare Source

Features
  • Add Error::remove
Documentation
  • (cookbook) Switch from humantime to jiff
  • (tutorial) Better cover required vs optional
Internal
  • Update pulldown-cmark
dagger/dagger (dagger-sdk)

v0.17.2

Compare Source

Added
Changed
What to do next?

v0.17.1

Compare Source

  • BREAKING(llm): fix go sdk capitalization of "Llm" to "LLM" instead, consistent with engine code and the rest of the go ecosystem (https://github.com/dagger/dagger/pull/9933)
    • this will break compilation of modules referencing the LLM API like dag.Llm. To fix, simply change to dag.LLM
  • when prompting for remote module LLM access, error early in non-interactive situations where we would previously hang indefinitely. (https://github.com/dagger/dagger/pull/9957)
What to do next?

v0.17.0

Compare Source

Added
Changed
What to do next?

v0.16.3

Compare Source

Added
Changed
Dependencies
What to do next?

v0.16.2

Compare Source

Added
Fixed
Dependencies
What to do next?

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?
tokio-rs/tokio (tokio)

v1.44.1: Tokio v1.44.1

Compare Source

1.44.1 (March 13th, 2025)

Fixed
  • rt: skip defer queue in block_in_place context (#​7216)

v1.44.0: Tokio v1.44.0

Compare Source

1.44.0 (March 7th, 2025)

This release changes the from_std method on sockets to panic if a blocking socket is provided. We determined this change is not a breaking change as Tokio is not intended to operate using blocking sockets. Doing so results in runtime hangs and should be considered a bug. Accidentally passing a blocking socket to Tokio is one of the most common user mistakes. If this change causes an issue for you, please comment on #​7172.

Added
  • coop: add task::coop module (#​7116)
  • process: add Command::get_kill_on_drop() (#​7086)
  • sync: add broadcast::Sender::closed (#​6685, #​7090)
  • sync: add broadcast::WeakSender (#​7100)
  • sync: add oneshot::Receiver::is_empty() (#​7153)
  • sync: add oneshot::Receiver::is_terminated() (#​7152)
Fixed
  • fs: empty reads on File should not start a background read (#​7139)
  • process: calling start_kill on exited child should not fail (#​7160)
  • signal: fix CTRL_CLOSE, CTRL_LOGOFF, CTRL_SHUTDOWN on windows (#​7122)
  • sync: properly handle panic during mpsc drop (#​7094)
Changes
  • runtime: clean up magic number in registration set (#​7112)
  • coop: make coop yield using waker defer strategy (#​7185)
  • macros: make select! budget-aware (#​7164)
  • net: panic when passing a blocking socket to from_std (#​7166)
  • io: clean up buffer casts (#​7142)
Changes to unstable APIs
  • rt: add before and after task poll callbacks (#​7120)
  • tracing: make the task tracing API unstable public (#​6972)
Documented
  • docs: fix nesting of sections in top-level docs (#​7159)
  • fs: rename symlink and hardlink parameter names (#​7143)
  • io: swap reader/writer in simplex doc test (#​7176)
  • macros: docs about select! alternatives (#​7110)
  • net: rename the argument for send_to (#​7146)
  • process: add example for reading Child stdout (#​7141)
  • process: clarify Child::kill behavior (#​7162)
  • process: fix grammar of the ChildStdin struct doc comment (#​7192)
  • runtime: consistently use worker_threads instead of core_threads (#​7186)

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.

👻 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 | |---|---|---|---| | [anyhow](https://github.com/dtolnay/anyhow) | workspace.dependencies | patch | `1.0.96` -> `1.0.97` | | [async-trait](https://github.com/dtolnay/async-trait) | dependencies | patch | `0.1.86` -> `0.1.88` | | [clap](https://github.com/clap-rs/clap) | workspace.dependencies | patch | `4.5.31` -> `4.5.34` | | [dagger-sdk](https://github.com/dagger/dagger) | dependencies | minor | `0.15.0` -> `0.17.0` | | [tokio](https://tokio.rs) ([source](https://github.com/tokio-rs/tokio)) | workspace.dependencies | minor | `1.43.0` -> `1.44.1` | --- ### Release Notes <details> <summary>dtolnay/anyhow (anyhow)</summary> ### [`v1.0.97`](https://github.com/dtolnay/anyhow/releases/tag/1.0.97) [Compare Source](https://github.com/dtolnay/anyhow/compare/1.0.96...1.0.97) - Documentation improvements </details> <details> <summary>dtolnay/async-trait (async-trait)</summary> ### [`v0.1.88`](https://github.com/dtolnay/async-trait/releases/tag/0.1.88) [Compare Source](https://github.com/dtolnay/async-trait/compare/0.1.87...0.1.88) - Fix lifetime bounding on generic parameters that have cfg ([#&#8203;289](https://github.com/dtolnay/async-trait/issues/289)) ### [`v0.1.87`](https://github.com/dtolnay/async-trait/releases/tag/0.1.87) [Compare Source](https://github.com/dtolnay/async-trait/compare/0.1.86...0.1.87) - Documentation improvements </details> <details> <summary>clap-rs/clap (clap)</summary> ### [`v4.5.34`](https://github.com/clap-rs/clap/blob/HEAD/CHANGELOG.md#4534---2025-03-27) [Compare Source](https://github.com/clap-rs/clap/compare/v4.5.33...v4.5.34) ##### Fixes - *(help)* Don't add extra blank lines with `flatten_help(true)` and subcommands without arguments ### [`v4.5.33`](https://github.com/clap-rs/clap/blob/HEAD/CHANGELOG.md#4533---2025-03-26) [Compare Source](https://github.com/clap-rs/clap/compare/v4.5.32...v4.5.33) ##### Fixes - *(error)* When showing the usage of a suggestion for an unknown argument, don't show the group ### [`v4.5.32`](https://github.com/clap-rs/clap/blob/HEAD/CHANGELOG.md#4532---2025-03-10) [Compare Source](https://github.com/clap-rs/clap/compare/v4.5.31...v4.5.32) ##### Features - Add `Error::remove` ##### Documentation - *(cookbook)* Switch from `humantime` to `jiff` - *(tutorial)* Better cover required vs optional ##### Internal - Update `pulldown-cmark` </details> <details> <summary>dagger/dagger (dagger-sdk)</summary> ### [`v0.17.2`](https://github.com/dagger/dagger/blob/HEAD/CHANGELOG.md#v0172---2025-03-27) [Compare Source](https://github.com/dagger/dagger/compare/v0.17.1...v0.17.2) ##### Added - New `Directory.filter` API for improved ergonomics by [@&#8203;rajatjindal](https://github.com/rajatjindal) in https://github.com/dagger/dagger/pull/9976 \ This was previously possible by doing `Query.directory.withDirectory("", dir)`, but this breaks the chain. ##### Changed - Various LLM API changes and improvements to tool calling scheme by [@&#8203;vito](https://github.com/vito) in https://github.com/dagger/dagger/pull/9956 ##### 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.17.1`](https://github.com/dagger/dagger/blob/HEAD/CHANGELOG.md#v0171---2025-03-24) [Compare Source](https://github.com/dagger/dagger/compare/v0.17.0...v0.17.1) - BREAKING(llm): fix go sdk capitalization of "Llm" to "LLM" instead, consistent with engine code and the rest of the go ecosystem (https://github.com/dagger/dagger/pull/9933) - this will break compilation of modules referencing the LLM API like `dag.Llm`. To fix, simply change to `dag.LLM` - when prompting for remote module LLM access, error early in non-interactive situations where we would previously hang indefinitely. (https://github.com/dagger/dagger/pull/9957) ##### 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.17.0`](https://github.com/dagger/dagger/blob/HEAD/CHANGELOG.md#v0170---2025-03-20) [Compare Source](https://github.com/dagger/dagger/compare/v0.16.3...v0.17.0) ##### Added - Stabilized Dagger Shell by [@&#8203;helderco](https://github.com/helderco) in https://github.com/dagger/dagger/pull/9896 Find out more at <https://docs.dagger.io/features/shell/> - New top-level `LLM` API to allow integrating LLMs with native Dagger types in https://github.com/dagger/dagger/pull/9628 Find out more at <https://docs.dagger.io/ai-agents/> ##### Changed - The default unix socket used to connect to the engine is now at `/run/dagger/engine.sock` by [@&#8203;sipsma](https://github.com/sipsma) in https://github.com/dagger/dagger/pull/9866 \ The previous socket path still exists for backwards compatibility but may be removed in a future version. - Fields that return directory paths such as `Directory.glob` and `Directory.entries` now return a trailing slash to distinguish from regular files by [@&#8203;jedevc](https://github.com/jedevc) in https://github.com/dagger/dagger/pull/9118 ##### 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.3`](https://github.com/dagger/dagger/blob/HEAD/CHANGELOG.md#v0163---2025-03-12) [Compare Source](https://github.com/dagger/dagger/compare/v0.16.2...v0.16.3) ##### Added - Add new `Directory.asGit` API for converting a directory into a git repository by [@&#8203;jedevc](https://github.com/jedevc) in https://github.com/dagger/dagger/pull/9730 - Allow CLI flags in `dagger call` for `GitRepository` and `GitRef` types by [@&#8203;jedevc](https://github.com/jedevc) in https://github.com/dagger/dagger/pull/9844 - Improved caching of `Container.asTarball` by [@&#8203;jedevc](https://github.com/jedevc) in https://github.com/dagger/dagger/pull/9395 ##### Changed - Improved visualization of chains with content digests by [@&#8203;vito](https://github.com/vito) in https://github.com/dagger/dagger/pull/9739 ##### Dependencies - Downgrade go to 1.23 by [@&#8203;jedevc](https://github.com/jedevc) in https://github.com/dagger/dagger/pull/9766 - This is due to a regression in go 1.24, see https://github.com/dagger/dagger/issues/9759 ##### 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.2`](https://github.com/dagger/dagger/blob/HEAD/CHANGELOG.md#v0162---2025-02-27) [Compare Source](https://github.com/dagger/dagger/compare/v0.16.1...v0.16.2) ##### Added - Add `Directory.name` field to retrieve current directory name by [@&#8203;TomChv](https://github.com/TomChv) in https://github.com/dagger/dagger/pull/9617 ##### Fixed - Fixed panic when `dagger call` or `dagger functions` called in directory with no modules - it now errors cleanly by [@&#8203;sipsma](https://github.com/sipsma) in https://github.com/dagger/dagger/pull/9658 - Improve load time when dagger commands run in directories with no `dagger.json` by [@&#8203;sipsma](https://github.com/sipsma) in https://github.com/dagger/dagger/pull/9659 - Fixed secret when using context directories from a private HTTPS module by [@&#8203;jedevc](https://github.com/jedevc) in https://github.com/dagger/dagger/pull/9697 ##### Dependencies - Bump go to 1.24 by [@&#8203;jedevc](https://github.com/jedevc) in https://github.com/dagger/dagger/pull/9673 ##### 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.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>tokio-rs/tokio (tokio)</summary> ### [`v1.44.1`](https://github.com/tokio-rs/tokio/releases/tag/tokio-1.44.1): Tokio v1.44.1 [Compare Source](https://github.com/tokio-rs/tokio/compare/tokio-1.44.0...tokio-1.44.1) ### 1.44.1 (March 13th, 2025) ##### Fixed - rt: skip defer queue in `block_in_place` context ([#&#8203;7216]) [#&#8203;7216]: https://github.com/tokio-rs/tokio/pull/7216 ### [`v1.44.0`](https://github.com/tokio-rs/tokio/releases/tag/tokio-1.44.0): Tokio v1.44.0 [Compare Source](https://github.com/tokio-rs/tokio/compare/tokio-1.43.0...tokio-1.44.0) ### 1.44.0 (March 7th, 2025) This release changes the `from_std` method on sockets to panic if a blocking socket is provided. We determined this change is not a breaking change as Tokio is not intended to operate using blocking sockets. Doing so results in runtime hangs and should be considered a bug. Accidentally passing a blocking socket to Tokio is one of the most common user mistakes. If this change causes an issue for you, please comment on [#&#8203;7172]. ##### Added - coop: add `task::coop` module ([#&#8203;7116]) - process: add `Command::get_kill_on_drop()` ([#&#8203;7086]) - sync: add `broadcast::Sender::closed` ([#&#8203;6685], [#&#8203;7090]) - sync: add `broadcast::WeakSender` ([#&#8203;7100]) - sync: add `oneshot::Receiver::is_empty()` ([#&#8203;7153]) - sync: add `oneshot::Receiver::is_terminated()` ([#&#8203;7152]) ##### Fixed - fs: empty reads on `File` should not start a background read ([#&#8203;7139]) - process: calling `start_kill` on exited child should not fail ([#&#8203;7160]) - signal: fix `CTRL_CLOSE`, `CTRL_LOGOFF`, `CTRL_SHUTDOWN` on windows ([#&#8203;7122]) - sync: properly handle panic during mpsc drop ([#&#8203;7094]) ##### Changes - runtime: clean up magic number in registration set ([#&#8203;7112]) - coop: make coop yield using waker defer strategy ([#&#8203;7185]) - macros: make `select!` budget-aware ([#&#8203;7164]) - net: panic when passing a blocking socket to `from_std` ([#&#8203;7166]) - io: clean up buffer casts ([#&#8203;7142]) ##### Changes to unstable APIs - rt: add before and after task poll callbacks ([#&#8203;7120]) - tracing: make the task tracing API unstable public ([#&#8203;6972]) ##### Documented - docs: fix nesting of sections in top-level docs ([#&#8203;7159]) - fs: rename symlink and hardlink parameter names ([#&#8203;7143]) - io: swap reader/writer in simplex doc test ([#&#8203;7176]) - macros: docs about `select!` alternatives ([#&#8203;7110]) - net: rename the argument for `send_to` ([#&#8203;7146]) - process: add example for reading `Child` stdout ([#&#8203;7141]) - process: clarify `Child::kill` behavior ([#&#8203;7162]) - process: fix grammar of the `ChildStdin` struct doc comment ([#&#8203;7192]) - runtime: consistently use `worker_threads` instead of `core_threads` ([#&#8203;7186]) [#&#8203;6685]: https://github.com/tokio-rs/tokio/pull/6685 [#&#8203;6972]: https://github.com/tokio-rs/tokio/pull/6972 [#&#8203;7086]: https://github.com/tokio-rs/tokio/pull/7086 [#&#8203;7090]: https://github.com/tokio-rs/tokio/pull/7090 [#&#8203;7094]: https://github.com/tokio-rs/tokio/pull/7094 [#&#8203;7100]: https://github.com/tokio-rs/tokio/pull/7100 [#&#8203;7110]: https://github.com/tokio-rs/tokio/pull/7110 [#&#8203;7112]: https://github.com/tokio-rs/tokio/pull/7112 [#&#8203;7116]: https://github.com/tokio-rs/tokio/pull/7116 [#&#8203;7120]: https://github.com/tokio-rs/tokio/pull/7120 [#&#8203;7122]: https://github.com/tokio-rs/tokio/pull/7122 [#&#8203;7139]: https://github.com/tokio-rs/tokio/pull/7139 [#&#8203;7141]: https://github.com/tokio-rs/tokio/pull/7141 [#&#8203;7142]: https://github.com/tokio-rs/tokio/pull/7142 [#&#8203;7143]: https://github.com/tokio-rs/tokio/pull/7143 [#&#8203;7146]: https://github.com/tokio-rs/tokio/pull/7146 [#&#8203;7152]: https://github.com/tokio-rs/tokio/pull/7152 [#&#8203;7153]: https://github.com/tokio-rs/tokio/pull/7153 [#&#8203;7159]: https://github.com/tokio-rs/tokio/pull/7159 [#&#8203;7160]: https://github.com/tokio-rs/tokio/pull/7160 [#&#8203;7162]: https://github.com/tokio-rs/tokio/pull/7162 [#&#8203;7164]: https://github.com/tokio-rs/tokio/pull/7164 [#&#8203;7166]: https://github.com/tokio-rs/tokio/pull/7166 [#&#8203;7172]: https://github.com/tokio-rs/tokio/pull/7172 [#&#8203;7176]: https://github.com/tokio-rs/tokio/pull/7176 [#&#8203;7185]: https://github.com/tokio-rs/tokio/pull/7185 [#&#8203;7186]: https://github.com/tokio-rs/tokio/pull/7186 [#&#8203;7192]: https://github.com/tokio-rs/tokio/pull/7192 </details> --- ### 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. 👻 **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:eyJjcmVhdGVkSW5WZXIiOiIzNy40MjQuMyIsInVwZGF0ZWRJblZlciI6IjM5LjIxOS4yIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->
kjuulh added 1 commit 2025-02-25 06:31:58 +01:00
fix(deps): update rust crate dagger-sdk to 0.16.0
Some checks failed
renovate/artifacts Artifact file update failure
continuous-integration/drone/push Build is failing
Details
continuous-integration/drone/pr Build is failing
Details
f30c491bae
kjuulh added 1 commit 2025-02-25 06:31:58 +01:00
fix(deps): update rust crate dagger-sdk to 0.16.0
Some checks failed
renovate/artifacts Artifact file update failure
continuous-integration/drone/push Build is failing
Details
continuous-integration/drone/pr Build is failing
Details
f30c491bae
kjuulh force-pushed renovate/all from f30c491bae to 6da0b33fb2 2025-03-04 02:35:26 +01:00 Compare
kjuulh changed title from fix(deps): update rust crate dagger-sdk to 0.16.0 to chore(deps): update all dependencies 2025-03-04 02:35:27 +01:00
kjuulh force-pushed renovate/all from 6da0b33fb2 to bb04827986 2025-03-04 06:33:37 +01:00 Compare
kjuulh changed title from chore(deps): update all dependencies to fix(deps): update all dependencies 2025-03-25 23:49:29 +01:00
kjuulh force-pushed renovate/all from bb04827986 to 9bdc89589e 2025-03-25 23:49:30 +01:00 Compare
kjuulh force-pushed renovate/all from 9bdc89589e to 05a60f2999 2025-03-26 21:00:32 +01:00 Compare
kjuulh force-pushed renovate/all from 05a60f2999 to 22f8c31fc6 2025-03-26 21:34:00 +01:00 Compare
kjuulh force-pushed renovate/all from 22f8c31fc6 to d72fa4879f 2025-03-27 03:00:58 +01:00 Compare
kjuulh commented 2025-03-27 03:33:48 +01:00
Author
Owner
Copy Link

⚠️ 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 ci/Cargo.toml --package dagger-sdk@0.15.4 --precise 0.17.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.17.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 crates/cuddle-rust-service-plan/Cargo.toml --package dagger-sdk@0.15.4 --precise 0.17.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.17.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 ci/Cargo.toml --package dagger-sdk@0.15.4 --precise 0.17.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.17.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 crates/cuddle-rust-service-plan/Cargo.toml --package dagger-sdk@0.15.4 --precise 0.17.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.17.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 force-pushed renovate/all from d72fa4879f to 0e9e435b2b 2025-03-27 03:33:49 +01:00 Compare
Some checks failed
renovate/artifacts Artifact file update failure
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.
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/cuddle-rust-service-plan#59
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?