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

fix(deps): update rust crate ring to v0.17.14 #150

Merged
renovate merged 1 commit from renovate/ring-0.x-lockfile into main 2025-03-11 21:24:35 +01:00
Conversation 1 Commits 1 Files changed 1 +2 -2
renovate commented 2025-03-11 21:20:26 +01:00
Collaborator
Copy link

This PR contains the following updates:

Package Type Update Change
ring dependencies patch 0.17.13 -> 0.17.14

Release Notes

briansmith/ring (ring)

v0.17.14

============================
Fixed a performance bug in the AVX2-based AES-GCM implementation added in
ring 0.17.13. This will be another notable performance improvement for most
newish x86-64 systems. The performance issue impacted not just AES-GCM.

Compatibility with GNU binutils 2.29 (used on Amazon Linux 2), and probably
even earlier versions, was restored. It is expected that ring 0.17.14 will
build on all the systems that 0.17.12 would build on.

Configuration

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

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, 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 | |---|---|---|---| | [ring](https://github.com/briansmith/ring) | dependencies | patch | `0.17.13` -> `0.17.14` | --- ### Release Notes <details> <summary>briansmith/ring (ring)</summary> ### [`v0.17.14`](https://github.com/briansmith/ring/blob/HEAD/RELEASES.md#Version-01714-2025-03-11) \============================ Fixed a performance bug in the AVX2-based AES-GCM implementation added in *ring* 0.17.13. This will be another notable performance improvement for most newish x86-64 systems. The performance issue impacted not just AES-GCM. Compatibility with GNU binutils 2.29 (used on Amazon Linux 2), and probably even earlier versions, was restored. It is expected that *ring* 0.17.14 will build on all the systems that 0.17.12 would build on. </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - "* 23 * * *" (UTC). 🚦 **Automerge**: Enabled. ♻ **Rebasing**: Whenever PR becomes conflicted, 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 2025-03-11 21:20:26 +01:00
fix(deps): update rust crate ring to v0.17.14
All checks were successful
/ check-renovaterc (push) Successful in 3s
Details
/ build (push) Successful in 1s
Details
/ check (clippy) (push) Successful in 2s
Details
/ check (module-ipv4-only-test) (push) Successful in 7s
Details
/ check (module-ipv4-test) (push) Successful in 7s
Details
/ check (module-ipv6-only-test) (push) Successful in 7s
Details
/ check (module-ipv6-test) (push) Successful in 6s
Details
/ check (module-nginx-test) (push) Successful in 6s
Details
/ check (nextest) (push) Successful in 2s
Details
/ check (treefmt) (push) Successful in 2s
Details
/ report-size (push) Successful in 2s
Details
33f8b1570d 
| datasource | package | from    | to      |
| ---------- | ------- | ------- | ------- |
| crate      | ring    | 0.17.13 | 0.17.14 |
renovate scheduled this pull request to auto merge when all checks succeed 2025-03-11 21:20:26 +01:00
forgejo-actions commented 2025-03-11 21:24:34 +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.

Packages

Name Size Size Change NAR Size NAR Size Change
default 35MiB 392B 2.9MiB 392B
git-cliff 60MiB 0B 19MiB 0B
webnsupdate 35MiB 392B 2.9MiB 392B
<!-- 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 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 | 392B | 2.9MiB | 392B | | `git-cliff` | 60MiB | 0B | 19MiB | 0B | | `webnsupdate` | 35MiB | 392B | 2.9MiB | 392B |
renovate merged commit 33f8b1570d into main 2025-03-11 21:24:35 +01:00
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

  
wontfix

This won't be fixed

No labels
bug
chore
duplicate
enhancement
help wanted
invalid
question
wontfix
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/webnsupdate#150
No description provided.
Delete branch "renovate/ring-0.x-lockfile"

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?