mCaptcha/pow_sha256
2
0
Fork 0
Code Issues 1 Pull requests 5 Projects Releases Packages Wiki Activity

chore(deps): update rust crate libfuzzer-sys to v0.4.12 #31

Open
renovate-bot wants to merge 1 commit from renovate/libfuzzer-sys-0.x-lockfile into master
pull from: renovate/libfuzzer-sys-0.x-lockfile
merge into: mCaptcha:master
Conversation 0 Commits 1 Files changed 1 +66 -12
renovate-bot commented 2026-05-18 05:18:21 +05:30
Member
Copy link

This PR contains the following updates:

Package Type Update Change
libfuzzer-sys dependencies patch 0.4.2 -> 0.4.12

Release Notes

rust-fuzz/libfuzzer (libfuzzer-sys)

v0.4.12

Released 2026-02-10.

Changed
  • Recommend SmallRng over StdRng in the examples for faster, more lightweight
    seeding and sampling
  • Updated rand dependency from 0.8.5 to 0.10
  • Updated flate2 dependency from 1.0.24 to 1.1
  • Rename gen variable to rng for better 2024 Edition compatibility

v0.4.11

Compare Source

Released 2026-02-10.

Changed
  • Updated to libFuzzer commit a47b42eb9f9b (release/22.x).

v0.4.10

Compare Source

Released 2025-07-03.

Changed
  • Updated to libFuzzer commit 6146a88f6049 (release/20.x).
  • Fuzz targets taking raw byte slice inputs can now return Corpus results.

v0.4.9

Compare Source

Released 2025-01-28.

Added
  • The example_init demonstrates how to pass an initialization code block to
    the fuzz_target! macro.
Changed
  • The fuzz_target! macro now supports the generation of LLVMFuzzerInitialize
    to execute initialization code once before running the fuzzer. This change is
    not breaking and is completely backward compatible.

v0.4.8

Compare Source

Released 2024-11-07.

Added
  • Bindings to LLVMFuzzerCustomCrossOver through the fuzz_crossover
    macro. See the example_crossover directory in this crate's repo for a
    complete example.
Changed
  • Updated to libFuzzer commit ab51eccf88f5321e7c60591c5546b254b6afab99
    (release/19.x).

v0.4.7

Compare Source

Released 2023-08-10.

Added
  • Added the link_libfuzzer cargo feature. This feature is on by default and
    preserves the existing behavior of statically linking libfuzzer. You can
    disable it if you are linking your own version of libfuzzer some other way, or
    another library that provides the same ABI as libfuzzer.

v0.4.6

Compare Source

Released 2023-01-26.

Fixed
  • Fixed a potential name conflict in functions generated by the fuzz_target!
    macro.
  • Fixed potential stale builds when updating custom libfuzzers to link against.

v0.4.5

Compare Source

Released 2022-10-18.

Added
  • Added the ability to tell libfuzzer whether to keep files inputs in the corpus
    or not. See the Corpus type and extended documentation for the
    fuzz_target! macro for details.
Changed
  • Ensured that there is always at least one inline-never frame on the stack per
    fuzz target. This helps prevent oss-fuzz from "deduplicating" different bugs
    from different fuzz targets into the same bug.

v0.4.4

Compare Source

Released 2022-09-01.

Changed
  • Updated to libFuzzer commit df90d22 (release/15.x).
  • LLVM 16's upcoming change to build requirements to C++17
    necessitate reflecting those changes. (libFuzzer updates contain C++14 code)
  • Drastically reduce build times by using parallel C++ compilation jobs
  • Updated rand dependency from 0.8.3 to 0.8.5
  • Updated flate2 dependency from 1.0.20 to 1.0.24

v0.4.3

Compare Source

Released 2020-03-03.

Changed
  • Updated to libFuzzer commit 60e32a1.
Fixed
  • Fixed an issue where the fuzz_target! macro would sometimes expand to
    versions of itself that were not $crate prefixed and would result in "error:
    cannot find macro fuzz_target in this scope" if the caller didn't import the
    macro but used the qualified version of it instead.

