Bump the deps group across 1 directory with 9 updates

[dependabot]

Bumps the deps group with 9 updates in the / directory:

Package	From	To
winit	0.30.2	0.30.4
clap	4.5.7	4.5.11
bitflags	2.5.0	2.6.0
log	0.4.21	0.4.22
wgpu	0.20.1	22.0.0
bytemuck	1.16.0	1.16.1
serde	1.0.203	1.0.204
toml	0.8.14	0.8.16
librashader	fff80df	f6cf642

Updates winit from 0.30.2 to 0.30.4

Release notes

Sourced from winit's releases.

Winit version 0.30.4

Changed

• DeviceId::dummy() and WindowId::dummy() are no longer marked unsafe.

Fixed

• On Wayland, avoid crashing when compositor is misbehaving.
• On Web, fix WindowEvent::Resized not using requestAnimationFrame when sending WindowEvent::RedrawRequested and also potentially causing WindowEvent::RedrawRequested to not be de-duplicated.
• Account for different browser engine implementations of pointer movement coordinate space.

Winit version 0.30.3

Added

• On Web, add EventLoopExtWebSys::(set_)poll_strategy() to allow setting control flow strategies before starting the event loop.
• On Web, add WaitUntilStrategy, which allows to set different strategies for ControlFlow::WaitUntil. By default the Prioritized Task Scheduling API is used, with a fallback to setTimeout() with a trick to circumvent throttling to 4ms. But an option to use a Web worker to schedule the timer is available as well, which commonly prevents any throttling when the window is not focused.

Changed

• On macOS, set the window theme on the NSWindow instead of application-wide.

Fixed

• On X11, build on arm platforms.
• On macOS, fixed WindowBuilder::with_theme not having any effect on the window.

Commits

