jalil/webnsupdate
1
1
Fork 0
Code Issues 1 Pull requests 4 Releases 1 Packages 1 Activity Actions

chore: release v0.3.8 #406

Open
jalil wants to merge 1 commit from release-plz-2025-08-30T20-04-41Z into main
pull from: release-plz-2025-08-30T20-04-41Z
merge into: jalil:main
Conversation 1 Commits 1 Files changed 3 +21 -2
jalil commented 2025-08-30 22:04:41 +02:00
Owner
Copy link

🤖 New release

  • webnsupdate: 0.3.7 -> 0.3.8
Changelog

[0.3.8] - 2025-09-12

🚜 Refactor

  • (config) Tidy up the code

⚙️ Miscellaneous Tasks

  • (manifest) Explicitly set the versions to the lockfile versions
  • (renovate) Don't pin dev dependencies in the Cargo.toml
  • (rust) Configure rustfmt to wrap comments
  • (rust) Configure rustfmt to split long strings
  • (rust) Configure rustfmt to group imports
  • (rust) Configure rustfmt to split each import out
  • (rust) Add more clippy lints
  • (rust) Remove direct dependency on the http crate
  • (rust) Even more clippy lints

This PR was generated with release-plz.

## 🤖 New release * `webnsupdate`: 0.3.7 -> 0.3.8 <details><summary><i><b>Changelog</b></i></summary><p> <blockquote> ## [0.3.8] - 2025-09-12 ### 🚜 Refactor - *(config)* Tidy up the code ### ⚙️ Miscellaneous Tasks - *(manifest)* Explicitly set the versions to the lockfile versions - *(renovate)* Don't pin dev dependencies in the Cargo.toml - *(rust)* Configure rustfmt to wrap comments - *(rust)* Configure rustfmt to split long strings - *(rust)* Configure rustfmt to group imports - *(rust)* Configure rustfmt to split each import out - *(rust)* Add more clippy lints - *(rust)* Remove direct dependency on the http crate - *(rust)* Even more clippy lints <!-- generated by git-cliff --> </blockquote> </p></details> --- This PR was generated with [release-plz](https://github.com/release-plz/release-plz/).
chore: release v0.3.8
All checks were successful
/ build (pull_request) Successful in 50s
Details
/ checks (x86_64-linux, clippy) (pull_request) Successful in 12s
Details
/ checks (x86_64-linux, deny) (pull_request) Successful in 4s
Details
/ checks (x86_64-linux, module-ipv4-only-test) (pull_request) Successful in 32s
Details
/ checks (x86_64-linux, module-ipv4-test) (pull_request) Successful in 32s
Details
/ checks (x86_64-linux, module-ipv6-only-test) (pull_request) Successful in 32s
Details
/ checks (x86_64-linux, module-ipv6-test) (pull_request) Successful in 31s
Details
/ checks (x86_64-linux, module-nginx-test) (pull_request) Successful in 32s
Details
/ checks (x86_64-linux, nextest) (pull_request) Successful in 4s
Details
/ checks (x86_64-linux, treefmt) (pull_request) Successful in 3s
Details
/ trigger-release (pull_request) Successful in 20s
Details
/ report-size (pull_request) Successful in 6s
Details
9aba27f597 
Signed-off-by: Dynamic User <gitea-runner@taurus.fritz.box>
forgejo-actions commented 2025-08-30 22:08:41 +02: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.

NixOS Configurations

Name Size Size Change NAR Size NAR Size Change

Home Manager Configurations

Name Size Size Change NAR Size NAR Size Change

Packages

