Skip to content

Conversation

@mockersf
Copy link
Owner

@mockersf mockersf commented Dec 5, 2025

Objective

  • Describe the objective or issue this PR addresses.
  • If you're fixing a specific issue, say "Fixes #X".

Solution

  • Describe the solution used to achieve the objective above.

Testing

  • Did you test these changes? If so, how?
  • Are there any parts that need more testing?
  • How can other people (reviewers) test your changes? Is there anything specific they need to know?
  • If relevant, what platforms did you test these changes on, and are there any important ones you can't test?

Showcase

This section is optional. If this PR does not include a visual change or does not add a new feature, you can delete this section.

  • Help others understand the result of this PR by showcasing your awesome work!
  • If this PR adds a new feature or public API, consider adding a brief pseudo-code snippet of it in action
  • If this PR includes a visual change, consider adding a screenshot, GIF, or video
    • If you want, you could even include a before/after comparison!
  • If the Migration Guide adequately covers the changes, you can delete this section

While a showcase should aim to be brief and digestible, you can use a toggleable section to save space on longer showcases:

Click to view showcase
println!("My super cool code.");

greeble-dev and others added 30 commits October 6, 2025 10:30
…evyengine#21418)

Adopts bevyengine#21414. Bumps
[crate-ci/typos](https://github.com/crate-ci/typos) from 1.36.3 to
1.37.2.

---------

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Fixes a clippy error introduced by bevyengine#21338. Issue was inside a
`#[cfg(target_os = "windows")]` block so it wasn't caught by CI.

```rust
error: this boolean expression can be simplified
   --> crates\bevy_winit\src\state.rs:481:16
    |
481 |             if !self.app_exit.is_some()
    |                ^^^^^^^^^^^^^^^^^^^^^^^^ help: try: `self.app_exit.is_none()`
```

Tested with Rust 1.90.0, Win10, `cargo run -p ci -- lints`, `cargo run
--example window_settings`.
…evyengine#20527)

# Objective
Use less memory overhead when storing resources and sparse set
components, maintain less unsafe code. Fixes bevyengine#14824. Supersedes bevyengine#18245.

## Solution
Use `BlobArray` and `ThinColumn` to replace ` BlobVec` and `Column` in
`ResourceData` and `ComponentSparseSet`. This both uses less memory
overhead for each resource and sparse set component we use, and also
allows us to avoid keeping two nearly identical implementations of
`BlobVec`/`BlobArray` and `ThinColumn`/`Column` around.

## Testing
Tested this against existing unit tests and miri.

Co-Authored By: [email protected]

---------

Co-authored-by: Mira <[email protected]>
- `reinhard_extended`
- `ycbcr_to_rgb`
# Objective

- Taplo 0.10.0 is out since may, let's update!

## Solution

- Stop using cargo-binstall. it's a pain to maintain and break updates
for the tools it installs anyway
<img width="827" height="749" alt="Screenshot 2025-10-01 at 21 54 58"
src="https://github.com/user-attachments/assets/f86ba2e9-767f-4a0d-b87c-9222d2b804ff"
/>

- All that just for the tool installing the tool
- Do the curl as recommended in taplo docs

## Testing

- CI
# Objective

`TextPipeline::queue_text` temporarily `take`s the buffer from its
`glyph_info` field, so that it can be used in a call to
`TextPipeline::update_buffer`. It then replaces it when the function
exits. This is a bit fragile, as the function has two exit points.

## Solution

Replace it immediately after calling `update_buffer`, and then access it
with `self` for the rest of the function.

---------

Co-authored-by: Dimitrios Loukadakis <[email protected]>
# Objective

- a way to draw aabbs that doesnt hurt my soul every time i use gizmos

## Solution

- Gizmos::cuboid actually draws a cube, so name it that to free up the
name for an actual cuboid drawing function
- Add a real Gizmos::cuboid which takes Into<Aabb3d> now that bevyengine#21307
merged, so we can also draw bevy_camera Aabb.

## Testing

- Existing gizmo tests and also tried making 3d_scene turn on
AabbGizmoConfigGroup.draw_all and it looked good:
<img width="774" height="393"
alt="{ADFB1568-0B6F-48C8-86C7-F81A73E7B409}"
src="https://github.com/user-attachments/assets/2bbcb638-c1d0-41fe-b942-08d21d64fa95"
/>
# Objective

- make morph support optional on bevy_mesh
- unblock bevyengine#20742
- another step towards bevyengine#20867

## Solution

- feature

## Testing

- morph targets example works
…w return a Result (bevyengine#20797)

# Objective

Remove panics from image reinterpretation methods.

## Solution

Introduce new errors and emit those instead of panicking.

## Testing

- Did you test these changes? If so, how?
  - CI + changed examples
- Are there any parts that need more testing?
  - No
- How can other people (reviewers) test your changes? Is there anything
specific they need to know?
  - examples, no
- If relevant, what platforms did you test these changes on, and are
there any important ones you can't test?
  - linux, amd cpu, amd gpu

---

Moved out of bevyengine#20536

---------

Co-authored-by: Alice Cecile <[email protected]>
This PR is the start of work to have the realtime Solari lighting path
support specular materials, like the existing pathtracer support.

* Refactor gbuffer decoding into a separate file
* ReSTIR DI still resamples based on only diffuse BRDF, but shading now
uses the full specular + diffuse brdf
* Resampling with the full BRDF is something to prototype in the future
* ReSTIR GI is still diffuse-only. A future PR will introduce a separate
pass for specular GI.
* Misc refactoring 

<img width="2564" height="1500" alt="image"
src="https://github.com/user-attachments/assets/b8dd050c-4940-4616-bd0e-83d181bae842"
/>

---------

Co-authored-by: atlv <[email protected]>
# Objective

Closes bevyengine#21395

## Solution

If bloom texture and uniform buffer don't change, then we skip updating
the bind groups.

I also tried implementing a global hash map cache similar to
TextureCache but the performance is worse than the current. So I think
we'd better cache bind groups locally rather than globally. Also, these
tasks can be parallelized on the CPU so the performance impact may not
be significant.

## Testing

After this the overhead of `prepare_bloom_bind_groups` become negligible
according to tracy.
# Objective

Simplify implementation of `debug_ensure_aligned`.  

The code has a comment asking for the implementation to be replaced when
`ptr::is_aligned_to` is stable. While `is_aligned_to` hasn't been
stabilized, `ptr::is_aligned` has, and is what we want here anyway.

## Solution

Use `ptr::is_aligned`.
…urce)]` (bevyengine#21385)

# Objective

Fixes bevyengine#20413 

Adding non-static lifetimes to `#[derive(Resource)]` should not compile.

## Solution

Added a check in the derive macro of `Resource` to ensure all lifetime
generics are bound to 'static, if not it raises an error.

## Testing

Added a ui-test for compile error.

---------

Co-authored-by: Chris Russell <[email protected]>
# Objective

- be able to use Cuboid with Into<Aabb3d> methods

## Solution

- impl From

## Testing

ci
# Objective

- Step towards bevyengine#20867

## Solution

- Do a rename

## Testing

- Ran some examples
# Objective

- Now that we've removed Column, there's not really a reason for
ThinColumn to have a special name

## Solution

- Rename ThinColumn to Column
- fix docs

## Testing

- compiles
# Objective

- make bevy_mesh optional for bevy_animate as mentioned in
bevyengine#20714 (comment)

## Solution

- copy paste the morph weights stuff out into a module, gate it, then
add the optional dep
# Objective

- Gizmos::cuboid is for drawing cubes, even the docs say so. A cuboid
drawing function should take Cuboid as input.

## Solution

- Rename ::cuboid to ::cube, making way for an actual cuboid drawing
function.

## Testing

- ci
# Objective

- allow users to cut unneeded deps

## Solution

- feature gate

## Testing

- clearcoat example uses generated tangents, still works.
# Objective

The `FontAtlasSets` resource contains a map from `AssetId<Font>`s to
`FontAtlasSet`s.
`FontAtlasSet` has another map from a `FontAtlasKey` (tuple of the font
size bit cast into a `u32` and `FontSmoothing`) to a vec that contains
the actual font atlases for the font. The redirection through the
additional map doesn't serve much purpose, only individual fonts are
looked up (except when freeing unused fonts), not the set of all atlases
for a particular font face.

## Solution
* Remove `FontAtlasSet`. 
* Rename `FontAtlasSets` to `FontAtlasSet`.
* Add `AssetId<Font>` to `FontAtlasKey`.
* Change the font atlas map to a `HashMap<FontAtlasKey, Vec<FontAtlas>>`
* Move the `FontAtlasSet` methods `add_glyph_to_atlas`,
`get_glyph_atlas_info`, and `get_outlined_glyph_texture` into the
`font_atlas` module and rework them into free functions.
* Change `FontAtlasSet` into a newtype around the map and remove the
manual method implementations in favour of deriving `Deref` and
`DerefMut`.

We could consider renaming `FontAlasSet` to `FontAtlasMap`, but it
doesn't seem necessary, and mathematically a map is a set so it's not
incorrect.

## Testing

The output from all of the text examples should be unchanged.

Naive benchmarks suggest this is a modest improvement in performance at
a very high load (5% ish), but this is more about reducing complexity to
make more significant optimisations possible. Freeing the unused atlases
when a font asset is removed will be slower, it has to filter all the
font atlas vecs now instead of just removing the entry for the font
asset, but this isn't done very often and the number of entries should
be relatively low.

---------

Co-authored-by: Dimitrios Loukadakis <[email protected]>
# Objective