Configuration

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

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ 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 | |---|---|---|---| | [libfuzzer-sys](https://github.com/rust-fuzz/libfuzzer) | dependencies | patch | `0.4.2` -> `0.4.12` | --- ### Release Notes <details> <summary>rust-fuzz/libfuzzer (libfuzzer-sys)</summary> ### [`v0.4.12`](https://github.com/rust-fuzz/libfuzzer/blob/HEAD/CHANGELOG.md#0412) Released 2026-02-10. ##### Changed - Recommend `SmallRng` over `StdRng` in the examples for faster, more lightweight seeding and sampling - Updated `rand` dependency from 0.8.5 to 0.10 - Updated `flate2` dependency from 1.0.24 to 1.1 - Rename `gen` variable to `rng` for better 2024 Edition compatibility *** ### [`v0.4.11`](https://github.com/rust-fuzz/libfuzzer/blob/HEAD/CHANGELOG.md#0411) [Compare Source](https://github.com/rust-fuzz/libfuzzer/compare/0.4.10...0.4.11) Released 2026-02-10. ##### Changed - Updated to `libFuzzer` commit `a47b42eb9f9b` (`release/22.x`). *** ### [`v0.4.10`](https://github.com/rust-fuzz/libfuzzer/blob/HEAD/CHANGELOG.md#0410) [Compare Source](https://github.com/rust-fuzz/libfuzzer/compare/0.4.9...0.4.10) Released 2025-07-03. ##### Changed - Updated to `libFuzzer` commit `6146a88f6049` (`release/20.x`). - Fuzz targets taking raw byte slice inputs can now return `Corpus` results. *** ### [`v0.4.9`](https://github.com/rust-fuzz/libfuzzer/blob/HEAD/CHANGELOG.md#049) [Compare Source](https://github.com/rust-fuzz/libfuzzer/compare/0.4.8...0.4.9) Released 2025-01-28. ##### Added - The `example_init` demonstrates how to pass an initialization code block to the `fuzz_target!` macro. ##### Changed - The `fuzz_target!` macro now supports the generation of `LLVMFuzzerInitialize` to execute initialization code once before running the fuzzer. This change is not breaking and is completely backward compatible. *** ### [`v0.4.8`](https://github.com/rust-fuzz/libfuzzer/blob/HEAD/CHANGELOG.md#048) [Compare Source](https://github.com/rust-fuzz/libfuzzer/compare/0.4.7...0.4.8) Released 2024-11-07. ##### Added - Bindings to `LLVMFuzzerCustomCrossOver` through the `fuzz_crossover` macro. See the `example_crossover` directory in this crate's repo for a complete example. ##### Changed - Updated to `libFuzzer` commit `ab51eccf88f5321e7c60591c5546b254b6afab99` (`release/19.x`). *** ### [`v0.4.7`](https://github.com/rust-fuzz/libfuzzer/blob/HEAD/CHANGELOG.md#047) [Compare Source](https://github.com/rust-fuzz/libfuzzer/compare/0.4.6...0.4.7) Released 2023-08-10. ##### Added - Added the `link_libfuzzer` cargo feature. This feature is on by default and preserves the existing behavior of statically linking libfuzzer. You can disable it if you are linking your own version of libfuzzer some other way, or another library that provides the same ABI as libfuzzer. *** ### [`v0.4.6`](https://github.com/rust-fuzz/libfuzzer/blob/HEAD/CHANGELOG.md#046) [Compare Source](https://github.com/rust-fuzz/libfuzzer/compare/0.4.5...0.4.6) Released 2023-01-26. ##### Fixed - Fixed a potential name conflict in functions generated by the `fuzz_target!` macro. - Fixed potential stale builds when updating custom libfuzzers to link against. *** ### [`v0.4.5`](https://github.com/rust-fuzz/libfuzzer/blob/HEAD/CHANGELOG.md#045) [Compare Source](https://github.com/rust-fuzz/libfuzzer/compare/0.4.4...0.4.5) Released 2022-10-18. ##### Added - Added the ability to tell libfuzzer whether to keep files inputs in the corpus or not. See the `Corpus` type and extended documentation for the `fuzz_target!` macro for details. ##### Changed - Ensured that there is always at least one inline-never frame on the stack per fuzz target. This helps prevent oss-fuzz from "deduplicating" different bugs from different fuzz targets into the same bug. *** ### [`v0.4.4`](https://github.com/rust-fuzz/libfuzzer/blob/HEAD/CHANGELOG.md#044) [Compare Source](https://github.com/rust-fuzz/libfuzzer/compare/0.4.3...0.4.4) Released 2022-09-01. ##### Changed - Updated to `libFuzzer` commit `df90d22` (`release/15.x`). - LLVM 16's [upcoming change][llvm_cxx17] to build requirements to C++17 necessitate reflecting those changes. (`libFuzzer` updates contain C++14 code) - Drastically reduce build times by using parallel C++ compilation jobs - Updated `rand` dependency from 0.8.3 to 0.8.5 - Updated `flate2` dependency from 1.0.20 to 1.0.24 [llvm_cxx17]: https://llvm.org/docs/ReleaseNotes.html#update-on-required-toolchains-to-build-llvm *** ### [`v0.4.3`](https://github.com/rust-fuzz/libfuzzer/blob/HEAD/CHANGELOG.md#043) [Compare Source](https://github.com/rust-fuzz/libfuzzer/compare/0.4.2...0.4.3) Released 2020-03-03. ##### Changed - Updated to `libFuzzer` commit `60e32a1`. ##### Fixed - Fixed an issue where the `fuzz_target!` macro would sometimes expand to versions of itself that were not `$crate` prefixed and would result in "error: cannot find macro `fuzz_target` in this scope" if the caller didn't import the macro but used the qualified version of it instead. *** </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **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:eyJjcmVhdGVkSW5WZXIiOiI0Mi41Mi44IiwidXBkYXRlZEluVmVyIjoiNDIuNTIuOCIsInRhcmdldEJyYW5jaCI6Im1hc3RlciIsImxhYmVscyI6WyJyZW5vdmF0ZS1ib3QiXX0=-->
chore(deps): update rust crate libfuzzer-sys to v0.4.12
Some checks failed
ci/woodpecker/push/woodpecker Pipeline failed
Details
ci/woodpecker/pr/woodpecker Pipeline failed
Details
ci/woodpecker/pull_request_metadata/woodpecker Pipeline was successful
Details
caa101174c
Some checks failed
ci/woodpecker/push/woodpecker Pipeline failed
Details
ci/woodpecker/pr/woodpecker Pipeline failed
Details
ci/woodpecker/pull_request_metadata/woodpecker Pipeline was successful
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 renovate/libfuzzer-sys-0.x-lockfile:renovate/libfuzzer-sys-0.x-lockfile
git switch renovate/libfuzzer-sys-0.x-lockfile

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch master
git merge --no-ff renovate/libfuzzer-sys-0.x-lockfile
git switch renovate/libfuzzer-sys-0.x-lockfile
git rebase master
git switch master
git merge --ff-only renovate/libfuzzer-sys-0.x-lockfile
git switch renovate/libfuzzer-sys-0.x-lockfile
git rebase master
git switch master
git merge --no-ff renovate/libfuzzer-sys-0.x-lockfile
git switch master
git merge --squash renovate/libfuzzer-sys-0.x-lockfile
git switch master
git merge --ff-only renovate/libfuzzer-sys-0.x-lockfile
git switch master
git merge renovate/libfuzzer-sys-0.x-lockfile
git push origin master
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
  
bug
Something is not working

  
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

  
renovate-bot

   
renovate-security

   
security

   
wontfix
This won't be fixed

No labels
bug
duplicate
enhancement
help wanted
invalid
question
renovate-bot
renovate-security
security
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
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
mCaptcha/pow_sha256!31
No description provided.