Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update dependency jax to >=0.4.35, <=0.4.35 #851

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 11, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
jax >=0.4.16, <=0.4.34 -> >=0.4.35, <=0.4.35 age adoption passing confidence

Release Notes

jax-ml/jax (jax)

v0.4.35

Compare Source

  • Breaking Changes

    • {func}jax.numpy.isscalar now returns True for any array-like object with
      zero dimensions. Previously it only returned True for zero-dimensional
      array-like objects with a weak dtype.
    • jax.experimental.host_callback has been deprecated since March 2024, with
      JAX version 0.4.26. Now we removed it.
      See {jax-issue}#20385 for a discussion of alternatives.
  • Changes:

    • jax.lax.FftType was introduced as a public name for the enum of FFT
      operations. The semi-public API jax.lib.xla_client.FftType has been
      deprecated.
    • TPU: JAX now installs TPU support from the libtpu package rather than
      libtpu-nightly. For the next few releases JAX will pin an empty version of
      libtpu-nightly as well as libtpu to ease the transition; that dependency
      will be removed in Q1 2025.
  • Deprecations:

    • The semi-public API jax.lib.xla_client.PaddingType has been deprecated.
      No JAX APIs consume this type, so there is no replacement.
    • The default behavior of {func}jax.pure_callback and
      {func}jax.extend.ffi.ffi_call under vmap has been deprecated and so has
      the vectorized parameter to those functions. The vmap_method parameter
      should be used instead for better defined behavior. See the discussion in
      {jax-issue}#23881 for more details.
    • The semi-public API jax.lib.xla_client.register_custom_call_target has
      been deprecated. Use the JAX FFI instead.
    • The semi-public APIs jax.lib.xla_client.dtype_to_etype,
      jax.lib.xla_client.ops,
      jax.lib.xla_client.shape_from_pyval, jax.lib.xla_client.PrimitiveType,
      jax.lib.xla_client.Shape, jax.lib.xla_client.XlaBuilder, and
      jax.lib.xla_client.XlaComputation have been deprecated. Use StableHLO
      instead.

Configuration

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

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

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

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


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

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested a review from a team September 11, 2024 22:19
@renovate renovate bot changed the title chore(deps): update dependency jax to >=0.4.32, <=0.4.32 chore(deps): update dependency jax to >=0.4.31, <=0.4.31 Sep 12, 2024
@renovate renovate bot changed the title chore(deps): update dependency jax to >=0.4.31, <=0.4.31 chore(deps): update dependency jax to >=0.4.33, <=0.4.33 Sep 16, 2024
@renovate renovate bot changed the title chore(deps): update dependency jax to >=0.4.33, <=0.4.33 chore(deps): update dependency jax to >=0.4.34, <=0.4.34 Oct 4, 2024
@renovate renovate bot changed the title chore(deps): update dependency jax to >=0.4.34, <=0.4.34 chore(deps): update dependency jax to >=0.4.35, <=0.4.35 Oct 22, 2024
Copy link

Stale pull request message. Please comment to remove stale tag. Otherwise this pr will be closed soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants