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

fix(deps): update all dependencies #16

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 +45 -15
kjuulh commented 2025-03-26 21:00:05 +01:00
Owner
Copy Link

This PR contains the following updates:

Package Type Update Change
anyhow workspace.dependencies patch 1.0.97 -> 1.0.98
clap workspace.dependencies patch 4.5.32 -> 4.5.37
dagger-sdk dependencies minor 0.17.1 -> 0.18.0
tokio (source) workspace.dependencies minor 1.44.1 -> 1.45.0

Release Notes

dtolnay/anyhow (anyhow)

v1.0.98

Compare Source

clap-rs/clap (clap)

v4.5.37

Compare Source

Features
  • Added ArgMatches::try_clear_id()

v4.5.36

Compare Source

Fixes
  • (help) Revert 4.5.35's "Don't leave space for shorts if there are none" for now

v4.5.35

Compare Source

Fixes
  • (help) Align positionals and flags when put in the same help_heading
  • (help) Don't leave space for shorts if there are none

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
dagger/dagger (dagger-sdk)

v0.18.6

Compare Source

🔥 Breaking Changes

  • Cache URI-based secrets based on their plaintext value rather than the URI by @​sipsma in https://github.com/dagger/dagger/pull/10311
    Previously, the "cache key" for URI-based secrets (e.g. env://FOO, file:///some/path, etc.) was the URI string. This meant that operations including the secret (e.g. as an environment variable in a Container) would be cached based on the URI value. If two secrets from different clients had the same URI but different plaintext values, cache for operations that include them would be shared.

    In many cases, even when URIs were the same, the plaintext of secrets could be meaningfully different, which made this behavior surprising and lead to unexpected results.

    Now, URI-based secrets are cached based on secure hashes of their plaintext value. Two secrets that have the same URI but different plaintext values will be cached separately, and operations that include them will not share cache.

    However, there are cases where users do want secrets with different plaintexts to share cache, e.g. secrets that rotate in plaintext value frequently but aren't meaningfully different and thus shouldn't bust the cache of operations that include them.

    To continue supporting those use cases, there is a new optional cacheKey argument to Secret that can be used to specify a custom cache key. If provided, the cache key will be used instead of the default plaintext-based cache key, allowing any secrets sharing that cache-key to be cached together.

    SDKs can provide this as an optional argument to the Secret constructor. Other example usages:

    dagger shell:

    • dagger shell -c "some-function --secret-arg $(secret env://FOO --cache-key my-cache-key)"

    dagger call (supports a special syntax that sets the cache key via a query param in the URI):

    • dagger call some-function --secret-arg env://FOO?cacheKey=my-cache-key
Added
Fixed
What to do next?

v0.18.5

Compare Source

Added
Fixed
What to do next?

v0.18.4

Compare Source

Fixed
Experimental
What to do next?

v0.18.3

Compare Source

Added
Fixed
Experimental
What to do next?

v0.18.2

Compare Source

Changed
Fixed
What to do next?

v0.18.1

Compare Source

What to do next?

v0.18.0

Compare Source

Changed
Fixed
What to do next?

v0.17.2

Compare Source

Added
Changed
What to do next?
tokio-rs/tokio (tokio)

v1.45.0: Tokio v1.45.0

Compare Source

Added
  • metrics: stabilize worker_total_busy_duration, worker_park_count, and worker_unpark_count (#​6899, #​7276)
  • process: add Command::spawn_with (#​7249)
Changed
  • io: do not require Unpin for some trait impls (#​7204)
  • rt: mark runtime::Handle as unwind safe (#​7230)
  • time: revert internal sharding implementation (#​7226)
Unstable
  • rt: remove alt multi-threaded runtime (#​7275)

v1.44.2: Tokio v1.44.2

Compare Source

This release fixes a soundness issue in the broadcast channel. The channel
accepts values that are Send but !Sync. Previously, the channel called
clone() on these values without synchronizing. This release fixes the channel
by synchronizing calls to .clone() (Thanks Austin Bonander for finding and
reporting the issue).

Fixed
  • sync: synchronize clone() call in broadcast channel (#​7232)

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.97` -> `1.0.98` | | [clap](https://github.com/clap-rs/clap) | workspace.dependencies | patch | `4.5.32` -> `4.5.37` | | [dagger-sdk](https://github.com/dagger/dagger) | dependencies | minor | `0.17.1` -> `0.18.0` | | [tokio](https://tokio.rs) ([source](https://github.com/tokio-rs/tokio)) | workspace.dependencies | minor | `1.44.1` -> `1.45.0` | --- ### Release Notes <details> <summary>dtolnay/anyhow (anyhow)</summary> ### [`v1.0.98`](https://github.com/dtolnay/anyhow/releases/tag/1.0.98) [Compare Source](https://github.com/dtolnay/anyhow/compare/1.0.97...1.0.98) - Add [`self.into_boxed_dyn_error()`](https://docs.rs/anyhow/1/anyhow/struct.Error.html#method.into_boxed_dyn_error) and [`self.reallocate_into_boxed_dyn_error_without_backtrace()`](https://docs.rs/anyhow/1/anyhow/struct.Error.html#method.reallocate_into_boxed_dyn_error_without_backtrace) methods for anyhow::Error ([#&#8203;415](https://github.com/dtolnay/anyhow/issues/415)) </details> <details> <summary>clap-rs/clap (clap)</summary> ### [`v4.5.37`](https://github.com/clap-rs/clap/blob/HEAD/CHANGELOG.md#4537---2025-04-18) [Compare Source](https://github.com/clap-rs/clap/compare/v4.5.36...v4.5.37) ##### Features - Added `ArgMatches::try_clear_id()` ### [`v4.5.36`](https://github.com/clap-rs/clap/blob/HEAD/CHANGELOG.md#4536---2025-04-11) [Compare Source](https://github.com/clap-rs/clap/compare/v4.5.35...v4.5.36) ##### Fixes - *(help)* Revert 4.5.35's "Don't leave space for shorts if there are none" for now ### [`v4.5.35`](https://github.com/clap-rs/clap/blob/HEAD/CHANGELOG.md#4535---2025-04-01) [Compare Source](https://github.com/clap-rs/clap/compare/v4.5.34...v4.5.35) ##### Fixes - *(help)* Align positionals and flags when put in the same `help_heading` - *(help)* Don't leave space for shorts if there are none ### [`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 </details> <details> <summary>dagger/dagger (dagger-sdk)</summary> ### [`v0.18.6`](https://github.com/dagger/dagger/blob/HEAD/CHANGELOG.md#v0186---2025-05-06) [Compare Source](https://github.com/dagger/dagger/compare/v0.18.5...v0.18.6) ##### 🔥 Breaking Changes - Cache URI-based secrets based on their plaintext value rather than the URI by [@&#8203;sipsma](https://github.com/sipsma) in https://github.com/dagger/dagger/pull/10311 \ Previously, the "cache key" for URI-based secrets (e.g. `env://FOO`, `file:///some/path`, etc.) was the URI string. This meant that operations including the secret (e.g. as an environment variable in a Container) would be cached based on the URI value. If two secrets from different clients had the same URI but different plaintext values, cache for operations that include them would be shared. In many cases, even when URIs were the same, the plaintext of secrets could be meaningfully different, which made this behavior surprising and lead to unexpected results. Now, URI-based secrets are cached based on secure hashes of their plaintext value. Two secrets that have the same URI but different plaintext values will be cached separately, and operations that include them will not share cache. However, there are cases where users do want secrets with different plaintexts to share cache, e.g. secrets that rotate in plaintext value frequently but aren't meaningfully different and thus shouldn't bust the cache of operations that include them. To continue supporting those use cases, there is a new optional `cacheKey` argument to `Secret` that can be used to specify a custom cache key. If provided, the cache key will be used instead of the default plaintext-based cache key, allowing any secrets sharing that cache-key to be cached together. SDKs can provide this as an optional argument to the `Secret` constructor. Other example usages: dagger shell: - `dagger shell -c "some-function --secret-arg $(secret env://FOO --cache-key my-cache-key)"` dagger call (supports a special syntax that sets the cache key via a query param in the URI): - `dagger call some-function --secret-arg env://FOO?cacheKey=my-cache-key` ##### Added - New `GitRepository.branches` API by [@&#8203;jedevc](https://github.com/jedevc) in https://github.com/dagger/dagger/pull/10250 - New `File` top-level field added to allow easier creation of `File` objects by [@&#8203;jedevc](https://github.com/jedevc) in https://github.com/dagger/dagger/pull/10290 ##### Fixed - `GitRepository.tags` `patterns` arg is now respected for local git repositories by [@&#8203;jedevc](https://github.com/jedevc) in https://github.com/dagger/dagger/pull/10250 - Return an error when a function argument conflicts with a persistent flag in `dagger call` by [@&#8203;helderco](https://github.com/helderco) in https://github.com/dagger/dagger/pull/10305 - Fix "failed to return error" and "failed to emit telemetry" errors when two identical functions execute at the same time and one client cancels the request by [@&#8203;sipsma](https://github.com/sipsma) in https://github.com/dagger/dagger/pull/10264 - Fix panic in vault secret provider when path exists but secret doesn't by [@&#8203;sipsma](https://github.com/sipsma) in https://github.com/dagger/dagger/pull/10311 - Fix panic when using `Container.build` with a Dockerfile that is `FROM scratch` by [@&#8203;sipsma](https://github.com/sipsma) in https://github.com/dagger/dagger/pull/10332 ##### 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.18.5`](https://github.com/dagger/dagger/blob/HEAD/CHANGELOG.md#v0185---2025-04-25) [Compare Source](https://github.com/dagger/dagger/compare/v0.18.4...v0.18.5) ##### Added - New `depth` arg to `GitRef.tree` to control the depth of a clone by [@&#8203;jedevc](https://github.com/jedevc) in https://github.com/dagger/dagger/pull/9980 - New `GitRef.ref` field for resolving the full ref string for a reference by [@&#8203;jedevc](https://github.com/jedevc) in https://github.com/dagger/dagger/pull/9980 ##### Fixed - Ensure consistent git state in `Git.tree` checkouts by [@&#8203;jedevc](https://github.com/jedevc) in https://github.com/dagger/dagger/pull/9980 - Fix cache invalidation of `withExec` when secrets created by `SetSecret` in function calls are included by [@&#8203;sipsma](https://github.com/sipsma) in https://github.com/dagger/dagger/pull/10260 - Fix handling of optional args in LLM by [@&#8203;vito](https://github.com/vito) in https://github.com/dagger/dagger/pull/10254 - Fix handling of Python SDK modules using requirements.lock by [@&#8203;helderco](https://github.com/helderco) in https://github.com/dagger/dagger/pull/10252 ##### 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.18.4`](https://github.com/dagger/dagger/blob/HEAD/CHANGELOG.md#v0184---2025-04-22) [Compare Source](https://github.com/dagger/dagger/compare/v0.18.3...v0.18.4) ##### Fixed - shell: fixed relative paths in `Directory` and `File` flags by [@&#8203;helderco](https://github.com/helderco) in https://github.com/dagger/dagger/pull/10169 - Fix re-use of LLM config from other concurrently running dagger sessions by [@&#8203;sipsma](https://github.com/sipsma) in https://github.com/dagger/dagger/pull/10184 - Fix "session not found" errors when invoking modules by [@&#8203;sipsma](https://github.com/sipsma) in https://github.com/dagger/dagger/pull/10168 - Fix errors using `CurrentModule` API during SDK module initialization by [@&#8203;sipsma](https://github.com/sipsma) in https://github.com/dagger/dagger/pull/10213 - Fix caching of contextual directory args when multiple clients invoking the same function by [@&#8203;sipsma](https://github.com/sipsma) in https://github.com/dagger/dagger/pull/10187 - Fix "client not found" errors when loading cached modules from private repos by [@&#8203;sipsma](https://github.com/sipsma) in https://github.com/dagger/dagger/pull/10223 - Fix API authentication errors when calling `llm.withModel` from a module function by [@&#8203;sipsma](https://github.com/sipsma) in https://github.com/dagger/dagger/pull/10230 - Fix "buildkit session not found" errors when calling `.plaintext` on a URI-based secret from a module w/ cache hit by [@&#8203;sipsma](https://github.com/sipsma) in https://github.com/dagger/dagger/pull/10223 - Fixed error when `setSecret` provided empty plaintext value and passed between function calls by [@&#8203;sipsma](https://github.com/sipsma) in https://github.com/dagger/dagger/pull/10223 ##### Experimental - Experimental API methods are now all marked as such by [@&#8203;jedevc](https://github.com/jedevc) in https://github.com/dagger/dagger/pull/10058 ##### 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.18.3`](https://github.com/dagger/dagger/blob/HEAD/CHANGELOG.md#v0183---2025-04-14) [Compare Source](https://github.com/dagger/dagger/compare/v0.18.2...v0.18.3) ##### Added - New `--recursive` flag for `dagger develop` by [@&#8203;jedevc](https://github.com/jedevc) in https://github.com/dagger/dagger/pull/9860 - Add the ability to load a module without specifying an SDK by [@&#8203;grouville](https://github.com/grouville) and [@&#8203;tiborvass](https://github.com/tiborvass) in https://github.com/dagger/dagger/pull/9984 - Add support for skipping automatic init process when using `Container.build` and `Directory.dockerBuild` by [@&#8203;sipsma](https://github.com/sipsma) in https://github.com/dagger/dagger/pull/10088 - Allow specifying `ttl` for local secret caching for vault by [@&#8203;rajatjindal](https://github.com/rajatjindal) in https://github.com/dagger/dagger/pull/9997 ##### Fixed - Fix error when parsing multi-line git config files by [@&#8203;marcosnils](https://github.com/marcosnils) in https://github.com/dagger/dagger/pull/10087 - Fix edge-case panic when attempting shell completion by [@&#8203;kasattejaswi](https://github.com/kasattejaswi) in https://github.com/dagger/dagger/pull/10125 ##### Experimental - Expose Dagger Core API as MCP tools by [@&#8203;grouville](https://github.com/grouville) and [@&#8203;tiborvass](https://github.com/tiborvass) in https://github.com/dagger/dagger/pull/10090 ##### 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.18.2`](https://github.com/dagger/dagger/blob/HEAD/CHANGELOG.md#v0182---2025-04-04) [Compare Source](https://github.com/dagger/dagger/compare/v0.18.1...v0.18.2) ##### Changed - shell: skip CSV flag parsing when spreading `with-exec` positional arguments by [@&#8203;helderco](https://github.com/helderco) in https://github.com/dagger/dagger/pull/10063 ##### Fixed - client: bump min connect timeout to 10s by [@&#8203;marcosnils](https://github.com/marcosnils) https://github.com/dagger/dagger/pull/10070 ##### 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.18.1`](https://github.com/dagger/dagger/blob/HEAD/CHANGELOG.md#v0181---2025-04-01) [Compare Source](https://github.com/dagger/dagger/compare/v0.18.0...v0.18.1) ##### 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.18.0`](https://github.com/dagger/dagger/blob/HEAD/CHANGELOG.md#v0180---2025-03-31) [Compare Source](https://github.com/dagger/dagger/compare/v0.17.2...v0.18.0) ##### Changed - use dockerignore files during docker build by [@&#8203;rajatjindal](https://github.com/rajatjindal) in https://github.com/dagger/dagger/pull/9857 ##### Fixed - Fixed an issue when reusing a variable with a pipeline, in the same run by [@&#8203;helderco](https://github.com/helderco) in https://github.com/dagger/dagger/pull/10018 - Fixed executing a dagger shell script from the root command by [@&#8203;helderco](https://github.com/helderco) in https://github.com/dagger/dagger/pull/10020 ##### 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.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) </details> <details> <summary>tokio-rs/tokio (tokio)</summary> ### [`v1.45.0`](https://github.com/tokio-rs/tokio/releases/tag/tokio-1.45.0): Tokio v1.45.0 [Compare Source](https://github.com/tokio-rs/tokio/compare/tokio-1.44.2...tokio-1.45.0) ##### Added - metrics: stabilize `worker_total_busy_duration`, `worker_park_count`, and `worker_unpark_count` ([#&#8203;6899], [#&#8203;7276]) - process: add `Command::spawn_with` ([#&#8203;7249]) ##### Changed - io: do not require `Unpin` for some trait impls ([#&#8203;7204]) - rt: mark `runtime::Handle` as unwind safe ([#&#8203;7230]) - time: revert internal sharding implementation ([#&#8203;7226]) ##### Unstable - rt: remove alt multi-threaded runtime ([#&#8203;7275]) [#&#8203;6899]: https://github.com/tokio-rs/tokio/pull/6899 [#&#8203;7276]: https://github.com/tokio-rs/tokio/pull/7276 [#&#8203;7249]: https://github.com/tokio-rs/tokio/pull/7249 [#&#8203;7204]: https://github.com/tokio-rs/tokio/pull/7204 [#&#8203;7230]: https://github.com/tokio-rs/tokio/pull/7230 [#&#8203;7226]: https://github.com/tokio-rs/tokio/pull/7226 [#&#8203;7275]: https://github.com/tokio-rs/tokio/pull/7275 ### [`v1.44.2`](https://github.com/tokio-rs/tokio/releases/tag/tokio-1.44.2): Tokio v1.44.2 [Compare Source](https://github.com/tokio-rs/tokio/compare/tokio-1.44.1...tokio-1.44.2) This release fixes a soundness issue in the broadcast channel. The channel accepts values that are `Send` but `!Sync`. Previously, the channel called `clone()` on these values without synchronizing. This release fixes the channel by synchronizing calls to `.clone()` (Thanks Austin Bonander for finding and reporting the issue). ##### Fixed - sync: synchronize `clone()` call in broadcast channel ([#&#8203;7232]) [#&#8203;7232]: https://github.com/tokio-rs/tokio/pull/7232 </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:eyJjcmVhdGVkSW5WZXIiOiIzOS4yMTguMSIsInVwZGF0ZWRJblZlciI6IjM5LjI2NC4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->
kjuulh added 1 commit 2025-03-26 21:00:05 +01:00
kjuulh changed title from chore(deps): update rust crate clap to v4.5.33 to chore(deps): update rust crate clap to v4.5.34 2025-03-27 03:00:35 +01:00
kjuulh force-pushed renovate/all from 91080a96fa to 59a02f69ff 2025-03-27 03:00:37 +01:00 Compare
kjuulh changed title from chore(deps): update rust crate clap to v4.5.34 to fix(deps): update all dependencies 2025-03-27 16:59:04 +01:00
kjuulh force-pushed renovate/all from 59a02f69ff to 1420142503 2025-03-27 16:59:05 +01:00 Compare
kjuulh force-pushed renovate/all from 1420142503 to 7f8c9ad7e7 2025-03-27 17:29:44 +01:00 Compare
kjuulh force-pushed renovate/all from 7f8c9ad7e7 to 8cd650fad5 2025-03-27 18:01:00 +01:00 Compare
kjuulh force-pushed renovate/all from 8cd650fad5 to e4672c1b22 2025-03-27 18:31:53 +01:00 Compare
kjuulh force-pushed renovate/all from e4672c1b22 to 59bc31de87 2025-03-27 19:02:05 +01:00 Compare
kjuulh force-pushed renovate/all from 59bc31de87 to b538199cae 2025-03-27 19:30:18 +01:00 Compare
kjuulh force-pushed renovate/all from b538199cae to f787bd730b 2025-03-27 19:59:39 +01:00 Compare
kjuulh force-pushed renovate/all from f787bd730b to 6f0bfecc74 2025-03-27 20:28:05 +01:00 Compare
kjuulh force-pushed renovate/all from 6f0bfecc74 to b35813bf7a 2025-03-27 20:57:51 +01:00 Compare
kjuulh force-pushed renovate/all from b35813bf7a to 052de92da2 2025-03-27 21:26:26 +01:00 Compare
kjuulh force-pushed renovate/all from 052de92da2 to eb358b6b07 2025-03-27 21:57:03 +01:00 Compare
kjuulh force-pushed renovate/all from eb358b6b07 to 89f86e7e2f 2025-03-28 23:23:51 +01:00 Compare
kjuulh force-pushed renovate/all from 89f86e7e2f to bff0171547 2025-03-29 02:18:58 +01:00 Compare
kjuulh force-pushed renovate/all from bff0171547 to 423f04cb6a 2025-03-29 05:19:31 +01:00 Compare
kjuulh force-pushed renovate/all from 423f04cb6a to 0e209c9620 2025-03-30 05:20:17 +02:00 Compare
kjuulh force-pushed renovate/all from 0e209c9620 to 8576e77d0a 2025-03-31 02:18:32 +02:00 Compare
kjuulh force-pushed renovate/all from 8576e77d0a to 61d9a0f97b 2025-03-31 05:19:03 +02:00 Compare
kjuulh force-pushed renovate/all from 61d9a0f97b to 304c7dd058 2025-04-01 02:19:29 +02:00 Compare
kjuulh force-pushed renovate/all from 304c7dd058 to cc4435a6f2 2025-04-01 05:19:38 +02:00 Compare
kjuulh force-pushed renovate/all from cc4435a6f2 to f828d210ea 2025-04-02 02:22:05 +02:00 Compare
kjuulh force-pushed renovate/all from f828d210ea to 13d92fc021 2025-04-06 02:19:53 +02:00 Compare
kjuulh force-pushed renovate/all from 13d92fc021 to e1f3acfc4f 2025-04-06 05:20:41 +02:00 Compare
kjuulh force-pushed renovate/all from e1f3acfc4f to 28c92f9e8b 2025-04-12 02:22:13 +02:00 Compare
kjuulh force-pushed renovate/all from 28c92f9e8b to 0a12f36fdb 2025-04-12 05:20:43 +02:00 Compare
kjuulh force-pushed renovate/all from 0a12f36fdb to 1e90c2b622 2025-04-14 05:20:40 +02:00 Compare
kjuulh force-pushed renovate/all from 1e90c2b622 to 0b580069c4 2025-04-15 02:22:42 +02:00 Compare
kjuulh force-pushed renovate/all from 0b580069c4 to c7a9b20933 2025-04-19 02:20:39 +02:00 Compare
kjuulh force-pushed renovate/all from c7a9b20933 to 3855cc1457 2025-04-19 05:20:47 +02:00 Compare
kjuulh force-pushed renovate/all from 3855cc1457 to 75acc9c93c 2025-05-07 02:21:15 +02:00 Compare
kjuulh commented 2025-05-07 05:20:51 +02: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.17.1 --precise 0.18.6
    Updating crates.io index
error: failed to select a version for the requirement `dagger-sdk = "^0.17.1"`
candidate versions found which didn't match: 0.18.6
location searched: crates.io index
required by package `cuddle-ci v0.3.0 (https://git.front.kjuulh.io/kjuulh/dagger-components?branch=main#2e714767)`
    ... which satisfies git dependency `cuddle-ci` (locked to 0.3.0) of package `cuddle-rust-cli-plan v0.1.0 (/tmp/renovate/repos/gitea/kjuulh/cuddle-rust-cli-plan/crates/cuddle-rust-cli-plan)`
File name: Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path crates/cuddle-rust-cli-plan/Cargo.toml --package dagger-sdk@0.17.1 --precise 0.18.6
    Updating crates.io index
error: failed to select a version for the requirement `dagger-sdk = "^0.17.1"`
candidate versions found which didn't match: 0.18.6
location searched: crates.io index
required by package `cuddle-ci v0.3.0 (https://git.front.kjuulh.io/kjuulh/dagger-components?branch=main#2e714767)`
    ... which satisfies git dependency `cuddle-ci` (locked to 0.3.0) of package `cuddle-rust-cli-plan v0.1.0 (/tmp/renovate/repos/gitea/kjuulh/cuddle-rust-cli-plan/crates/cuddle-rust-cli-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.17.1 --precise 0.18.6 Updating crates.io index error: failed to select a version for the requirement `dagger-sdk = "^0.17.1"` candidate versions found which didn't match: 0.18.6 location searched: crates.io index required by package `cuddle-ci v0.3.0 (https://git.front.kjuulh.io/kjuulh/dagger-components?branch=main#2e714767)` ... which satisfies git dependency `cuddle-ci` (locked to 0.3.0) of package `cuddle-rust-cli-plan v0.1.0 (/tmp/renovate/repos/gitea/kjuulh/cuddle-rust-cli-plan/crates/cuddle-rust-cli-plan)` ``` ##### File name: Cargo.lock ``` Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path crates/cuddle-rust-cli-plan/Cargo.toml --package dagger-sdk@0.17.1 --precise 0.18.6 Updating crates.io index error: failed to select a version for the requirement `dagger-sdk = "^0.17.1"` candidate versions found which didn't match: 0.18.6 location searched: crates.io index required by package `cuddle-ci v0.3.0 (https://git.front.kjuulh.io/kjuulh/dagger-components?branch=main#2e714767)` ... which satisfies git dependency `cuddle-ci` (locked to 0.3.0) of package `cuddle-rust-cli-plan v0.1.0 (/tmp/renovate/repos/gitea/kjuulh/cuddle-rust-cli-plan/crates/cuddle-rust-cli-plan)` ```
kjuulh force-pushed renovate/all from 75acc9c93c to d57e30898d 2025-05-07 05:20:52 +02: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
kjuulh
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: kjuulh/cuddle-rust-cli-plan#16
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?