[dependabot]

Updates the requirements on JET to permit the latest version.

Release notes

Sourced from JET's releases.

v0.13.1

JET v0.13.1

Diff since v0.13.0

Changelog

Sourced from JET's changelog.

[0.13.1]

Changed

• Improved the performance of the error analysis of JETAnalyzer, e.g. report_call and report_package, on Julia 1.14.

Fixed

• Fixed false positive reports on Julia 1.14 and later with code coverage enabled, e.g. under Pkg.test(; coverage=true), where JET could reuse the analysis results cached during its precompilation and fail to constant-fold calls:

  const SV = Core.svec(1, 2, 3)
  f() = sin(length(SV) == 3 ? 1.0 : "1")
  @test_call f() # failed, reporting no method for `sin(::String)`

[0.13.0]

Added

• Added support for Julia v1.14. JET now loads full functionality on Julia 1.14 instead of empty stubs.

• Added the allow_unsupported_julia preference, which loads full JET functionality on unsupported Julia versions, e.g. nightly builds, without the development features that JET_DEV_MODE also enables:

  LocalPreferences.toml

  [JET]
  allow_unsupported_julia = true # previously `JET_DEV_MODE = true` was needed

  JET emits a warning when it is loaded on an unsupported Julia version this way, since it may not work correctly there.

• JETInterface now exports has_problems, the predicate that call_test_ex and func_test use to decide whether an analysis result fails a test.

• Calls whose matching methods are ambiguous are now reported as AmbiguousMethodErrorReport instead of MethodErrorReport saying that no matching method is found. For a union-split call, the ambiguous signatures are reported separately from those without any matching method:

  k(::Int, ::Any) = 1
  k(::Any, ::Int) = 2
  m(x::Int) = k(x, x)               # reported: ambiguous `k(::Int, ::Int)`
  n(x::Union{Int,String}) = k(x, x) # reported: ambiguous `k(::Int, ::Int)`
                                    # and no method for `k(::String, ::String)`

... (truncated)

Commits

• 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 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)