chore: release v0.4.4 #597

Open

jalil wants to merge 1 commit from release-plz-2025-12-26T14-38-22Z into main

pull from: release-plz-2025-12-26T14-38-22Z

merge into: jalil:main

jalil:main

jalil:release-plz-2025-11-10T21-06-59Z

jalil:push-yzyrkwyqprvk

jalil:release-plz-2025-08-29T15-04-46Z

Conversation 1 Commits 1 Files changed 3 +10 -2

jalil commented 2025-12-26 15:38:22 +01:00

Owner

Copy link

🤖 New release

• webnsupdate: 0.4.3 -> 0.4.4

Changelog

[0.4.4] - 2026-01-06

⚙️ Miscellaneous Tasks

• Update Cargo.lock dependencies

---

This PR was generated with release-plz.

## 🤖 New release * `webnsupdate`: 0.4.3 -> 0.4.4 <details><summary><i><b>Changelog</b></i></summary><p> <blockquote> ## [0.4.4] - 2026-01-06 ### ⚙️ Miscellaneous Tasks - Update Cargo.lock dependencies <!-- generated by git-cliff --> </blockquote> </p></details> --- This PR was generated with [release-plz](https://github.com/release-plz/release-plz/).

jalil added 1 commit 2025-12-26 15:38:22 +01:00

chore: release v0.4.4 ... 3109ae7742

Signed-off-by: Dynamic User <gitea-runner@taurus.fritz.box>

jalil added the

release

label 2025-12-26 15:38:22 +01:00

forgejo-actions commented 2025-12-26 15:39:15 +01:00

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/Home-Manager 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	44MiB	44MiB	2.1MiB	2.1MiB
release-script	408MiB	408MiB	1.4KiB	1.4KiB
webnsupdate	44MiB	0B	2.1MiB	0B

<!-- AUTOGENERATED by nix-flake-outputs-size action --> ## 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/Home-Manager 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` | 44MiB | 44MiB | 2.1MiB | 2.1MiB | | `release-script` | 408MiB | 408MiB | 1.4KiB | 1.4KiB | | `webnsupdate` | 44MiB | 0B | 2.1MiB | 0B |

jalil force-pushed release-plz-2025-12-26T14-38-22Z from 3109ae7742 to 20d38c2474 2025-12-26 15:42:34 +01:00 Compare

jalil force-pushed release-plz-2025-12-26T14-38-22Z from 20d38c2474 to 650cbd78ce 2025-12-27 03:12:41 +01:00 Compare

jalil force-pushed release-plz-2025-12-26T14-38-22Z from 650cbd78ce to dab59d5d8b 2025-12-27 19:42:29 +01:00 Compare

jalil force-pushed release-plz-2025-12-26T14-38-22Z from dab59d5d8b to b59f659a9d 2025-12-28 13:22:39 +01:00 Compare

jalil force-pushed release-plz-2025-12-26T14-38-22Z from b59f659a9d to 88f270c2be 2025-12-29 00:12:52 +01:00 Compare

jalil force-pushed release-plz-2025-12-26T14-38-22Z from 88f270c2be to 4cf97f025b 2025-12-29 02:14:51 +01:00 Compare

jalil force-pushed release-plz-2025-12-26T14-38-22Z from 4cf97f025b to 6d75ad47af 2025-12-29 10:59:58 +01:00 Compare

jalil force-pushed release-plz-2025-12-26T14-38-22Z from 6d75ad47af to 25bd3c1099 2025-12-29 11:03:37 +01:00 Compare

jalil force-pushed release-plz-2025-12-26T14-38-22Z from 25bd3c1099 to e59ff49ba5 2025-12-30 03:52:38 +01:00 Compare

jalil force-pushed release-plz-2025-12-26T14-38-22Z from e59ff49ba5 to b32c71712a 2025-12-30 10:22:33 +01:00 Compare

jalil force-pushed release-plz-2025-12-26T14-38-22Z from b32c71712a to c4fdd6a251 2025-12-30 10:44:22 +01:00 Compare

jalil force-pushed release-plz-2025-12-26T14-38-22Z from c4fdd6a251 to a9930d0969 2025-12-31 02:22:35 +01:00 Compare

jalil force-pushed release-plz-2025-12-26T14-38-22Z from a9930d0969 to a1d35f6678 2026-01-01 14:52:39 +01:00 Compare

jalil force-pushed release-plz-2025-12-26T14-38-22Z from a1d35f6678 to 58181b9f46 2026-01-02 12:22:38 +01:00 Compare

jalil force-pushed release-plz-2025-12-26T14-38-22Z from 58181b9f46 to ffd874b6d0 2026-01-05 00:28:52 +01:00 Compare

jalil force-pushed release-plz-2025-12-26T14-38-22Z from ffd874b6d0 to 70f5ce86f6 2026-01-05 02:42:50 +01:00 Compare

jalil force-pushed release-plz-2025-12-26T14-38-22Z from 70f5ce86f6 to af05fee0c4 2026-01-05 17:14:17 +01:00 Compare

jalil force-pushed release-plz-2025-12-26T14-38-22Z from af05fee0c4 to d52c3130d4 2026-01-06 16:42:51 +01:00 Compare

jalil force-pushed release-plz-2025-12-26T14-38-22Z from d52c3130d4 to ef2dab03ca 2026-01-06 17:52:46 +01:00 Compare

All checks were successful

Hide all checks

/ build (pull_request) Successful in 2s

Required

Details

/ checks (x86_64-linux, clippy) (pull_request) Successful in 2s

Required

Details

/ checks (x86_64-linux, deny) (pull_request) Successful in 2s

Required

Details

/ checks (x86_64-linux, module-ipv4-only-test) (pull_request) Successful in 4s

Required

Details

/ checks (x86_64-linux, module-ipv4-test) (pull_request) Successful in 4s

Required

Details

/ checks (x86_64-linux, module-ipv6-only-test) (pull_request) Successful in 5s

Required

Details

/ checks (x86_64-linux, module-ipv6-test) (pull_request) Successful in 4s

Required

Details

/ checks (x86_64-linux, module-nginx-test) (pull_request) Successful in 5s

Required

Details

/ checks (x86_64-linux, nextest) (pull_request) Successful in 2s

Required

Details

/ checks (x86_64-linux, treefmt) (pull_request) Successful in 2s

Required

Details

/ trigger-release (pull_request) Successful in 18s

Required

Details

/ report-size (pull_request) Successful in 15s

Required

Details

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 release-plz-2025-12-26T14-38-22Z:release-plz-2025-12-26T14-38-22Z

git switch release-plz-2025-12-26T14-38-22Z

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels   

bug

Something is not working

  

chore

Cleanup/trivial updates

  

duplicate

This issue or pull request already exists

  

enhancement

New feature

  

help wanted

Need some help

  

invalid

Something is wrong

  

question

More information is needed

  

release

A PR created by `release-plz`

  

wontfix

This won't be fixed

No labels

bug

chore

duplicate

enhancement

help wanted

invalid

question

release

wontfix

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

2 participants

Notifications

Subscribe

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/webnsupdate!597

No description provided.