- `bevy_asset` needs more tests! This adds three related to asset
processing.

## Solution

- Create a new `MemoryAssetWriter` to pair with `MemoryAssetReader`.
- Adds a way to override whether the asset processor is created or not.
- Make `Data::value` and `Data::path` `pub` so that we can actually see
what is written to the processed dir. Note: `Dir::get_asset` returns
`Data` already, but it isn't usable.
- Add three tests: one to test that assets are copied to the processed
dir for no-processing assets, one to test that using a default processor
works, and one to test that an asset meta file works.

## Testing

- This adds testing! :D
# Objective

- Fixes bevyengine#21425.
- Prior to bevyengine#19408, we were loading the LUTs with sRGB off. bevyengine#19408
accidentally did not maintain this behavior.

## Solution

- Specify the settings for the LUTs to disable sRGB.
- Also make the LUTs only accessible in the render world.

## Testing

- Ran the anti_aliasing example. Compared no AA to SMAA and it looks
different now!
…task. (bevyengine#21204)

# Objective

- The previous state had the loader task send a single
`InternalAssetEvent::Loaded` for every root asset **and** each of its
subassets. The `handle_internal_asset_events` system reads these events
one at a time. This means these two threads are racing. So it's possible
to see some of the subassets loaded without the root asset being loaded
in a frame, and then have to wait an additional frame to see the
remaining subassets and root asset loaded.

## Solution

- Instead of recursively sending the subassets inside the loader task,
just send the `LoadedAsset` in its entirety.
- Do the recursion when processing the loaded asset. Since we're doing
this in the system, the entire loaded asset will be processed in a
single frame.
- This also reduces contention of the channel.

## Testing

- None. This is kinda a "fake issue". In order to see it, handling a
loaded asset in `handle_internal_asset_events` needs to finish the last
received subasset before the loader task sends the root asset. This is
probably pretty unlikely, but could in theory cause flaky tests.
## Objective

Closes bevyengine#21349

Provides an ergonomic way to create a `Handle<A>` from a `Uuid` at
runtime.

## Solution

Implements the `From<Uuid>` trait for `Handle<A>`, allowing users to
write:
```rust
let uuid = Uuid::new_v4();
let handle: Handle<Image> = uuid.into();
```

Instead of the current verbose approach:
```rust
let handle = Handle::<Image>::Uuid(uuid, PhantomData);
```

## Testing

- Added comprehensive test `from_uuid` that verifies:
  - Conversion from `Uuid` to `Handle<A>` works correctly
  - The resulting handle is a UUID variant
  - The handle ID matches the input UUID
  - Both `.into()` and explicit `From::from()` work
- All existing handle tests continue to pass
- Clippy and formatting checks pass

---------

Co-authored-by: Alice Cecile <[email protected]>
Co-authored-by: François Mockers <[email protected]>
# Objective

- Only prefix features bevy_ if they correspond to a crate
- Another step towards bevyengine#20867

## Solution

- rename it

## Testing

- ci
# Objective

Fix nightly clippy

## Solution

```
cargo +nightly clippy --workspace --all-targets --all-features --fix
```

## Testing

CI
# Objective

- i always forget what it is

## Solution

- put it at the top of the file (another md template does this - not
new)

## Testing

- umm
# Objective

- Only prefix features bevy_ if they correspond to a crate
- Another step towards bevyengine#20867

## Solution

- rename it

## Testing

- ci
…o it (bevyengine#20215)

# Objective

Moving the camera around is really important to validate that our scenes
are rendered correctly.

Bevy engine devs currently do this via a fairly cursed "library example"
which includes a basic freecam controller (which is technically distinct
from a flycam apparently). This has three problems:

1. Oh god why are we taking pseudo-dependencies on other examples.
2. Something like this would be useful for debugging for users.
3. Something like this would be useful for the editor and other tooling.

## Solution

Create a new `bevy_camera_controllers` crate, and move the existing
freecam implementation into it, nearly verbatim.

This cleans up some ugly tech debt in how we do this, makes it easier to
add a camera controller to other examples, and also gives us a scaffold
for future camera controllers.

This PR has been marked `X-Blessed`, as I went over this plan with @cart
in a [meeting on
2025-06-23](https://discord.com/channels/691052431525675048/692572690833473578/1386847828923519038),
and we both agreed that this was the right first step.

## Testing

I've tested the examples that rely on this camera controller: they work
just like before.

## Notes for reviewers

- I don't intend to land this in Bevy 0.17: the existing example code is
not high enough quality for me to be happy shipping this
- we're also soft feature-frozen; I was just in the mood to do this
today
- this PR has some minimal cleanup: just enough naming and docs work to
make this code not an active liability. Any more will risk derailing
this PR and making it harder to review
- I've opted to expose top-level feature flags for the various camera
controllers. This is a bit noisy, but it was the only sensible way I
could see to both have "no camera controllers by default" and "still
easy to use these controllers in examples"
- this will not be the only camera controller in this crate, or the Bevy
Editor
- this is not the place to discuss "what should the default camera
controller for the Bevy Editor be"
- if you think this crate, or this particular move is the wrong strategy
for some other reason though, please do speak up :)
- my personal (unblessed) hope is that we continue to add camera
controllers to this crate as needed for various first-party tooling. I
will probably largely push-back on adding camera controllers that we do
not actively use to this crate, since I don't think they make great
libraries in general (much better to copy-paste)

## TODO

- [x] add release note. I'm waiting until after Bevy 0.17 ships to do
this
- [x] update the examples/README.md file. I was lazy and didn't want to
constantly resolve merge conflicts on that while this PR sits
- [x] change to singular crate name

## Future work

- split apart the giant camera controller component
- make keybinding better, either with or without a real input manager
solution
- split apart the system to make it more modular
- make the system handle fixed timesteps better
- use the camera controller in more examples for debugging
- add more camera controllers!

---------

Co-authored-by: atlv <[email protected]>
Co-authored-by: Jan Hohenheim <[email protected]>
# Objective

- Only prefix features bevy_ if they correspond to a crate
- Another step towards bevyengine#20867

## Solution

- rename it

## Testing

- ci
samoylovfp and others added 30 commits November 26, 2025 22:04
# Objective

This is a follow up to
https://github.com/bevyengine/bevy/pull/21713/files

I noticed something weird in the migration guide --- the `asset_path`
method was removed,
so proposed fix now yields
```
no method named `asset_path` found for mutable reference `&mut LoadContext<'c>` in the current scope
```

The actual change to get the original path is `.path().path()`


## Solution
Updated the migration guide
## Testing
I've played around with `load_context` in `GltfLoader` and checked the
signatures the methods return

---

Found this thanks to Alice's merge train

Co-authored-by: François Mockers <[email protected]>
# Objective

Some shaders on the `atmosphere` module of `bevy_pbr` have many unused
imports

## Solution

Trim imports of the offending shaders.

## Testing

`atmosphere` example

---------

Co-authored-by: François Mockers <[email protected]>
# Objective

- `hashbrown` 0.16.0 does not provide `get_disjoint_key_value_mut()`,
which is used in `crates\bevy_platform\src\collections\hash_map.rs `, We
must update to hashbrown 0.16.1, which includes this method.

## Testing

- CI

---
…cation code. (bevyengine#21962)

Currently, custom prepasses can't be easily added outside the `bevy_pbr`
crate for two reasons:

1. The fields in `PrepassSpecializer` are private to the `bevy_pbr`
crate, so a `PrepassSpecializer` can't be constructed. Furthermore, the
`PrepassSpecializer::specialize` method itself calls private APIs, so a
developer can't even copy and paste the `PrepassSpecializer` into
application code.

2. The `set_mesh_motion_vector_flags` system is private, meaning that
specialization systems for custom prepasses can't be ordered after it.
This is a problem because those specialization systems may need to read
the motion vector flags that that system sets.

This commit changes the fields in `PrepassSpecializer` to be public and
also changes the `set_mesh_motion_vector_flags` system to be public.
…f they have shadows enabled. (bevyengine#21961)

Currently, the `specialize_prepass_material_meshes` function adds meshes
to the prepass unless both `prepass_enabled` *and* `shadows_enabled` are
false for that material. This seems incorrect, as (1) the flags are
separate for a reason and (2) meshes are added to the shadow pass not in
`specialize_prepass_material_meshes` but in `specialize_shadows`.

This patch changes `specialize_prepass_material_meshes` to skip adding
meshes to the prepass if `prepass_enabled` is false, even if
`shadows_enabled` is true.
# Objective

```rust
/// Calculate the size of the text area for the given buffer.
fn buffer_dimensions(buffer: &Buffer) -> Vec2 {
    let (width, height) = buffer
        .layout_runs()
        .map(|run| (run.line_w, run.line_height))
        .reduce(|(w1, h1), (w2, h2)| (w1.max(w2), h1 + h2))
        .unwrap_or((0.0, 0.0));

    Vec2::new(width, height).ceil()
}
```

This function is unnecessarily complicated, there's no need to map and
then reduce, it could just use a fold.

## Solution

A for-loop seems like the most straightforward solution:

```rust
/// Calculate the size of the text area for the given buffer.
fn buffer_dimensions(buffer: &Buffer) -> Vec2 {
    let mut size = Vec2::ZERO;
    for run in buffer.layout_runs() {
        size.x = size.x.max(run.line_w);
        size.y += run.line_height;
    }
    size.ceil()
}
```

Naive benchmarks suggest this is a bit more efficient as well, but the
difference is quite small.

## Testing

`testbed_ui`'s output remaining unchanged should be enough to verify
that this is correct.
# Objective

- Although unsafe, `ThinSlicePtr::get()` doesn't signal that it doesn't
perform bounds checking unless you are familiar with the API.
- `ThinSlicePtr::get()` takes `self`, not `&self`, meaning it consumes
the `ThinSlicePtr` each time `get()` is called. This does not match the
behavior of
[`slice.get()`](https://doc.rust-lang.org/stable/std/primitive.slice.html#method.get),
which takes `&self`.
- This small issue was hidden by the fact that `ThinSlicePtr` implements
`Copy`. This isn't a large issue because it all compiles down to the
same machine code, but there's no point to `get()` requiring `self`.
- `ThinSlicePtr` could use better documentation, and could be improved a
little in some areas.

## Solution

- Rename `ThinSlicePtr::get()` to `get_unchecked()`, making the API
mirror
[`slice.get_unchecked()`](https://doc.rust-lang.org/stable/std/primitive.slice.html#method.get_unchecked).
The old `get()` is kept as a deprecated method, to be removed in 1.19.0.
- Make the new `slice.get_unchecked()` take `&self` rather than `self`.
- Add more documentation and slightly re-arrange code, while maintaining
original behavior.

## Testing

- Any unintentional changes should be caught by the Rust Compiler and
Miri!

---------

Co-authored-by: François Mockers <[email protected]>
# Objective

Attempting to display entities with padding does not work, no padding is
added.

## Solution

Fix the `fmt::Display` implementation of `Entity` so that padding works.

## Testing

Added some unit tests for padding.

Co-authored-by: François Mockers <[email protected]>
…ine#21869)

Updates the requirements on
[notify-debouncer-full](https://github.com/notify-rs/notify) to permit
the latest version.
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/notify-rs/notify/blob/main/CHANGELOG.md">notify-debouncer-full's
changelog</a>.</em></p>
<blockquote>
<h2>debouncer-full 0.6.0 (2025-08-03)</h2>
<ul>
<li>FEATURE: allow <code>FileIdCache</code> trait implementations to
choose ownership of the returned file-ids <a
href="https://redirect.github.com/notify-rs/notify/issues/664">#664</a></li>
<li>FEATURE: added support for the <a
href="https://docs.rs/flume"><code>flume</code></a> crate <a
href="https://redirect.github.com/notify-rs/notify/issues/680">#680</a></li>
<li>FIX: skip all <code>Modify</code> events right after a
<code>Create</code> event, unless it's a rename event <a
href="https://redirect.github.com/notify-rs/notify/issues/701">#701</a></li>
</ul>
<p><a
href="https://redirect.github.com/notify-rs/notify/issues/664">#664</a>:
<a
href="https://redirect.github.com/notify-rs/notify/pull/664">notify-rs/notify#664</a>
<a
href="https://redirect.github.com/notify-rs/notify/issues/680">#680</a>:
<a
href="https://redirect.github.com/notify-rs/notify/pull/680">notify-rs/notify#680</a>
<a
href="https://redirect.github.com/notify-rs/notify/issues/701">#701</a>:
<a
href="https://redirect.github.com/notify-rs/notify/pull/701">notify-rs/notify#701</a></p>
<h2>debouncer-mini 0.7.0 (2025-08-03)</h2>
<ul>
<li>FEATURE: added support for the <a
href="https://docs.rs/flume"><code>flume</code></a> crate <a
href="https://redirect.github.com/notify-rs/notify/issues/680">#680</a></li>
</ul>
<h2>file-id 0.2.3 (2025-08-03)</h2>
<ul>
<li>CHANGE: implement <code>AsRef&lt;FileId&gt;</code> for
<code>FileId</code> <a
href="https://redirect.github.com/notify-rs/notify/issues/664">#664</a></li>
</ul>
<h2>notify 8.1.0 (2025-07-03)</h2>
<ul>
<li>FEATURE: added support for the <a
href="https://docs.rs/flume"><code>flume</code></a> crate</li>
<li>FIX: kqueue-backend: do not double unwatch top-level directory when
recursively unwatching <a
href="https://redirect.github.com/notify-rs/notify/issues/683">#683</a></li>
<li>FIX: Return the crate error <code>PathNotFound</code> instead
bubbling up the std::io error <a
href="https://redirect.github.com/notify-rs/notify/issues/685">#685</a></li>
<li>FIX: fix server hangs when trashing folders on Windows <a
href="https://redirect.github.com/notify-rs/notify/issues/674">#674</a></li>
</ul>
<h2>notify 8.0.0 (2025-01-10)</h2>
<ul>
<li>CHANGE: update notify-types to version 2.0.0</li>
<li>CHANGE: raise MSRV to 1.77 <strong>breaking</strong></li>
<li>FEATURE: add config option to disable following symbolic links <a
href="https://redirect.github.com/notify-rs/notify/issues/635">#635</a></li>
<li>FIX: unaligned access to FILE_NOTIFY_INFORMATION <a
href="https://redirect.github.com/notify-rs/notify/issues/647">#647</a>
<strong>breaking</strong></li>
</ul>
<p><a
href="https://redirect.github.com/notify-rs/notify/issues/635">#635</a>:
<a
href="https://redirect.github.com/notify-rs/notify/pull/635">notify-rs/notify#635</a>
<a
href="https://redirect.github.com/notify-rs/notify/issues/647">#647</a>:
<a
href="https://redirect.github.com/notify-rs/notify/pull/647">notify-rs/notify#647</a></p>
<h2>notify-types 2.0.0 (2025-01-10)</h2>
<ul>
<li>CHANGE: replace instant crate with web-time <a
href="https://redirect.github.com/notify-rs/notify/issues/652">#652</a>
<strong>breaking</strong></li>
<li>CHANGE: the web-time dependency is now behind the
<code>web-time</code> feature <strong>breaking</strong></li>
</ul>
<p><a
href="https://redirect.github.com/notify-rs/notify/issues/652">#652</a>:
<a
href="https://redirect.github.com/notify-rs/notify/pull/652">notify-rs/notify#652</a></p>
<h2>debouncer-mini 0.6.0 (2025-01-10)</h2>
<ul>
<li>CHANGE: update notify to version 8.0.0</li>
</ul>
<h2>debouncer-full 0.5.0 (2025-01-10)</h2>
<ul>
<li>CHANGE: update notify to version 8.0.0</li>
<li>CHANGE: pass <code>web-time</code> feature to notify-types</li>
</ul>
<h2>notify-types 1.0.1 (2024-12-17)</h2>
<ul>
<li>FIX: <code>Event::kind</code> serialization with
<code>serialization-compat-6</code> feature <a
href="https://redirect.github.com/notify-rs/notify/issues/660">#660</a></li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/notify-rs/notify/commit/a1d7c2d8f80786679d58ec6d5986a1d4278bc8cf"><code>a1d7c2d</code></a>
Prepare release (<a
href="https://redirect.github.com/notify-rs/notify/issues/706">#706</a>)</li>
<li><a
href="https://github.com/notify-rs/notify/commit/c685ea7d82b35b06bf81a824f68095e2bda6f0a7"><code>c685ea7</code></a>
Skip all <code>Modify</code> events right after a <code>Create</code>
event, unless it's a rename e...</li>
<li><a
href="https://github.com/notify-rs/notify/commit/e36d54e94d2c364478f99f1d3b62245ed2ad2926"><code>e36d54e</code></a>
fix: INotifyWatcher may raise events with no paths (<a
href="https://redirect.github.com/notify-rs/notify/issues/700">#700</a>)</li>
<li><a
href="https://github.com/notify-rs/notify/commit/394ef18bebf0063c717ff7ea7387d36dacaf2c1c"><code>394ef18</code></a>
feat(inotify): notify a user if the <code>max_user_watches</code> has
been reached impli...</li>
<li><a
href="https://github.com/notify-rs/notify/commit/04473dea90a88c3444ff1a2876c4fbeda479441d"><code>04473de</code></a>
chore: Prepare 8.1.0 release (<a
href="https://redirect.github.com/notify-rs/notify/issues/697">#697</a>)</li>
<li><a
href="https://github.com/notify-rs/notify/commit/12a026d18ac097e578b2c3c2885ee60ae664072c"><code>12a026d</code></a>
fix: make <code>PathsMut::commit</code> consuming (<a
href="https://redirect.github.com/notify-rs/notify/issues/695">#695</a>)</li>
<li><a
href="https://github.com/notify-rs/notify/commit/d824023e483b24ceb398f08dec20f35ce575e7fa"><code>d824023</code></a>
feat: introduce <code>Watcher::paths_mut</code> for adding/removing
paths in batch (<a
href="https://redirect.github.com/notify-rs/notify/issues/692">#692</a>)</li>
<li><a
href="https://github.com/notify-rs/notify/commit/b98413446040fe47e13eb3de7c8acd77d18aea78"><code>b984134</code></a>
Do not clone paths while walking dirs (<a
href="https://redirect.github.com/notify-rs/notify/issues/693">#693</a>)</li>
<li><a
href="https://github.com/notify-rs/notify/commit/416ba8248e25fc30b9503b1319933275c13e3576"><code>416ba82</code></a>
chore: Use MSRV for Clippy and rustfmt (<a
href="https://redirect.github.com/notify-rs/notify/issues/694">#694</a>)</li>
<li><a
href="https://github.com/notify-rs/notify/commit/10ce3ef6b79555159fae8a02919a43b499d1c2c3"><code>10ce3ef</code></a>
Update <code>windows-sys</code> to v0.60 (<a
href="https://redirect.github.com/notify-rs/notify/issues/691">#691</a>)</li>
<li>Additional commits viewable in <a
href="https://github.com/notify-rs/notify/compare/debouncer-full-0.5.0...debouncer-full-0.6.0">compare
view</a></li>
</ul>
</details>
<br />


Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop
Dependabot creating any more for this major version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop
Dependabot creating any more for this minor version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)


</details>

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: François Mockers <[email protected]>
Updates the requirements on
[lz4_flex](https://github.com/pseitz/lz4_flex) to permit the latest
version.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/pseitz/lz4_flex/releases">lz4_flex's
releases</a>.</em></p>
<blockquote>
<h2>0.12.0</h2>
<h2>What's Changed</h2>
<ul>
<li>Fix integer overflows when decoding large payloads by <a
href="https://github.com/teh-cmc"><code>@​teh-cmc</code></a> in <a
href="https://redirect.github.com/PSeitz/lz4_flex/pull/192">PSeitz/lz4_flex#192</a></li>
<li>chore(readme): add python binding impl by <a
href="https://github.com/LVivona"><code>@​LVivona</code></a> in <a
href="https://redirect.github.com/PSeitz/lz4_flex/pull/190">PSeitz/lz4_flex#190</a></li>
</ul>
<h2>New Contributors</h2>
<ul>
<li><a href="https://github.com/teh-cmc"><code>@​teh-cmc</code></a> made
their first contribution in <a
href="https://redirect.github.com/PSeitz/lz4_flex/pull/192">PSeitz/lz4_flex#192</a></li>
<li><a href="https://github.com/LVivona"><code>@​LVivona</code></a> made
their first contribution in <a
href="https://redirect.github.com/PSeitz/lz4_flex/pull/190">PSeitz/lz4_flex#190</a></li>
</ul>
<p><strong>Full Changelog</strong>: <a
href="https://github.com/PSeitz/lz4_flex/compare/0.11.5...0.12.0">https://github.com/PSeitz/lz4_flex/compare/0.11.5...0.12.0</a></p>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/PSeitz/lz4_flex/blob/main/CHANGELOG.md">lz4_flex's
changelog</a>.</em></p>
<blockquote>
<h1>0.12.0 (2025-11-11)</h1>
<ul>
<li>Fix integer overflows when decoding large payloads <a
href="https://redirect.github.com/PSeitz/lz4_flex/pull/192">#192</a>
(thanks <a
href="https://github.com/teh-cmc"><code>@​teh-cmc</code></a>)</li>
</ul>
<pre><code>This fixes an u32 integer overflow when decoding large
payloads in the block format.
Note: The block format is not suitable for such large payloads, since it
keeps everything in memory. Consider using the frame format for large
data.
<p>This change also removes a unsafe fast-path for write_integer to
simplify the code.
The performance impact is on incompressible data, which is already fast
enough.
</code></pre></p>
<h1>0.11.5 (2025-06-19)</h1>
<ul>
<li>Fix incorrect rust-version field name in Cargo.toml <a
href="https://redirect.github.com/PSeitz/lz4_flex/pull/187">#187</a></li>
</ul>
<h1>0.11.4 (2025-06-14)</h1>
<ul>
<li>Upgrade to twox-hash 2.0<a
href="https://redirect.github.com/PSeitz/lz4_flex/pull/175">#175</a></li>
<li>Better <code>no_std</code> compatibility <a
href="https://redirect.github.com/PSeitz/lz4_flex/pull/180">#180</a></li>
</ul>
<h1>0.11.3 (2024-03-30)</h1>
<ul>
<li>Fix support for <code>--deny=unsafe_code</code> compilation <a
href="https://redirect.github.com/PSeitz/lz4_flex/pull/152">#152</a></li>
<li>make <code>get_maximum_output_size</code> const <a
href="https://redirect.github.com/PSeitz/lz4_flex/pull/153">#153</a></li>
</ul>
<h1>0.11.2 (2024-01-11)</h1>
<ul>
<li>Include license file in the published crate</li>
</ul>
<h1>0.11.1 (2023-06-19)</h1>
<ul>
<li>[<strong>breaking</strong>] remove <code>unchecked-decode</code>
Remove <code>unchecked-decode</code> feature-flag, because of feature
unification:
<a
href="https://doc.rust-lang.org/cargo/reference/features.html#feature-unification">https://doc.rust-lang.org/cargo/reference/features.html#feature-unification</a></li>
</ul>
<h1>0.11.0 (2023-06-18)</h1>
<h3>Documentation</h3>
<ul>
<li>Docs: add decompress block example</li>
</ul>
<h3>Fixes</h3>
<ul>
<li>Handle empty input in Frame Format <a
href="https://redirect.github.com/PSeitz/lz4_flex/pull/120">#120</a></li>
</ul>
<pre><code>Empty input was ignored previously and didn't write anything.
Now an empty Frame is written. This improves compatibility with the
reference implementation and some corner cases.
</code></pre>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/PSeitz/lz4_flex/commit/975bfa7ac9583da879b5d7578b423232d84f69fe"><code>975bfa7</code></a>
bump version to 0.12.0</li>
<li><a
href="https://github.com/PSeitz/lz4_flex/commit/40d81107aba09e62b14a04938443d6edd885b540"><code>40d8110</code></a>
update readme</li>
<li><a
href="https://github.com/PSeitz/lz4_flex/commit/642020e842cf4b9ba15173765fab4df40a8574fa"><code>642020e</code></a>
bump version to 0.12</li>
<li><a
href="https://github.com/PSeitz/lz4_flex/commit/5295b1601ef27629f7cf6d7f157f50d51c1308ee"><code>5295b16</code></a>
chore(readme): add python binding impl</li>
<li><a
href="https://github.com/PSeitz/lz4_flex/commit/c1483c4db47d1086489b72337762db7b458b6132"><code>c1483c4</code></a>
fix the issue</li>
<li><a
href="https://github.com/PSeitz/lz4_flex/commit/b3c03bea751f25e58819724caab81d5856c895c7"><code>b3c03be</code></a>
implement test demonstrating the issue</li>
<li><a
href="https://github.com/PSeitz/lz4_flex/commit/a61ee5f23f409641a8c8ab27cac784cdba57d708"><code>a61ee5f</code></a>
remove unsafe write_integer which AFAICT is not used <em>and</em>
broken</li>
<li><a
href="https://github.com/PSeitz/lz4_flex/commit/ad71a3103daa37f8ddd139f0c29b6e4ce8724ba3"><code>ad71a31</code></a>
fix illegal doc comment</li>
<li><a
href="https://github.com/PSeitz/lz4_flex/commit/f1c070e987b7d056c4868b19e0b00149f4256653"><code>f1c070e</code></a>
clippy</li>
<li><a
href="https://github.com/PSeitz/lz4_flex/commit/1496be413a0a5236f1aa8d3b8f14169ef7ce42d2"><code>1496be4</code></a>
update binggan</li>
<li>Additional commits viewable in <a
href="https://github.com/pseitz/lz4_flex/compare/0.11...0.12.0">compare
view</a></li>
</ul>
</details>
<br />


Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop
Dependabot creating any more for this major version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop
Dependabot creating any more for this minor version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)


</details>

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
# Objective

Remove a double space in a doc comment for `PointerButtonState`.

## Solution

Delete it.
Bumps [actions/checkout](https://github.com/actions/checkout) from 5 to
6.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/actions/checkout/releases">actions/checkout's
releases</a>.</em></p>
<blockquote>
<h2>v6.0.0</h2>
<h2>What's Changed</h2>
<ul>
<li>Update README to include Node.js 24 support details and requirements
by <a href="https://github.com/salmanmkc"><code>@​salmanmkc</code></a>
in <a
href="https://redirect.github.com/actions/checkout/pull/2248">actions/checkout#2248</a></li>
<li>Persist creds to a separate file by <a
href="https://github.com/ericsciple"><code>@​ericsciple</code></a> in <a
href="https://redirect.github.com/actions/checkout/pull/2286">actions/checkout#2286</a></li>
<li>v6-beta by <a
href="https://github.com/ericsciple"><code>@​ericsciple</code></a> in <a
href="https://redirect.github.com/actions/checkout/pull/2298">actions/checkout#2298</a></li>
<li>update readme/changelog for v6 by <a
href="https://github.com/ericsciple"><code>@​ericsciple</code></a> in <a
href="https://redirect.github.com/actions/checkout/pull/2311">actions/checkout#2311</a></li>
</ul>
<p><strong>Full Changelog</strong>: <a
href="https://github.com/actions/checkout/compare/v5.0.0...v6.0.0">https://github.com/actions/checkout/compare/v5.0.0...v6.0.0</a></p>
<h2>v6-beta</h2>
<h2>What's Changed</h2>
<p>Updated persist-credentials to store the credentials under
<code>$RUNNER_TEMP</code> instead of directly in the local git
config.</p>
<p>This requires a minimum Actions Runner version of <a
href="https://github.com/actions/runner/releases/tag/v2.329.0">v2.329.0</a>
to access the persisted credentials for <a
href="https://docs.github.com/en/actions/tutorials/use-containerized-services/create-a-docker-container-action">Docker
container action</a> scenarios.</p>
<h2>v5.0.1</h2>
<h2>What's Changed</h2>
<ul>
<li>Port v6 cleanup to v5 by <a
href="https://github.com/ericsciple"><code>@​ericsciple</code></a> in <a
href="https://redirect.github.com/actions/checkout/pull/2301">actions/checkout#2301</a></li>
</ul>
<p><strong>Full Changelog</strong>: <a
href="https://github.com/actions/checkout/compare/v5...v5.0.1">https://github.com/actions/checkout/compare/v5...v5.0.1</a></p>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/actions/checkout/blob/main/CHANGELOG.md">actions/checkout's
changelog</a>.</em></p>
<blockquote>
<h1>Changelog</h1>
<h2>V6.0.0</h2>
<ul>
<li>Persist creds to a separate file by <a
href="https://github.com/ericsciple"><code>@​ericsciple</code></a> in <a
href="https://redirect.github.com/actions/checkout/pull/2286">actions/checkout#2286</a></li>
<li>Update README to include Node.js 24 support details and requirements
by <a href="https://github.com/salmanmkc"><code>@​salmanmkc</code></a>
in <a
href="https://redirect.github.com/actions/checkout/pull/2248">actions/checkout#2248</a></li>
</ul>
<h2>V5.0.1</h2>
<ul>
<li>Port v6 cleanup to v5 by <a
href="https://github.com/ericsciple"><code>@​ericsciple</code></a> in <a
href="https://redirect.github.com/actions/checkout/pull/2301">actions/checkout#2301</a></li>
</ul>
<h2>V5.0.0</h2>
<ul>
<li>Update actions checkout to use node 24 by <a
href="https://github.com/salmanmkc"><code>@​salmanmkc</code></a> in <a
href="https://redirect.github.com/actions/checkout/pull/2226">actions/checkout#2226</a></li>
</ul>
<h2>V4.3.1</h2>
<ul>
<li>Port v6 cleanup to v4 by <a
href="https://github.com/ericsciple"><code>@​ericsciple</code></a> in <a
href="https://redirect.github.com/actions/checkout/pull/2305">actions/checkout#2305</a></li>
</ul>
<h2>V4.3.0</h2>
<ul>
<li>docs: update README.md by <a
href="https://github.com/motss"><code>@​motss</code></a> in <a
href="https://redirect.github.com/actions/checkout/pull/1971">actions/checkout#1971</a></li>
<li>Add internal repos for checking out multiple repositories by <a
href="https://github.com/mouismail"><code>@​mouismail</code></a> in <a
href="https://redirect.github.com/actions/checkout/pull/1977">actions/checkout#1977</a></li>
<li>Documentation update - add recommended permissions to Readme by <a
href="https://github.com/benwells"><code>@​benwells</code></a> in <a
href="https://redirect.github.com/actions/checkout/pull/2043">actions/checkout#2043</a></li>
<li>Adjust positioning of user email note and permissions heading by <a
href="https://github.com/joshmgross"><code>@​joshmgross</code></a> in <a
href="https://redirect.github.com/actions/checkout/pull/2044">actions/checkout#2044</a></li>
<li>Update README.md by <a
href="https://github.com/nebuk89"><code>@​nebuk89</code></a> in <a
href="https://redirect.github.com/actions/checkout/pull/2194">actions/checkout#2194</a></li>
<li>Update CODEOWNERS for actions by <a
href="https://github.com/TingluoHuang"><code>@​TingluoHuang</code></a>
in <a
href="https://redirect.github.com/actions/checkout/pull/2224">actions/checkout#2224</a></li>
<li>Update package dependencies by <a
href="https://github.com/salmanmkc"><code>@​salmanmkc</code></a> in <a
href="https://redirect.github.com/actions/checkout/pull/2236">actions/checkout#2236</a></li>
</ul>
<h2>v4.2.2</h2>
<ul>
<li><code>url-helper.ts</code> now leverages well-known environment
variables by <a href="https://github.com/jww3"><code>@​jww3</code></a>
in <a
href="https://redirect.github.com/actions/checkout/pull/1941">actions/checkout#1941</a></li>
<li>Expand unit test coverage for <code>isGhes</code> by <a
href="https://github.com/jww3"><code>@​jww3</code></a> in <a
href="https://redirect.github.com/actions/checkout/pull/1946">actions/checkout#1946</a></li>
</ul>
<h2>v4.2.1</h2>
<ul>
<li>Check out other refs/* by commit if provided, fall back to ref by <a
href="https://github.com/orhantoy"><code>@​orhantoy</code></a> in <a
href="https://redirect.github.com/actions/checkout/pull/1924">actions/checkout#1924</a></li>
</ul>
<h2>v4.2.0</h2>
<ul>
<li>Add Ref and Commit outputs by <a
href="https://github.com/lucacome"><code>@​lucacome</code></a> in <a
href="https://redirect.github.com/actions/checkout/pull/1180">actions/checkout#1180</a></li>
<li>Dependency updates by <a
href="https://github.com/dependabot"><code>@​dependabot</code></a>- <a
href="https://redirect.github.com/actions/checkout/pull/1777">actions/checkout#1777</a>,
<a
href="https://redirect.github.com/actions/checkout/pull/1872">actions/checkout#1872</a></li>
</ul>
<h2>v4.1.7</h2>
<ul>
<li>Bump the minor-npm-dependencies group across 1 directory with 4
updates by <a
href="https://github.com/dependabot"><code>@​dependabot</code></a> in <a
href="https://redirect.github.com/actions/checkout/pull/1739">actions/checkout#1739</a></li>
<li>Bump actions/checkout from 3 to 4 by <a
href="https://github.com/dependabot"><code>@​dependabot</code></a> in <a
href="https://redirect.github.com/actions/checkout/pull/1697">actions/checkout#1697</a></li>
<li>Check out other refs/* by commit by <a
href="https://github.com/orhantoy"><code>@​orhantoy</code></a> in <a
href="https://redirect.github.com/actions/checkout/pull/1774">actions/checkout#1774</a></li>
<li>Pin actions/checkout's own workflows to a known, good, stable
version. by <a href="https://github.com/jww3"><code>@​jww3</code></a> in
<a
href="https://redirect.github.com/actions/checkout/pull/1776">actions/checkout#1776</a></li>
</ul>
<h2>v4.1.6</h2>
<ul>
<li>Check platform to set archive extension appropriately by <a
href="https://github.com/cory-miller"><code>@​cory-miller</code></a> in
<a
href="https://redirect.github.com/actions/checkout/pull/1732">actions/checkout#1732</a></li>
</ul>
<h2>v4.1.5</h2>
<ul>
<li>Update NPM dependencies by <a
href="https://github.com/cory-miller"><code>@​cory-miller</code></a> in
<a
href="https://redirect.github.com/actions/checkout/pull/1703">actions/checkout#1703</a></li>
<li>Bump github/codeql-action from 2 to 3 by <a
href="https://github.com/dependabot"><code>@​dependabot</code></a> in <a
href="https://redirect.github.com/actions/checkout/pull/1694">actions/checkout#1694</a></li>
<li>Bump actions/setup-node from 1 to 4 by <a
href="https://github.com/dependabot"><code>@​dependabot</code></a> in <a
href="https://redirect.github.com/actions/checkout/pull/1696">actions/checkout#1696</a></li>
<li>Bump actions/upload-artifact from 2 to 4 by <a
href="https://github.com/dependabot"><code>@​dependabot</code></a> in <a
href="https://redirect.github.com/actions/checkout/pull/1695">actions/checkout#1695</a></li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/actions/checkout/commit/1af3b93b6815bc44a9784bd300feb67ff0d1eeb3"><code>1af3b93</code></a>
update readme/changelog for v6 (<a
href="https://redirect.github.com/actions/checkout/issues/2311">#2311</a>)</li>
<li><a
href="https://github.com/actions/checkout/commit/71cf2267d89c5cb81562390fa70a37fa40b1305e"><code>71cf226</code></a>
v6-beta (<a
href="https://redirect.github.com/actions/checkout/issues/2298">#2298</a>)</li>
<li><a
href="https://github.com/actions/checkout/commit/069c6959146423d11cd0184e6accf28f9d45f06e"><code>069c695</code></a>
Persist creds to a separate file (<a
href="https://redirect.github.com/actions/checkout/issues/2286">#2286</a>)</li>
<li><a
href="https://github.com/actions/checkout/commit/ff7abcd0c3c05ccf6adc123a8cd1fd4fb30fb493"><code>ff7abcd</code></a>
Update README to include Node.js 24 support details and requirements (<a
href="https://redirect.github.com/actions/checkout/issues/2248">#2248</a>)</li>
<li>See full diff in <a
href="https://github.com/actions/checkout/compare/v5...v6">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=actions/checkout&package-manager=github_actions&previous-version=5&new-version=6)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop
Dependabot creating any more for this major version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop
Dependabot creating any more for this minor version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)


</details>

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…1965)

# Objective

- The `update_text()` system was running on every frame, causing
unnecessary performance overhead.

## Solution

- Refactored it to use `on_timer()` to run on a configurable interval.

## Testing

- Ran the `fps_overlay.rs` example; the overlay works correctly and the
new performance warning triggers as expected.

---
# Objective

- Part of bevyengine#20115

We should try to minimize allocations where its easy to do so.

## Solution

Pre-allocate things upfront where we know their exact resulting size.

## Testing

It'd probably be good to benchmark to see how much (if any) this helps.
)

After many many hours of debugging, I narrowed down the energy loss in
solari to rgb9e5float issues.

All credit to @SparkyPotato for the solution, which is to use a log
scale.

With this fix:
<img width="2564" height="1500" alt="image"
src="https://github.com/user-attachments/assets/96d34e39-b2e6-48aa-97f3-aeea835d1305"
/>

Without this fix:
<img width="2564" height="1500" alt="image"
src="https://github.com/user-attachments/assets/83be5dc0-e6ca-4561-bdcc-c5ecd8db51a4"
/>

Pathtraced reference:
<img width="2564" height="1500" alt="image"
src="https://github.com/user-attachments/assets/cdd73e51-7e60-486d-8868-446a0c46bd1a"
/>
In bevyengine#21649, I switched where
visibility rays get traced, and while it improved DI, it regressed GI.
I'm reverting the GI change to fix.

Before:
<img width="3206" height="1875" alt="image"
src="https://github.com/user-attachments/assets/379c613a-2a36-4fe0-81f1-9e278b28ca37"
/>

After:
<img width="3206" height="1875" alt="image"
src="https://github.com/user-attachments/assets/56f5c457-6639-4b48-9472-8cd2ad4936d8"
/>
…1974)

# Objective

Fixes bevyengine#21815 

## Solution

- Adds a new scene to `examples/testbed/ui` called `Transformations`
that calls some basic `UiTransform`s on Nodes.

This is my first PR for Bevy!

## Testing

I ran the example via console to test out the scene.

Tested on Desktop MacOS 15.7.1

## Showcase

<img width="902" height="780" alt="Screenshot 2025-11-29 at 11 29 52 AM"
src="https://github.com/user-attachments/assets/602ab485-61dd-4887-a0ad-0624b3d79db8"
/>

To view, run in console: `cargo run --package bevy --example testbed_ui`
Press spacebar 11x until you see the new scene.
# Objective

Cleanup code that was previously required in older rust versions but is
no longer needed in newer versions.

## Solution

[As of rust 1.79.0, we can put bounds on associated types
directly](https://blog.rust-lang.org/2024/06/13/Rust-1.79.0/#bounds-in-associated-type-position),
so lets do that for `SystemCondition`.
# Objective

`bevy_math` does not work when no `alloc` is available despite the
existance of the `alloc` feature which should gate all logic that
requires it. Support for no std + no alloc can be useful for some
embedded usecases, for example using `bevy_math` types on the GPU using
Rust GPU.

## Solution

Swap `smallvec` out with `arrayvec`, and fix two minor uses of
`alloc::slice::sort_by` (not available on `core` because they allocate
`Vec`s internally)

## Testing

- Unit tests still pass
- I was able to compile a shader with Rust GPU while depending on
bevy_math
# Objective

- Calling `Hashed::new` could be annoying if a function accepts it.

## Solution

- Add `From` impl to allow creating functions that accepts `impl
From<V>`.
Bumps
[super-linter/super-linter](https://github.com/super-linter/super-linter)
from 8.2.1 to 8.3.0.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/super-linter/super-linter/releases">super-linter/super-linter's
releases</a>.</em></p>
<blockquote>
<h2>v8.3.0</h2>
<h2><a
href="https://github.com/super-linter/super-linter/compare/v8.2.1...v8.3.0">8.3.0</a>
(2025-11-28)</h2>
<h3>🚀 Features</h3>
<ul>
<li>add ability to specify config files for nbqa tools (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7184">#7184</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/b37c1c33a78f7cbf9bfa04609b83180319421bfc">b37c1c3</a>)</li>
<li>lint dependabot, github actions with zizmor (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7241">#7241</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/09306cdabe5c1afaedcab156e7a75b88575c829b">09306cd</a>),
closes <a
href="https://redirect.github.com/super-linter/super-linter/issues/7137">#7137</a></li>
<li>support rust 2024 (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7211">#7211</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/c15ee6dd7d559940b734579617c3637b9c007f6f">c15ee6d</a>),
closes <a
href="https://redirect.github.com/super-linter/super-linter/issues/7139">#7139</a></li>
</ul>
<h3>🐛 Bugfixes</h3>
<ul>
<li>parse json to extract terraform version (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7239">#7239</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/29f17277db2147d8af291ae20e5c792b499052c7">29f1727</a>)</li>
</ul>
<h3>⬆️ Dependency updates</h3>
<ul>
<li><strong>bundler:</strong> bump rubocop in /dependencies in the
rubocop group (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7188">#7188</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/74b24446f8c7575d1b83edc5c975726d9e47416a">74b2444</a>)</li>
<li><strong>bundler:</strong> bump rubocop-rails in /dependencies in the
rubocop group (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7231">#7231</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/dd55c528c7a818fc25840f934f8a8d8c8264bab7">dd55c52</a>)</li>
<li><strong>bundler:</strong> bump the rubocop group in /dependencies
with 2 updates (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7178">#7178</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/3bdc91928162635ba67a148016a0ee29846087c6">3bdc919</a>)</li>
<li><strong>bundler:</strong> bump the rubocop group in /dependencies
with 4 updates (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7202">#7202</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/0e09528bdf1e450d83fab9ce2400225a11c7657d">0e09528</a>)</li>
<li><strong>docker:</strong> bump python in the docker-base-images group
(<a
href="https://redirect.github.com/super-linter/super-linter/issues/7123">#7123</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/41c3da1d09d0e5ec067ad65c9b855c6aeff225bc">41c3da1</a>)</li>
<li><strong>docker:</strong> bump the docker group across 1 directory
with 12 updates (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7235">#7235</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/b1cf27d548d8e772a89094d18b52c6d097b5ba08">b1cf27d</a>)</li>
<li><strong>docker:</strong> bump the docker group across 1 directory
with 6 updates (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7148">#7148</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/76149cff49dabb7f045e86f46e93f6767e2da34d">76149cf</a>)</li>
<li><strong>docker:</strong> bump the docker group across 1 directory
with 9 updates (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7194">#7194</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/45f731ea75a53496824bd31bb77c6ceab71a18ec">45f731e</a>)</li>
<li><strong>npm:</strong> bump <code>@​babel/eslint-parser</code> in
/dependencies (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7183">#7183</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/197eb8863a766dcfcf4c4ca670dc8560a9db85c6">197eb88</a>)</li>
<li><strong>npm:</strong> bump
<code>@​typescript-eslint/eslint-plugin</code> (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7127">#7127</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/2d57f06c64c521f2cfbbea3b8cc9c8f080fb473a">2d57f06</a>)</li>
<li><strong>npm:</strong> bump
<code>@​typescript-eslint/eslint-plugin</code> (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7196">#7196</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/033ea992a1aa5a0d4f868c2a3d401008ef218d9a">033ea99</a>)</li>
<li><strong>npm:</strong> bump body-parser from 2.2.0 to 2.2.1 in
/dependencies (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7238">#7238</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/30403f6aa43e234b7196dfd2eaa425b05294aa4c">30403f6</a>)</li>
<li><strong>npm:</strong> bump eslint from 9.37.0 to 9.38.0 in
/dependencies (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7170">#7170</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/b42af6f21b7bc5b827acd2c977b6047baad41ce9">b42af6f</a>)</li>
<li><strong>npm:</strong> bump eslint from 9.38.0 to 9.39.0 in
/dependencies (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7191">#7191</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/0cf22c89f925988556f38fcce929adde347f527b">0cf22c8</a>)</li>
<li><strong>npm:</strong> bump eslint from 9.39.0 to 9.39.1 in
/dependencies (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7197">#7197</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/513ae8ba519bb2c67e124d0fa1f03aff521babaa">513ae8b</a>)</li>
<li><strong>npm:</strong> bump eslint-plugin-react-hooks (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7180">#7180</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/61e42084aa3bc2771777fc56ca15f2b480117106">61e4208</a>)</li>
<li><strong>npm:</strong> bump js-yaml from 3.14.1 to 3.14.2 in
/dependencies (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7210">#7210</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/29faa987594b8d482545899275cd14bfc3cfe6bd">29faa98</a>)</li>
<li><strong>npm:</strong> bump npm-groovy-lint from 15.2.1 to 15.2.2 in
/dependencies (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7130">#7130</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/49138252344a9c051b5d4c4f12cc660d670415d8">4913825</a>)</li>
<li><strong>npm:</strong> bump renovate from 41.142.0 to 41.146.5 in
/dependencies (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7134">#7134</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/900b973697b89c3d89462a12bdd556c8dec5b4d0">900b973</a>)</li>
<li><strong>npm:</strong> bump renovate from 41.151.1 to 41.161.0 in
/dependencies (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7182">#7182</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/1d8c2a20d753278a958cf2a5f8c5b264bd1807c4">1d8c2a2</a>)</li>
<li><strong>npm:</strong> bump renovate from 41.161.0 to 42.4.0 in
/dependencies (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7198">#7198</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/0a4ed306a12b6a923c8c5ae80b798fd64314e193">0a4ed30</a>)</li>
<li><strong>npm:</strong> bump the eslint-plugins-configs group across 1
directory with 2 updates (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7145">#7145</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/c137ca99f70bb902052d71b0191dd000fb2390a1">c137ca9</a>)</li>
<li><strong>npm:</strong> bump the npm group across 1 directory with 2
updates (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7175">#7175</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/f0b0ff5c9a26aac384cd4b016a099932ec2f96a9">f0b0ff5</a>)</li>
<li><strong>npm:</strong> bump the npm group across 1 directory with 3
updates (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7146">#7146</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/d4d3f168263fb5ae8b10cec7280d34954230f0a0">d4d3f16</a>)</li>
<li><strong>npm:</strong> bump the npm group across 1 directory with 3
updates (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7195">#7195</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/ad4f63c1683738277ceb276609c1acedf4f72ca9">ad4f63c</a>)</li>
<li><strong>npm:</strong> bump the npm group across 1 directory with 5
updates (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7233">#7233</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/5cadbf190ab223e8deab07f2415670e0aef342d9">5cadbf1</a>)</li>
<li><strong>npm:</strong> bump the npm group across 1 directory with 8
updates (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7221">#7221</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/3802c521f77bf81bda1453e9ba189a6e442a0dbb">3802c52</a>)</li>
<li><strong>npm:</strong> bump the react group across 1 directory with 2
updates (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7190">#7190</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/d6c8078d417d100057ba28b372755aa78d9cbf0b">d6c8078</a>)</li>
<li><strong>npm:</strong> bump the react group across 1 directory with 4
updates (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7128">#7128</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/40347029803087080f7cc79e7ca129c1e6b7cbd1">4034702</a>)</li>
<li><strong>npm:</strong> bump the typescript group across 1 directory
with 2 updates (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7176">#7176</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/39aba7679238de915382df7ecbe0194bc6677af9">39aba76</a>)</li>
<li><strong>python:</strong> bump the pip group across 1 directory with
11 updates (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7199">#7199</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/07fbf76c2cf08a5c12b51f73329ae4ddc0c93d22">07fbf76</a>)</li>
<li><strong>python:</strong> bump the pip group across 1 directory with
3 updates (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7234">#7234</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/c8bd6d308cdb7dc47ef439de8edff221afca95d2">c8bd6d3</a>)</li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/super-linter/super-linter/blob/main/CHANGELOG.md">super-linter/super-linter's
changelog</a>.</em></p>
<blockquote>
<h2><a
href="https://github.com/super-linter/super-linter/compare/v8.2.1...v8.3.0">8.3.0</a>
(2025-11-28)</h2>
<h3>🚀 Features</h3>
<ul>
<li>add ability to specify config files for nbqa tools (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7184">#7184</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/b37c1c33a78f7cbf9bfa04609b83180319421bfc">b37c1c3</a>)</li>
<li>lint dependabot, github actions with zizmor (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7241">#7241</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/09306cdabe5c1afaedcab156e7a75b88575c829b">09306cd</a>),
closes <a
href="https://redirect.github.com/super-linter/super-linter/issues/7137">#7137</a></li>
<li>support rust 2024 (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7211">#7211</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/c15ee6dd7d559940b734579617c3637b9c007f6f">c15ee6d</a>),
closes <a
href="https://redirect.github.com/super-linter/super-linter/issues/7139">#7139</a></li>
</ul>
<h3>🐛 Bugfixes</h3>
<ul>
<li>parse json to extract terraform version (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7239">#7239</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/29f17277db2147d8af291ae20e5c792b499052c7">29f1727</a>)</li>
</ul>
<h3>⬆️ Dependency updates</h3>
<ul>
<li><strong>bundler:</strong> bump rubocop in /dependencies in the
rubocop group (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7188">#7188</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/74b24446f8c7575d1b83edc5c975726d9e47416a">74b2444</a>)</li>
<li><strong>bundler:</strong> bump rubocop-rails in /dependencies in the
rubocop group (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7231">#7231</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/dd55c528c7a818fc25840f934f8a8d8c8264bab7">dd55c52</a>)</li>
<li><strong>bundler:</strong> bump the rubocop group in /dependencies
with 2 updates (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7178">#7178</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/3bdc91928162635ba67a148016a0ee29846087c6">3bdc919</a>)</li>
<li><strong>bundler:</strong> bump the rubocop group in /dependencies
with 4 updates (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7202">#7202</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/0e09528bdf1e450d83fab9ce2400225a11c7657d">0e09528</a>)</li>
<li><strong>docker:</strong> bump python in the docker-base-images group
(<a
href="https://redirect.github.com/super-linter/super-linter/issues/7123">#7123</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/41c3da1d09d0e5ec067ad65c9b855c6aeff225bc">41c3da1</a>)</li>
<li><strong>docker:</strong> bump the docker group across 1 directory
with 12 updates (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7235">#7235</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/b1cf27d548d8e772a89094d18b52c6d097b5ba08">b1cf27d</a>)</li>
<li><strong>docker:</strong> bump the docker group across 1 directory
with 6 updates (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7148">#7148</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/76149cff49dabb7f045e86f46e93f6767e2da34d">76149cf</a>)</li>
<li><strong>docker:</strong> bump the docker group across 1 directory
with 9 updates (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7194">#7194</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/45f731ea75a53496824bd31bb77c6ceab71a18ec">45f731e</a>)</li>
<li><strong>npm:</strong> bump <code>@​babel/eslint-parser</code> in
/dependencies (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7183">#7183</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/197eb8863a766dcfcf4c4ca670dc8560a9db85c6">197eb88</a>)</li>
<li><strong>npm:</strong> bump
<code>@​typescript-eslint/eslint-plugin</code> (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7127">#7127</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/2d57f06c64c521f2cfbbea3b8cc9c8f080fb473a">2d57f06</a>)</li>
<li><strong>npm:</strong> bump
<code>@​typescript-eslint/eslint-plugin</code> (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7196">#7196</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/033ea992a1aa5a0d4f868c2a3d401008ef218d9a">033ea99</a>)</li>
<li><strong>npm:</strong> bump body-parser from 2.2.0 to 2.2.1 in
/dependencies (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7238">#7238</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/30403f6aa43e234b7196dfd2eaa425b05294aa4c">30403f6</a>)</li>
<li><strong>npm:</strong> bump eslint from 9.37.0 to 9.38.0 in
/dependencies (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7170">#7170</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/b42af6f21b7bc5b827acd2c977b6047baad41ce9">b42af6f</a>)</li>
<li><strong>npm:</strong> bump eslint from 9.38.0 to 9.39.0 in
/dependencies (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7191">#7191</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/0cf22c89f925988556f38fcce929adde347f527b">0cf22c8</a>)</li>
<li><strong>npm:</strong> bump eslint from 9.39.0 to 9.39.1 in
/dependencies (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7197">#7197</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/513ae8ba519bb2c67e124d0fa1f03aff521babaa">513ae8b</a>)</li>
<li><strong>npm:</strong> bump eslint-plugin-react-hooks (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7180">#7180</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/61e42084aa3bc2771777fc56ca15f2b480117106">61e4208</a>)</li>
<li><strong>npm:</strong> bump js-yaml from 3.14.1 to 3.14.2 in
/dependencies (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7210">#7210</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/29faa987594b8d482545899275cd14bfc3cfe6bd">29faa98</a>)</li>
<li><strong>npm:</strong> bump npm-groovy-lint from 15.2.1 to 15.2.2 in
/dependencies (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7130">#7130</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/49138252344a9c051b5d4c4f12cc660d670415d8">4913825</a>)</li>
<li><strong>npm:</strong> bump renovate from 41.142.0 to 41.146.5 in
/dependencies (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7134">#7134</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/900b973697b89c3d89462a12bdd556c8dec5b4d0">900b973</a>)</li>
<li><strong>npm:</strong> bump renovate from 41.151.1 to 41.161.0 in
/dependencies (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7182">#7182</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/1d8c2a20d753278a958cf2a5f8c5b264bd1807c4">1d8c2a2</a>)</li>
<li><strong>npm:</strong> bump renovate from 41.161.0 to 42.4.0 in
/dependencies (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7198">#7198</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/0a4ed306a12b6a923c8c5ae80b798fd64314e193">0a4ed30</a>)</li>
<li><strong>npm:</strong> bump the eslint-plugins-configs group across 1
directory with 2 updates (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7145">#7145</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/c137ca99f70bb902052d71b0191dd000fb2390a1">c137ca9</a>)</li>
<li><strong>npm:</strong> bump the npm group across 1 directory with 2
updates (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7175">#7175</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/f0b0ff5c9a26aac384cd4b016a099932ec2f96a9">f0b0ff5</a>)</li>
<li><strong>npm:</strong> bump the npm group across 1 directory with 3
updates (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7146">#7146</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/d4d3f168263fb5ae8b10cec7280d34954230f0a0">d4d3f16</a>)</li>
<li><strong>npm:</strong> bump the npm group across 1 directory with 3
updates (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7195">#7195</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/ad4f63c1683738277ceb276609c1acedf4f72ca9">ad4f63c</a>)</li>
<li><strong>npm:</strong> bump the npm group across 1 directory with 5
updates (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7233">#7233</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/5cadbf190ab223e8deab07f2415670e0aef342d9">5cadbf1</a>)</li>
<li><strong>npm:</strong> bump the npm group across 1 directory with 8
updates (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7221">#7221</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/3802c521f77bf81bda1453e9ba189a6e442a0dbb">3802c52</a>)</li>
<li><strong>npm:</strong> bump the react group across 1 directory with 2
updates (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7190">#7190</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/d6c8078d417d100057ba28b372755aa78d9cbf0b">d6c8078</a>)</li>
<li><strong>npm:</strong> bump the react group across 1 directory with 4
updates (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7128">#7128</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/40347029803087080f7cc79e7ca129c1e6b7cbd1">4034702</a>)</li>
<li><strong>npm:</strong> bump the typescript group across 1 directory
with 2 updates (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7176">#7176</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/39aba7679238de915382df7ecbe0194bc6677af9">39aba76</a>)</li>
<li><strong>python:</strong> bump the pip group across 1 directory with
11 updates (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7199">#7199</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/07fbf76c2cf08a5c12b51f73329ae4ddc0c93d22">07fbf76</a>)</li>
<li><strong>python:</strong> bump the pip group across 1 directory with
3 updates (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7234">#7234</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/c8bd6d308cdb7dc47ef439de8edff221afca95d2">c8bd6d3</a>)</li>
<li><strong>python:</strong> bump the pip group across 1 directory with
4 updates (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7219">#7219</a>)
(<a
href="https://github.com/super-linter/super-linter/commit/91361a34fd58bc5dc83b52e0bd25114a06223fab">91361a3</a>)</li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/super-linter/super-linter/commit/502f4fe48a81a392756e173e39a861f8c8efe056"><code>502f4fe</code></a>
chore(main): release 8.3.0 (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7149">#7149</a>)</li>
<li><a
href="https://github.com/super-linter/super-linter/commit/13997378fdbc9d06dd8791ab2ff8985d27810d58"><code>1399737</code></a>
chore: update google-java-format to 1.29.0 (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7104">#7104</a>)</li>
<li><a
href="https://github.com/super-linter/super-linter/commit/b1cf27d548d8e772a89094d18b52c6d097b5ba08"><code>b1cf27d</code></a>
deps(docker): bump the docker group across 1 directory with 12 updates
(<a
href="https://redirect.github.com/super-linter/super-linter/issues/7235">#7235</a>)</li>
<li><a
href="https://github.com/super-linter/super-linter/commit/09306cdabe5c1afaedcab156e7a75b88575c829b"><code>09306cd</code></a>
feat: lint dependabot, github actions with zizmor (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7241">#7241</a>)</li>
<li><a
href="https://github.com/super-linter/super-linter/commit/5aa81e2b92d9cec28bdd7183b8197383aace3203"><code>5aa81e2</code></a>
chore: set devcontainer name (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7240">#7240</a>)</li>
<li><a
href="https://github.com/super-linter/super-linter/commit/29f17277db2147d8af291ae20e5c792b499052c7"><code>29f1727</code></a>
fix: parse json to extract terraform version (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7239">#7239</a>)</li>
<li><a
href="https://github.com/super-linter/super-linter/commit/30403f6aa43e234b7196dfd2eaa425b05294aa4c"><code>30403f6</code></a>
deps(npm): bump body-parser from 2.2.0 to 2.2.1 in /dependencies (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7238">#7238</a>)</li>
<li><a
href="https://github.com/super-linter/super-linter/commit/c8bd6d308cdb7dc47ef439de8edff221afca95d2"><code>c8bd6d3</code></a>
deps(python): bump the pip group across 1 directory with 3 updates (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7234">#7234</a>)</li>
<li><a
href="https://github.com/super-linter/super-linter/commit/5cadbf190ab223e8deab07f2415670e0aef342d9"><code>5cadbf1</code></a>
deps(npm): bump the npm group across 1 directory with 5 updates (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7233">#7233</a>)</li>
<li><a
href="https://github.com/super-linter/super-linter/commit/f40c1749ad03cda5cbb70dd78fd74c9f2a8209a6"><code>f40c174</code></a>
ci(github-actions): bump actions/checkout in the dev-ci-tools group (<a
href="https://redirect.github.com/super-linter/super-linter/issues/7232">#7232</a>)</li>
<li>Additional commits viewable in <a
href="https://github.com/super-linter/super-linter/compare/v8.2.1...v8.3.0">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=super-linter/super-linter&package-manager=github_actions&previous-version=8.2.1&new-version=8.3.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop
Dependabot creating any more for this major version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop
Dependabot creating any more for this minor version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)


</details>

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [crate-ci/typos](https://github.com/crate-ci/typos) from 1.39.2 to
1.40.0.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/crate-ci/typos/releases">crate-ci/typos's
releases</a>.</em></p>
<blockquote>
<h2>v1.40.0</h2>
<h2>[1.40.0] - 2025-11-26</h2>
<h3>Features</h3>
<ul>
<li>Updated the dictionary with the <a
href="https://redirect.github.com/crate-ci/typos/issues/1405">November
2025</a> changes</li>
</ul>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/crate-ci/typos/blob/master/CHANGELOG.md">crate-ci/typos's
changelog</a>.</em></p>
<blockquote>
<h2>[1.40.0] - 2025-11-26</h2>
<h3>Features</h3>
<ul>
<li>Updated the dictionary with the <a
href="https://redirect.github.com/crate-ci/typos/issues/1405">November
2025</a> changes</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/crate-ci/typos/commit/2d0ce569feab1f8752f1dde43cc2f2aa53236e06"><code>2d0ce56</code></a>
chore: Release</li>
<li><a
href="https://github.com/crate-ci/typos/commit/efbd900f8db9952781b6bd1ad83baa38ebd153e3"><code>efbd900</code></a>
chore: Release</li>
<li><a
href="https://github.com/crate-ci/typos/commit/863fd15db8bf16bfe9117ec1a83ea7b6e802e9f3"><code>863fd15</code></a>
docs: Update changelog</li>
<li><a
href="https://github.com/crate-ci/typos/commit/9a27b16791dd73549457a07f247bc4920f787919"><code>9a27b16</code></a>
Merge pull request <a
href="https://redirect.github.com/crate-ci/typos/issues/1432">#1432</a>
from epage/nov</li>
<li><a
href="https://github.com/crate-ci/typos/commit/3dbd9d4eacab7f22586ea581e4d403c3ca9dbbb7"><code>3dbd9d4</code></a>
feat(dict): November additions</li>
<li><a
href="https://github.com/crate-ci/typos/commit/a1a16c7b7c25d1c27cc750525aada8b9ae68b716"><code>a1a16c7</code></a>
Merge pull request <a
href="https://redirect.github.com/crate-ci/typos/issues/1427">#1427</a>
from deining/bump-github-action</li>
<li><a
href="https://github.com/crate-ci/typos/commit/cb8d2e78ff23c82fca05340ed256b04513d022b9"><code>cb8d2e7</code></a>
docs: Bump GitHub checkout action in 'github-action.md'</li>
<li><a
href="https://github.com/crate-ci/typos/commit/9f99fb8dfe87b8a3441863fb2e5d5da88a2aa9a2"><code>9f99fb8</code></a>
docs(ref): Clarify extend-words / extend-identifiers</li>
<li>See full diff in <a
href="https://github.com/crate-ci/typos/compare/v1.39.2...v1.40.0">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=crate-ci/typos&package-manager=github_actions&previous-version=1.39.2&new-version=1.40.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop
Dependabot creating any more for this major version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop
Dependabot creating any more for this minor version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)


</details>

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Updates the requirements on
[criterion](https://github.com/criterion-rs/criterion.rs) to permit the
latest version.
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/criterion-rs/criterion.rs/blob/master/CHANGELOG.md">criterion's
changelog</a>.</em></p>
<blockquote>
<h2><a
href="https://github.com/criterion-rs/criterion.rs/compare/criterion-v0.7.0...criterion-v0.8.0">0.8.0</a>
- 2025-11-29</h2>
<h3>BREAKING</h3>
<ul>
<li>Drop async-std support</li>
</ul>
<h3>Changed</h3>
<ul>
<li>Bump MSRV to 1.86, stable to 1.91.1</li>
</ul>
<h3>Added</h3>
<ul>
<li>Add ability to plot throughput on summary page.</li>
<li>Add support for reporting throughput in elements and bytes -
<code>Throughput::ElementsAndBytes</code> allows the text summary to
report throughput in both units simultaneously.</li>
<li>Add alloca-based memory layout randomisation to mitigate memory
effects on measurements.</li>
<li>Add doc comment to benchmark runner in criterion_group macro
(removes linter warnings)</li>
</ul>
<h3>Fixed</h3>
<ul>
<li>Fix plotting NaN bug</li>
</ul>
<h3>Other</h3>
<ul>
<li>Remove Master API Docs links temporarily while we restore the docs
publishing.</li>
</ul>
<h2>[0.7.0] - 2025-07-25</h2>
<ul>
<li>Bump version of criterion-plot to align dependencies.</li>
</ul>
<h2>[0.6.0] - 2025-05-17</h2>
<h3>Changed</h3>
<ul>
<li>MSRV bumped to 1.80</li>
<li>The <code>real_blackbox</code> feature no longer has any impact.
Criterion always uses <code>std::hint::black_box()</code> now.
Users of <code>criterion::black_box()</code> should switch to
<code>std::hint::black_box()</code>.</li>
<li><code>clap</code> dependency unpinned.</li>
</ul>
<h3>Fixed</h3>
<ul>
<li>gnuplot version is now correctly detected when using certain Windows
binaries/configurations that used to fail</li>
</ul>
<h3>Added</h3>
<ul>
<li>Async benchmarking with Tokio may be done via a
<code>tokio::runtime::Handle</code>, not only a
<code>tokio::runtime::Runtime</code></li>
</ul>
<h2>[0.5.1] - 2023-05-26</h2>
<h3>Fixed</h3>
<ul>
<li>Quick mode (--quick) no longer crashes with measured times over 5
seconds when --noplot is not active</li>
</ul>
<h2>[0.5.0] - 2023-05-23</h2>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/criterion-rs/criterion.rs/commit/b49ade728c064f49cb2a70b0368658a15cf21833"><code>b49ade7</code></a>
chore: release v0.8.0</li>
<li>See full diff in <a
href="https://github.com/criterion-rs/criterion.rs/compare/criterion-plot-v0.7.0...criterion-v0.8.0">compare
view</a></li>
</ul>
</details>
<br />


Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop
Dependabot creating any more for this major version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop
Dependabot creating any more for this minor version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)


</details>

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.