Name Size Size Change NAR Size NAR Size Change
webnsupdate 34MiB 64B 2.2MiB 64B
<!-- 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> ## NixOS Configurations | Name | Size | Size Change | NAR Size | NAR Size Change | |------|-----:|------------:|---------:|----------------:| ## Home Manager Configurations | Name | Size | Size Change | NAR Size | NAR Size Change | |------|-----:|------------:|---------:|----------------:| ## Packages | Name | Size | Size Change | NAR Size | NAR Size Change | |------|-----:|------------:|---------:|----------------:| | `webnsupdate` | 34MiB | 64B | 2.2MiB | 64B |
jalil force-pushed release-plz-2025-08-30T20-04-41Z from 9aba27f597 to ce3aa2178a 2025-08-31 22:02:29 +02:00 Compare
jalil force-pushed release-plz-2025-08-30T20-04-41Z from ce3aa2178a to 5fa3aa93ac 2025-09-01 22:05:47 +02:00 Compare
jalil force-pushed release-plz-2025-08-30T20-04-41Z from 5fa3aa93ac to dbbaadccba 2025-09-01 23:45:54 +02:00 Compare
jalil force-pushed release-plz-2025-08-30T20-04-41Z from dbbaadccba to b2b524bc45 2025-09-01 23:59:02 +02:00 Compare
jalil force-pushed release-plz-2025-08-30T20-04-41Z from b2b524bc45 to 0af453b512 2025-09-02 13:29:23 +02:00 Compare
jalil force-pushed release-plz-2025-08-30T20-04-41Z from 0af453b512 to 19d7e46f42 2025-09-02 22:05:46 +02:00 Compare
jalil force-pushed release-plz-2025-08-30T20-04-41Z from 19d7e46f42 to bb45334a67 2025-09-03 22:04:45 +02:00 Compare
jalil force-pushed release-plz-2025-08-30T20-04-41Z from bb45334a67 to a1568aa9f7 2025-09-03 22:15:33 +02:00 Compare
jalil force-pushed release-plz-2025-08-30T20-04-41Z from a1568aa9f7 to 3feabcdd3f 2025-09-04 22:05:35 +02:00 Compare
jalil force-pushed release-plz-2025-08-30T20-04-41Z from 3feabcdd3f to 9fcecdec4c 2025-09-05 17:44:57 +02:00 Compare
jalil force-pushed release-plz-2025-08-30T20-04-41Z from 9fcecdec4c to 4a3bdb7102 2025-09-05 22:05:33 +02:00 Compare
jalil force-pushed release-plz-2025-08-30T20-04-41Z from 4a3bdb7102 to 67b4e40f44 2025-09-06 18:01:22 +02:00 Compare
jalil force-pushed release-plz-2025-08-30T20-04-41Z from 67b4e40f44 to 0ecb27c75e 2025-09-06 18:28:27 +02:00 Compare
jalil force-pushed release-plz-2025-08-30T20-04-41Z from 0ecb27c75e to 9baecfe215 2025-09-06 18:37:21 +02:00 Compare
jalil self-assigned this 2025-09-06 18:46:16 +02:00
jalil force-pushed release-plz-2025-08-30T20-04-41Z from 9baecfe215 to 4c36f9b1f4 2025-09-06 18:50:06 +02:00 Compare
jalil force-pushed release-plz-2025-08-30T20-04-41Z from 4c36f9b1f4 to 4689c21941 2025-09-06 22:05:00 +02:00 Compare
jalil force-pushed release-plz-2025-08-30T20-04-41Z from 4689c21941 to 7e79f7bab8 2025-09-07 22:04:53 +02:00 Compare
jalil force-pushed release-plz-2025-08-30T20-04-41Z from 7e79f7bab8 to eb4b4d871d 2025-09-08 22:04:52 +02:00 Compare
jalil force-pushed release-plz-2025-08-30T20-04-41Z from eb4b4d871d to 28641d851c 2025-09-09 22:05:45 +02:00 Compare
jalil force-pushed release-plz-2025-08-30T20-04-41Z from 28641d851c to d72d95b9ed 2025-09-10 22:05:43 +02:00 Compare
jalil force-pushed release-plz-2025-08-30T20-04-41Z from d72d95b9ed to 78308ebadd 2025-09-11 18:41:33 +02:00 Compare
jalil force-pushed release-plz-2025-08-30T20-04-41Z from 78308ebadd to 216f99ee9e 2025-09-11 22:06:24 +02:00 Compare
jalil force-pushed release-plz-2025-08-30T20-04-41Z from 216f99ee9e to 803ac10e60 2025-09-12 22:05:25 +02:00 Compare
All checks were successful
/ build (pull_request) Successful in 48s
Required
Details
/ checks (x86_64-linux, clippy) (pull_request) Successful in 12s
Required
Details
/ checks (x86_64-linux, deny) (pull_request) Successful in 3s
Required
Details
/ checks (x86_64-linux, module-ipv4-only-test) (pull_request) Successful in 32s
Required
Details
/ checks (x86_64-linux, module-ipv4-test) (pull_request) Successful in 30s
Required
Details
/ checks (x86_64-linux, module-ipv6-only-test) (pull_request) Successful in 31s
Required
Details
/ checks (x86_64-linux, module-ipv6-test) (pull_request) Successful in 30s
Required
Details
/ checks (x86_64-linux, module-nginx-test) (pull_request) Successful in 32s
Required
Details
/ checks (x86_64-linux, nextest) (pull_request) Successful in 3s
Required
Details
/ checks (x86_64-linux, treefmt) (pull_request) Successful in 2s
Required
Details
/ trigger-release (pull_request) Successful in 19s
Required
Details
/ report-size (pull_request) Successful in 5s
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-08-30T20-04-41Z:release-plz-2025-08-30T20-04-41Z
git switch release-plz-2025-08-30T20-04-41Z
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
jalil
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/webnsupdate#406
No description provided.
Delete branch "release-plz-2025-08-30T20-04-41Z"

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?