• 04d8a28 Winit version 0.30.4
• 949cb0f Web: fix MouseMotion coordinate space (#3770)
• bf68ac0 Web: fix WindowEvent::Resized not using rAF (#3790)
• ba18837 wayland: bump dependencies
• 6509f8a Make DeviceId/WindowId::dummy() safe (#3784)
• 71dea46 Fix CI (#3775)
• ec24c3e wayland: ignore events for dead objects
• feca480 Avoid path when importing modules (#3755)
• 655fdc8 ci: Use taiki-e/checkout-action
• faa641e Add notgull as Windows maintainer
• Additional commits viewable in compare view

Updates clap from 4.5.7 to 4.5.11

Release notes

Sourced from clap's releases.

v4.5.10

[4.5.10] - 2024-07-23

v4.5.9

[4.5.9] - 2024-07-09

Fixes

• (error) When defining a custom help flag, be sure to suggest it like we do the built-in one

v4.5.8

[4.5.8] - 2024-06-28

Fixes

• Reduce extra flushes

Changelog

Sourced from clap's changelog.

[4.5.11] - 2024-07-25

[4.5.10] - 2024-07-23

[4.5.9] - 2024-07-09

Fixes

• (error) When defining a custom help flag, be sure to suggest it like we do the built-in one

[4.5.8] - 2024-06-28

Fixes

• Reduce extra flushes

Commits

• 349ed30 chore: Release
• 68ed9ff docs: Update changelog
• afecaa4 Merge pull request #5576 from shannmu/option_value_new
• 4a00677 chore: Release
• 36c849b refactor(clap_complete): Reuse code about shortflag parsing
• fc479ba feat(clap_complete): Add support for -fbar and -f=bar completion
• 48a23f5 test(clap_complete): Add test cases for -fbar and -f=bar completion
• 6b18d77 docs(derive): Acknowledge Vec<Vec>
• 5efa52a chore: Release
• 1857e47 docs: Update changelog
• Additional commits viewable in compare view

Updates bitflags from 2.5.0 to 2.6.0

Release notes

Sourced from bitflags's releases.

2.6.0

What's Changed

• Sync CHANGELOG.md with github release notes by @​dextero in bitflags/bitflags#402
• Update error messages and zerocopy by @​KodrAus in bitflags/bitflags#403
• Bump minimum declared versions of dependencies by @​dextero in bitflags/bitflags#404
• chore(deps): bump serde_derive and bytemuck versions by @​joshka in bitflags/bitflags#405
• add OSFF Scorecard workflow by @​KodrAus in bitflags/bitflags#396
• Update stderr messages by @​KodrAus in bitflags/bitflags#408
• Fix typo by @​waywardmonkeys in bitflags/bitflags#410
• Allow specifying outer attributes in impl mode by @​KodrAus in bitflags/bitflags#411
• Prepare for 2.6.0 release by @​KodrAus in bitflags/bitflags#412

New Contributors

• @​dextero made their first contribution in bitflags/bitflags#402
• @​joshka made their first contribution in bitflags/bitflags#405
• @​waywardmonkeys made their first contribution in bitflags/bitflags#410

Full Changelog: bitflags/bitflags@2.5.0...2.6.0

Changelog

Sourced from bitflags's changelog.

2.6.0

What's Changed

• Sync CHANGELOG.md with github release notes by @​dextero in bitflags/bitflags#402
• Update error messages and zerocopy by @​KodrAus in bitflags/bitflags#403
• Bump minimum declared versions of dependencies by @​dextero in bitflags/bitflags#404
• chore(deps): bump serde_derive and bytemuck versions by @​joshka in bitflags/bitflags#405
• add OSFF Scorecard workflow by @​KodrAus in bitflags/bitflags#396
• Update stderr messages by @​KodrAus in bitflags/bitflags#408
• Fix typo by @​waywardmonkeys in bitflags/bitflags#410
• Allow specifying outer attributes in impl mode by @​KodrAus in bitflags/bitflags#411

New Contributors

• @​dextero made their first contribution in bitflags/bitflags#402
• @​joshka made their first contribution in bitflags/bitflags#405
• @​waywardmonkeys made their first contribution in bitflags/bitflags#410

Full Changelog: bitflags/bitflags@2.5.0...2.6.0

Commits

• 1351369 Merge pull request #412 from KodrAus/cargo/2.6.0
• a187b29 prepare for 2.6.0 release
• e1ac235 Merge pull request #411 from KodrAus/fix/impl-mode-attributes
• dc8f03a allow specifying outer attributes in impl mode
• 9c4b93c Merge pull request #410 from waywardmonkeys/fix-typo
• 980c588 Fix typo
• 9f633fe Merge pull request #408 from KodrAus/chore/ci-fix
• 70a8247 update stderr messages
• 650025d update to scorecard 2.3.1
• 4020868 Merge pull request #396 from bitflags/ci/scorecard
• Additional commits viewable in compare view

Updates log from 0.4.21 to 0.4.22

Changelog

Sourced from log's changelog.

[0.4.22] - 2024-06-27

What's Changed

• Add some clarifications to the library docs by @​KodrAus in rust-lang/log#620
• Add links to colog crate by @​chrivers in rust-lang/log#621
• adding line_number test + updating some testing infrastructure by @​DIvkov575 in rust-lang/log#619
• Clarify the actual set of functions that can race in _racy variants by @​KodrAus in rust-lang/log#623
• Replace deprecated std::sync::atomic::spin_loop_hint() by @​Catamantaloedis in rust-lang/log#625
• Check usage of max_level features by @​Thomasdezeeuw in rust-lang/log#627
• Remove unneeded import by @​Thomasdezeeuw in rust-lang/log#628
• Loosen orderings for logger initialization in rust-lang/log#632. Originally by @​pwoolcoc in rust-lang/log#599
• Use Location::caller() for file and line info in rust-lang/log#633. Originally by @​Cassy343 in rust-lang/log#520

New Contributors

• @​chrivers made their first contribution in rust-lang/log#621
• @​DIvkov575 made their first contribution in rust-lang/log#619
• @​Catamantaloedis made their first contribution in rust-lang/log#625

Full Changelog: rust-lang/log@0.4.21...0.4.22

Commits

• d5ba2cf Merge pull request #634 from rust-lang/cargo/0.4.22
• d1a8306 prepare for 0.4.22 release
• 46894ef Merge pull request #633 from rust-lang/feat/panic-info
• e0d389c Merge pull request #632 from rust-lang/feat/loosen-atomics
• c9e5e13 use Location::caller() for file and line info
• 507b672 loosen orderings for logger initialization
• c879b01 Merge pull request #628 from Thomasdezeeuw/fix-warnings
• 405fdb4 Merge pull request #627 from Thomasdezeeuw/check-features
• 1307ade Remove unneeded import
• 710560e Don't use --all-features in CI
• Additional commits viewable in compare view

Updates wgpu from 0.20.1 to 22.0.0

Release notes

Sourced from wgpu's releases.

v22.0.0 (Our first major version release!)

Our first major version release!

For the first time ever, WGPU is being released with a major version (i.e., 22.* instead of 0.22.*)! Maintainership has decided to fully adhere to Semantic Versioning's recommendations for versioning production software. According to SemVer 2.0.0's Q&A about when to use 1.0.0 versions (and beyond):

How do I know when to release 1.0.0?

If your software is being used in production, it should probably already be 1.0.0. If you have a stable API on which users have come to depend, you should be 1.0.0. If you’re worrying a lot about backward compatibility, you should probably already be 1.0.0.

It is a well-known fact that WGPU has been used for applications and platforms already in production for years, at this point. We are often concerned with tracking breaking changes, and affecting these consumers' ability to ship. By releasing our first major version, we publicly acknowledge that this is the case. We encourage other projects in the Rust ecosystem to follow suit.

Note that while we start to use the major version number, WGPU is not "going stable", as many Rust projects do. We anticipate many breaking changes before we fully comply with the WebGPU spec., which we expect to take a small number of years.

Overview

A major (pun intended) theme of this release is incremental improvement. Among the typically large set of bug fixes, new features, and other adjustments to WGPU by the many contributors listed below, @​wumpf and @​teoxoy have merged a series of many simplifications to WGPU's internals and, in one case, to the render and compute pass recording APIs. Many of these change WGPU to use atomically reference-counted resource tracking (i.e., Arc<…>), rather than using IDs to manage the lifetimes of platform-specific graphics resources in a registry of separate reference counts. This has led us to diagnose and fix many long-standing bugs, and net some neat performance improvements on the order of 40% or more of some workloads.

While the above is exciting, we acknowledge already finding and fixing some (easy-to-fix) regressions from the above work. If you migrate to WGPU 22 and encounter such bugs, please engage us in the issue tracker right away!

Major Changes

Lifetime bounds on wgpu::RenderPass & wgpu::ComputePass

wgpu::RenderPass & wgpu::ComputePass recording methods (e.g. wgpu::RenderPass:set_render_pipeline) no longer impose a lifetime constraint to objects passed to a pass (like pipelines/buffers/bindgroups/query-sets etc.).

This means the following pattern works now as expected:

let mut pipelines: Vec<wgpu::RenderPipeline> = ...;
// ...
let mut cpass = encoder.begin_compute_pass(&wgpu::ComputePassDescriptor::default());
cpass.set_pipeline(&pipelines[123]);
// Change pipeline container - this requires mutable access to `pipelines` while one of the pipelines is in use.
pipelines.push(/* ... */);
// Continue pass recording.
cpass.set_bindgroup(...);

Previously, a set pipeline (or other resource) had to outlive pass recording which often affected wider systems, meaning that users needed to prove to the borrow checker that Vec<wgpu::RenderPipeline> (or similar constructs) aren't accessed mutably for the duration of pass recording.

Furthermore, you can now opt out of wgpu::RenderPass/wgpu::ComputePass's lifetime dependency on its parent wgpu::CommandEncoder using wgpu::RenderPass::forget_lifetime/wgpu::ComputePass::forget_lifetime:

fn independent_cpass<'enc>(encoder: &'enc mut wgpu::CommandEncoder) -> wgpu::ComputePass<'static> {
    let cpass: wgpu::ComputePass<'enc> = encoder.begin_compute_pass(&wgpu::ComputePassDescriptor::default());
    cpass.forget_lifetime()
}

⚠️ As long as a wgpu::RenderPass/wgpu::ComputePass is pending for a given wgpu::CommandEncoder, creation of a compute or render pass is an error and invalidates the wgpu::CommandEncoder.

... (truncated)

Changelog

Sourced from wgpu's changelog.

22.0.0 (2024-07-17)

Overview

Our first major version release!

For the first time ever, WGPU is being released with a major version (i.e., 22.* instead of 0.22.*)! Maintainership has decided to fully adhere to Semantic Versioning's recommendations for versioning production software. According to SemVer 2.0.0's Q&A about when to use 1.0.0 versions (and beyond):

How do I know when to release 1.0.0?

If your software is being used in production, it should probably already be 1.0.0. If you have a stable API on which users have come to depend, you should be 1.0.0. If you’re worrying a lot about backward compatibility, you should probably already be 1.0.0.

It is a well-known fact that WGPU has been used for applications and platforms already in production for years, at this point. We are often concerned with tracking breaking changes, and affecting these consumers' ability to ship. By releasing our first major version, we publicly acknowledge that this is the case. We encourage other projects in the Rust ecosystem to follow suit.

Note that while we start to use the major version number, WGPU is not "going stable", as many Rust projects do. We anticipate many breaking changes before we fully comply with the WebGPU spec., which we expect to take a small number of years.

Overview

A major (pun intended) theme of this release is incremental improvement. Among the typically large set of bug fixes, new features, and other adjustments to WGPU by the many contributors listed below, @​wumpf and @​teoxoy have merged a series of many simplifications to WGPU's internals and, in one case, to the render and compute pass recording APIs. Many of these change WGPU to use atomically reference-counted resource tracking (i.e., Arc<…>), rather than using IDs to manage the lifetimes of platform-specific graphics resources in a registry of separate reference counts. This has led us to diagnose and fix many long-standing bugs, and net some neat performance improvements on the order of 40% or more of some workloads.

While the above is exciting, we acknowledge already finding and fixing some (easy-to-fix) regressions from the above work. If you migrate to WGPU 22 and encounter such bugs, please engage us in the issue tracker right away!

Major Changes

Lifetime bounds on wgpu::RenderPass & wgpu::ComputePass

wgpu::RenderPass & wgpu::ComputePass recording methods (e.g. wgpu::RenderPass:set_render_pipeline) no longer impose a lifetime constraint to objects passed to a pass (like pipelines/buffers/bindgroups/query-sets etc.).

This means the following pattern works now as expected:

let mut pipelines: Vec<wgpu::RenderPipeline> = ...;
// ...
let mut cpass = encoder.begin_compute_pass(&wgpu::ComputePassDescriptor::default());
cpass.set_pipeline(&pipelines[123]);
// Change pipeline container - this requires mutable access to `pipelines` while one of the pipelines is in use.
pipelines.push(/* ... */);
// Continue pass recording.
cpass.set_bindgroup(...);

Previously, a set pipeline (or other resource) had to outlive pass recording which often affected wider systems, meaning that users needed to prove to the borrow checker that Vec<wgpu::RenderPipeline> (or similar constructs) aren't accessed mutably for the duration of pass recording.

Furthermore, you can now opt out of wgpu::RenderPass/wgpu::ComputePass's lifetime dependency on its parent wgpu::CommandEncoder using wgpu::RenderPass::forget_lifetime/wgpu::ComputePass::forget_lifetime:

fn independent_cpass<'enc>(encoder: &'enc mut wgpu::CommandEncoder) -> wgpu::ComputePass<'static> {
    let cpass: wgpu::ComputePass<'enc> = encoder.begin_compute_pass(&wgpu::ComputePassDescriptor::default());
    cpass.forget_lifetime()
</tr></table> 

... (truncated)

Commits

• 278d278 chore: remove non-existent wgpu-example workspace dep.
• e883fa7 docs(CHANGELOG): add Unreleased section
• 6a1432c chore: release 22.0.0
• 9a0adef use ManuallyDrop instead of Option for PendingWrites
• 77e45d4 add missing device valid check in create_texture_view
• f767220 remove same device check from create_texture_binding
• ed67ff2 [deno] remove assertDeviceMatch
• 63303d4 add missing same device checks
• 2f7860b move same device check in compute_pass_end_impl
• 7761b57 move same device checks in render_pass_end
• Additional commits viewable in compare view

Updates bytemuck from 1.16.0 to 1.16.1

Changelog

Sourced from bytemuck's changelog.

1.16.1

• NOT SEMVER SUPPORTED: Adds the nightly_float Cargo feature. This activates the f16 and f128 nightly features, and then provides Zeroable and Pod impls for those types.

Commits

• 02ffd53 chore: Release bytemuck version 1.16.1
• e0364d2 update changelog
• 9b81537 Support Zeroable and Pod for f16 and f128 (#251)
• d15b8e0 stupid branch stuff. (#248)
• c954006 Fix the errors CI is showing (#247)
• a630404 support deriving Zeroable for fieldless enums (#233)
• 9a27279 Allow generics in derive(ByteEq, ByteHash). (#219)
• 1c37514 fix clippy lints (#137)
• f9f7bb1 Address unexpected_cfgs warnings instead of allowing the lint (#243)
• 89885d1 chore: Release bytemuck_derive version 1.6.1
• Additional commits viewable in compare view

Updates serde from 1.0.203 to 1.0.204

Release notes

Sourced from serde's releases.

v1.0.204

• Apply #[diagnostic::on_unimplemented] attribute on Rust 1.78+ to suggest adding serde derive or enabling a "serde" feature flag in dependencies (#2767, thanks @​weiznich)

Commits

• 18dcae0 Release 1.0.204
• 58c307f Alphabetize list of rustc-check-cfg
• 8cc4809 Merge pull request #2769 from dtolnay/onunimpl
• 1179158 Update ui test with diagnostic::on_unimplemented from PR 2767
• 91aa40e Add ui test of unsatisfied serde trait bound
• 595019e Cut test_suite from workspace members in old toolchain CI jobs
• b0d7917 Pull in trybuild 'following types implement trait' fix
• 8e6637a Merge pull request #2767 from weiznich/feature/diagnostic_on_unimplemented
• 694fe05 Use the #[diagnostic::on_unimplemented] attribute when possible
• f3dfd2a Suppress dead code warning in test of unit struct remote derive
• Additional commits viewable in compare view

Updates toml from 0.8.14 to 0.8.16

Commits

• 4ac61f7 chore: Release
• a5eb1ac chore: Disable serde_toml releasing for now
• 9217e44 chore: Release
• 003ce94 docs: Update changelog
• b463f3d Merge pull request #757 from epage/key
• 3d8852b fix(encode): Be extra sure it can be a literal
• e1bc1c3 refactor(encode): Pull out literal inference
• fbb0ac2 test(encode): Add property-based tests for keys/strings
• 0b268f2 fix(encode): Correct encoding for key with mixed quotes
• 82c0195 refactor(encode): Make str repr inferring clearer
• Additional commits viewable in compare view

Updates librashader from fff80df to f6cf642

Commits

• f6cf642 chore: Release
• 98958df dep: update rustc_hash
• b5d523e rt(mtl): move icrate definitions to objc2-metal
• 5e9ce12 Revert "ci: temporarily remove deny-deprecated on ctypes to unblock ares"
• 1b0574c presets: show file name and details on io error
• b84e104 capi: fix malformed vulkan include
• See full diff in compare view

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 commands and options

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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[dependabot]

Looks like these dependencies are no longer updatable, so this is no longer needed.