jalil/configuration.nix
1
1
Fork 0
Code Issues 2 Pull requests Projects Activity Actions

fix(deps): update rust crate serde to v1.0.217 #212

Merged
renovate merged 1 commit from renovate/serde-monorepo into main 2024-12-31 09:42:39 +01:00
Conversation 2 Commits 1 Files changed 1 +4 -4
renovate commented 2024-12-31 09:30:10 +01:00
Collaborator
Copy link

This PR contains the following updates:

Package Type Update Change
serde (source) dependencies patch 1.0.216 -> 1.0.217

❗ Important

Release Notes retrieval for this PR were skipped because no github.com credentials were available.
If you are self-hosted, please see this instruction.

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - "* 1-2 * * *" (UTC).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • 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 | |---|---|---|---| | [serde](https://serde.rs) ([source](https://github.com/serde-rs/serde)) | dependencies | patch | `1.0.216` -> `1.0.217` | > :exclamation: **Important** > > Release Notes retrieval for this PR were skipped because no github.com credentials were available. > If you are self-hosted, please see [this instruction](https://github.com/renovatebot/renovate/blob/master/docs/usage/examples/self-hosting.md#githubcom-token-for-release-notes). --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - "* 1-2 * * *" (UTC). 🚦 **Automerge**: Enabled. ♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- 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:eyJjcmVhdGVkSW5WZXIiOiIzOC4xMDUuMiIsInVwZGF0ZWRJblZlciI6IjM4LjEwNS4yIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->
renovate added 1 commit 2024-12-31 09:30:10 +01:00
fix(deps): update rust crate serde to v1.0.217
All checks were successful
/ check (nvimDev) (push) Successful in 8s
Details
/ check (nvimHeadless) (push) Successful in 3s
Details
/ check (nvimNoBundledBins) (push) Successful in 4s
Details
/ check (nvimNoLsp) (push) Successful in 4s
Details
/ check (nvimNoTSGrammars) (push) Successful in 4s
Details
/ check (treefmt) (push) Successful in 3s
Details
/ build (audiomenu) (push) Successful in 40s
Details
/ build (docs) (push) Successful in 2s
Details
/ build (jpassmenu) (push) Successful in 2s
Details
/ build (nixosConfigurations.vm.config.system.build.toplevel) (push) Successful in 23s
Details
/ build (nvim) (push) Successful in 9s
Details
/ report-size (push) Successful in 1m4s
Details
23c008804d 
| datasource | package | from    | to      |
| ---------- | ------- | ------- | ------- |
| crate      | serde   | 1.0.216 | 1.0.217 |
renovate scheduled this pull request to auto merge when all checks succeed 2024-12-31 09:30:10 +01:00
forgejo-actions commented 2024-12-31 09:38:39 +01:00
First-time contributor
Copy link

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.

NixOS Configurations

Name Size Size Change NAR Size NAR Size Change
vm 10GiB 632B 19KiB 0B

Packages

Name Size Size Change NAR Size NAR Size Change
audiomenu 42MiB 632B 1.4MiB 632B
docs 2.4MiB 0B 2.4MiB 0B
docs-home-markdown 11KiB 0B 11KiB 0B
docs-nixos-markdown 6.3KiB 0B 6.3KiB 0B
docs-nvim-markdown 1.9KiB 0B 1.9KiB 0B
jpassmenu 43MiB 0B 2.3MiB 0B
nvim 2.1GiB 0B 579KiB 0B
nvim-headless 616MiB 0B 579KiB 0B
nvim-no-lsps 1.1GiB 0B 579KiB 0B
nvim-no-ts 2.1GiB 0B 579KiB 0B
nvim-small 1.3GiB 0B 579KiB 0B
# 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. # NixOS Configurations | Name | Size | Size Change | NAR Size | NAR Size Change | |------|-----:|------------:|---------:|----------------:| | `vm` | 10GiB | 632B | 19KiB | 0B | # Packages | Name | Size | Size Change | NAR Size | NAR Size Change | |------|-----:|------------:|---------:|----------------:| | `audiomenu` | 42MiB | 632B | 1.4MiB | 632B | | `docs` | 2.4MiB | 0B | 2.4MiB | 0B | | `docs-home-markdown` | 11KiB | 0B | 11KiB | 0B | | `docs-nixos-markdown` | 6.3KiB | 0B | 6.3KiB | 0B | | `docs-nvim-markdown` | 1.9KiB | 0B | 1.9KiB | 0B | | `jpassmenu` | 43MiB | 0B | 2.3MiB | 0B | | `nvim` | 2.1GiB | 0B | 579KiB | 0B | | `nvim-headless` | 616MiB | 0B | 579KiB | 0B | | `nvim-no-lsps` | 1.1GiB | 0B | 579KiB | 0B | | `nvim-no-ts` | 2.1GiB | 0B | 579KiB | 0B | | `nvim-small` | 1.3GiB | 0B | 579KiB | 0B |
renovate force-pushed renovate/serde-monorepo from 23c008804d to 8247c003cc 2024-12-31 09:40:12 +01:00 Compare
forgejo-actions commented 2024-12-31 09:42:37 +01:00
First-time contributor
Copy link

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.

NixOS Configurations

Name Size Size Change NAR Size NAR Size Change
vm 10GiB 632B 19KiB 0B

Packages

Name Size Size Change NAR Size NAR Size Change
audiomenu 42MiB 632B 1.4MiB 632B
docs 2.4MiB 0B 2.4MiB 0B
docs-home-markdown 11KiB 0B 11KiB 0B
docs-nixos-markdown 6.3KiB 0B 6.3KiB 0B
docs-nvim-markdown 1.9KiB 0B 1.9KiB 0B
jpassmenu 43MiB 0B 2.3MiB 0B
nvim 2.1GiB 0B 579KiB 0B
nvim-headless 616MiB 0B 579KiB 0B
nvim-no-lsps 1.1GiB 0B 579KiB 0B
nvim-no-ts 2.1GiB 0B 579KiB 0B
nvim-small 1.3GiB 0B 579KiB 0B
# 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. # NixOS Configurations | Name | Size | Size Change | NAR Size | NAR Size Change | |------|-----:|------------:|---------:|----------------:| | `vm` | 10GiB | 632B | 19KiB | 0B | # Packages | Name | Size | Size Change | NAR Size | NAR Size Change | |------|-----:|------------:|---------:|----------------:| | `audiomenu` | 42MiB | 632B | 1.4MiB | 632B | | `docs` | 2.4MiB | 0B | 2.4MiB | 0B | | `docs-home-markdown` | 11KiB | 0B | 11KiB | 0B | | `docs-nixos-markdown` | 6.3KiB | 0B | 6.3KiB | 0B | | `docs-nvim-markdown` | 1.9KiB | 0B | 1.9KiB | 0B | | `jpassmenu` | 43MiB | 0B | 2.3MiB | 0B | | `nvim` | 2.1GiB | 0B | 579KiB | 0B | | `nvim-headless` | 616MiB | 0B | 579KiB | 0B | | `nvim-no-lsps` | 1.1GiB | 0B | 579KiB | 0B | | `nvim-no-ts` | 2.1GiB | 0B | 579KiB | 0B | | `nvim-small` | 1.3GiB | 0B | 579KiB | 0B |
renovate merged commit 8247c003cc into main 2024-12-31 09:42:39 +01:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: jalil/configuration.nix#212
No description provided.
Delete branch "renovate/serde-monorepo"

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?