jalil/webnsupdate

Fork 0

chore(deps): lock file maintenance #237

Merged

renovate merged 1 commit from renovate/lock-file-maintenance into main

2025-05-16 22:00:52 +02:00

renovate commented

2025-05-16 22:00:25 +02:00

Collaborator

This PR contains the following updates:

Update	Change
lockFileMaintenance	All locks refreshed

🔧 This Pull Request updates lock files to use the latest dependency versions.

Configuration

📅 Schedule: Branch creation - Between 10:00 PM and 10:59 PM ( * 22 * * * ) (UTC), Automerge - Between 11:00 PM and 11:59 PM ( * 23 * * * ) (UTC).

🚦 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: | Update | Change | |---|---| | lockFileMaintenance | All locks refreshed | 🔧 This Pull Request updates lock files to use the latest dependency versions. --- ### Configuration 📅 **Schedule**: Branch creation - Between 10:00 PM and 10:59 PM ( * 22 * * * ) (UTC), Automerge - Between 11:00 PM and 11:59 PM ( * 23 * * * ) (UTC). 🚦 **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. --- - [ ] 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 added 1 commit 2025-05-16 22:00:25 +02:00

chore(deps): lock file maintenance

renovate/artifacts Artifact file update failure

/ build (push) Successful in 1s

Details

/ check-integration-tests (push) Successful in 10s

Details

/ report-size (push) Successful in 1s

Details

7ea209ca66

renovate scheduled this pull request to auto merge when all checks succeed 2025-05-16 22:00:25 +02:00

renovate commented

2025-05-16 22:00:25 +02:00

Author

Collaborator

⚠️ Artifact update problem

Renovate failed to update an artifact 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 Cargo.toml
error: failed to parse manifest at `/var/lib/private/renovate/repos/gitea/jalil/webnsupdate/Cargo.toml`

Caused by:
  feature `edition2024` is required

  The package requires the Cargo feature called `edition2024`, but that feature is not stabilized in this version of Cargo (1.82.0 (8f40fc59f 2024-08-21)).
  Consider adding `cargo-features = ["edition2024"]` to the top of Cargo.toml (above the [package] table) to tell Cargo you are opting in to use this unstable feature.
  See https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#edition-2024 for more information about the status of this feature.

### ⚠️ Artifact update problem Renovate failed to update an artifact 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 Cargo.toml error: failed to parse manifest at `/var/lib/private/renovate/repos/gitea/jalil/webnsupdate/Cargo.toml` Caused by: feature `edition2024` is required The package requires the Cargo feature called `edition2024`, but that feature is not stabilized in this version of Cargo (1.82.0 (8f40fc59f 2024-08-21)). Consider adding `cargo-features = ["edition2024"]` to the top of Cargo.toml (above the [package] table) to tell Cargo you are opting in to use this unstable feature. See https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#edition-2024 for more information about the status of this feature. ```

forgejo-actions commented

2025-05-16 22:00:49 +02:00

Flake output sizes

Definitions

Name: the name of the package/configuration.
Size: the closure size (size on disk/NAR size + all transitive dependencies).
NAR Size: the size of the build output (package without the dependencies).
[NAR] Size Change: the amount changed compared to the main branch.

Tips on reading this data

For NixOS configurations you generally care only about the Size (closure size/size on disk).
- Reduce the Size by disabling unneeded services/default packages.
For Packages you care about both the Size and the NAR Size.
- Reduce the NAR Size by reducing the size of the build outputs, e.g. don't copy unnecessary data to the $out dir, optimize binaries for size, etc.
- Reduce the Size by reducing the dependencies (e.g. buildInputs).
- Don't worry too much about size, some dependencies are deduplicated, e.g. glibc adds ~40MiB to the Size, but is generally shared by ~every binary on the system, so, chances are, you are already including it from somewhere else and statically linking with e.g. musl is not gonna improve things.

Packages

Name	Size	Size Change	NAR Size	NAR Size Change
`default`	35MiB	0B	2.9MiB	0B
`git-cliff`	60MiB	0B	19MiB	0B
`webnsupdate`	35MiB	0B	2.9MiB	0B

## Flake output sizes <details><summary><b>Definitions</b></summary> - `Name`: the name of the package/configuration. - `Size`: the closure size (size on disk/NAR size + all transitive dependencies). - `NAR Size`: the size of the build output (package without the dependencies). - `[NAR] Size Change`: the amount changed compared to the main branch. </details> <details><summary><b>Tips on reading this data</b></summary> - For NixOS configurations you generally care only about the `Size` (closure size/size on disk). - Reduce the `Size` by disabling unneeded services/default packages. - For Packages you care about both the `Size` and the `NAR Size`. - Reduce the `NAR Size` by reducing the size of the build outputs, e.g. don't copy unnecessary data to the $out dir, optimize binaries for size, etc. - Reduce the `Size` by reducing the dependencies (e.g. `buildInputs`). - Don't worry too much about size, some dependencies are deduplicated, e.g. `glibc` adds ~40MiB to the `Size`, but is generally shared by ~every binary on the system, so, chances are, you are already including it from somewhere else and statically linking with e.g. `musl` is not gonna improve things. </details> ## Packages | Name | Size | Size Change | NAR Size | NAR Size Change | |------|-----:|------------:|---------:|----------------:| | `default` | 35MiB | 0B | 2.9MiB | 0B | | `git-cliff` | 60MiB | 0B | 19MiB | 0B | | `webnsupdate` | 35MiB | 0B | 2.9MiB | 0B |

renovate merged commit 7ea209ca66 into main

2025-05-16 22:00:52 +02:00

renovate deleted branch renovate/lock-file-maintenance

2025-05-16 22:00:52 +02:00