Update dependency jax to v0.5.0

[red-hat-konflux]

This PR contains the following updates:

Package	Update	Change
jax	minor	==0.4.36.dev20241122 -> ==0.5.0

---

Release Notes

jax-ml/jax (jax)

v0.5.0

Compare Source

As of this release, JAX now uses
effort-based versioning.
Since this release makes a breaking change to PRNG key semantics that
may require users to update their code, we are bumping the "meso" version of JAX
to signify this.

• Breaking changes

  • Enable jax_threefry_partitionable by default (see
    the update note).

  • This release drops support for Mac x86 wheels. Mac ARM of course remains
    supported. For a recent discussihttps://github.com/jax-ml/jax/discussions/22936iscussions/22936.

    Two key factors motivated this decision:

    • The Mac x86 build (only) has a number of test failures and crashes. We
      would prefer to ship no release than a broken release.
    • Mac x86 hardware is end-of-life and cannot be easily obtained for
      developers at this point. So it is difficult for us to fix this kind of
      problem even if we wanted to.

    We are open to readding support for Mac x86 if the community is willing
    to help support that platform: in particular, we would need the JAX test
    suite to pass cleanly on Mac x86 before we could ship releases again.

• Changes:

  • The minimum NumPy version is now 1.25. NumPy 1.25 will remain the minimum
    supported version until June 2025.
  • The minimum SciPy version is now 1.11. SciPy 1.11 will remain the minimum
    supported version until June 2025.
  • {func}jax.numpy.einsum now defaults to optimize='auto' rather than
    optimize='optimal'. This avoids exponentially-scaling trace-time in
    the case of many arguments ({jax-issue}#25214).
  • {func}jax.numpy.linalg.solve no longer supports batched 1D arguments
    on the right hand side. To recover the previous behavior in these cases,
    use solve(a, b[..., None]).squeeze(-1).

• New Features

  • {func}jax.numpy.fft.fftn, {func}jax.numpy.fft.rfftn,
    {func}jax.numpy.fft.ifftn, and {func}jax.numpy.fft.irfftn now support
    transforms in more than 3 dimensions, which was previously the limit. See
    {jax-issue}#25606 for more details.
  • Support added for user defined state in the FFI via the new
    {func}jax.ffi.register_ffi_type_id function.
  • The AOT lowering .as_text() method now supports the debug_info option
    to include debugging information, e.g., source location, in the output.

• Deprecations

  • From {mod}jax.interpreters.xla, abstractify and pytype_aval_mappings
    are now deprecated, having been replaced by symbols of the same name
    in {mod}jax.core.
  • {func}jax.scipy.special.lpmn and {func}jax.scipy.special.lpmn_values
    are deprecated, following their deprecation in SciPy v1.15.0. There are
    no plans to replace these deprecated functions with new APIs.
  • The {mod}jax.extend.ffi submodule was moved to {mod}jax.ffi, and the
    previous import path is deprecated.

• Deletions

  • jax_enable_memories flag has been deleted and the behavior of that flag
    is on by default.
  • From jax.lib.xla_client, the previously-deprecated Device and
    XlaRuntimeError symbols have been removed; instead use jax.Device
    and jax.errors.JaxRuntimeError respectively.
  • The jax.experimental.array_api module has been removed after being
    deprecated in JAX v0.4.32. Since that release, {mod}jax.numpy supports
    the array API directly.

v0.4.38

Compare Source

• Breaking Changes

  • XlaExecutable.cost_analysis now returns a dict[str, float] (instead of a
    single-element list[dict[str, float]]).

• Changes:

  • jax.tree.flatten_with_path and jax.tree.map_with_path are added
    as shortcuts of the corresponding tree_util functions.

• Deprecations

  • a number of APIs in the internal jax.core namespace have been deprecated.
    Most were no-ops, were little-used, or can be replaced by APIs of the same
    name in {mod}jax.extend.core; see the documentation for {mod}jax.extend
    for information on the compatibility guarantees of these semi-public extensions.
  • Several previously-deprecated APIs have been removed, including:
    • from {mod}jax.core: check_eqn, check_type, check_valid_jaxtype, and
      non_negative_dim.
    • from {mod}jax.lib.xla_bridge: xla_client and default_backend.
    • from {mod}jax.lib.xla_client: _xla and bfloat16.
    • from {mod}jax.numpy: round_.

• New Features

  • {func}jax.export.export can be used for device-polymorphic export with
    shardings constructed with {func}jax.sharding.AbstractMesh.
    See the jax.export documentation.
  • Added {func}jax.lax.split. This is a primitive version of
    {func}jax.numpy.split, added because it yields a more compact
    transpose during automatic differentiation.

v0.4.37

Compare Source

This is a patch release of jax 0.4.36. Only "jax" was released at this version.

---

Configuration

📅 Schedule: Branch creation - "after 5am on saturday" (UTC), Automerge - At any time (no schedule defined).

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

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

To execute skipped test pipelines write comment /ok-to-test.

This PR has been generated by MintMaker (powered by Renovate Bot).

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: red-hat-konflux[bot]
Once this PR has been reviewed and has the lgtm label, please assign rh-steve-grubb for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

Hi @red-hat-konflux[bot]. Thanks for your PR.

I'm waiting for a opendatahub-io member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.