Update naga requirement from 22.1.0 to 23.1.0

[dependabot]

Updates the requirements on naga to permit the latest version.

Release notes

Sourced from naga's releases.

v23.1.0 (2024-12-16)

This release only contains naga v23.1.0 all other packages are still at their previous versions.

New Features

Naga

• Expose Ray Query flags as constants in WGSL. Implement candidate intersections. By @​kvark in #5429

Changelog

Sourced from naga's changelog.

23.1.0 (2024-12-11)

New Features

Naga

• Expose Ray Query flags as constants in WGSL. Implement candidate intersections. By @​kvark in #5429

23.0.1 (2024-11-25)

This release includes patches for wgpu, wgpu-core and wgpu-hal. All other crates remain at 23.0.0. Below changes were cherry-picked from 24.0.0 development line.

Bug fixes

General

• Fix Texture view leaks regression. By @​xiaopengli89 in #6576

Metal

• Fix surface creation crashing on iOS. By @​mockersf in #6535

Vulkan

• Fix surface capabilities being advertised when its query failed. By @​wumpf in #6510

23.0.0 (2024-10-25)

Themes of this release

This release's theme is one that is likely to repeat for a few releases: convergence with the WebGPU specification! WGPU's design and base functionality are actually determined by two specifications: one for WebGPU, and one for the WebGPU Shading Language.

This may not sound exciting, but let us convince you otherwise! All major web browsers have committed to offering WebGPU in their environment. Even JS runtimes like Node and Deno have communities that are very interested in providing WebGPU! WebGPU is slowly eating the world, as it were. 😀 It's really important, then, that WebGPU implementations behave in ways that one would expect across all platforms. For example, if Firefox's WebGPU implementation were to break when running scripts and shaders that worked just fine in Chrome, that would mean sad users for both application authors and browser authors.

WGPU also benefits from standard, portable behavior in the same way as web browsers. Because of this behavior, it's generally fairly easy to port over usage of WebGPU in JavaScript to WGPU. It is also what lets WGPU go full circle: WGPU can be an implementation of WebGPU on native targets, but also it can use other implementations of WebGPU as a backend in JavaScript when compiled to WASM. Therefore, the same dynamic applies: if WGPU's own behavior were significantly different, then WGPU and end users would be sad, sad humans as soon as they discover places where their nice apps are breaking, right?

The answer is: yes, we do have sad, sad humans that really want their WGPU code to work everywhere. As Firefox and others use WGPU to implement WebGPU, the above example of Firefox diverging from standard is, unfortunately, today's reality. It mostly behaves the same as a standards-compliant WebGPU, but it still doesn't in many important ways. Of particular note is Naga, its implementation of the WebGPU Shader Language. Shaders are pretty much a black-and-white point of failure in GPU programming; if they don't compile, then you can't use the rest of the API! And yet, it's extremely easy to run into this:

fn gimme_a_float() -> f32 {
  return 42; // fails in Naga, but standard WGSL happily converts to `f32`
}

We intend to continue making visible strides in converging with specifications for WebGPU and WGSL, as this release has. This is, unfortunately, one of the major reasons that WGPU has no plans to work hard at keeping a SemVer-stable interface for the foreseeable future; we have an entire platform of GPU programming functionality we have to catch up with, and SemVer stability is unfortunately in tension with that. So, for now, you're going to keep seeing major releases and breaking changes. Where possible, we'll try to make that painless, but compromises to do so don't always make sense with our limited resources.

... (truncated)

Commits

• 9993f5c [v23] Rt constants backport (#6711)
• cbe98e6 Updates to v23.0.1 changelog notes - fix date & links
• 1755db7 bump wgpu, wgpu-core, wgpu-hal to 23.0.1
• 1f49837 Fix Vulkan surface capabilities being advertised when its query failed. (#6510)
• 5ea7288 Fix leaks of WeakVec (#6576)
• f286882 Fix iOS crash: don't set autoresizing mask (#6535)
• 08c9d8c chore: bump WGPU workspace crates to 23
• 1ab5f65 docs(CHANGELOG): add missing entry for #6107
• 9bf9bb8 style(CHANGELOG): join soft-wrapped lines in Unreleased
• 0ad2753 docs(CHANGELOG): add Major changes item for Optional entry points
• Additional commits viewable in compare view

You can trigger a rebase of this PR 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 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)