[dependabot]

Updates the requirements on JLArrays, JET and DocStringExtensions to permit the latest version.
Updates JLArrays to 0.4.2

Commits

• See full diff in compare view

Updates JET to 0.13.0

Release notes

Sourced from JET's releases.

v0.13.0

JET v0.13.0

Diff since v0.12.3

CHANGELOG

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

• invoke calls that throw MethodError because no method matches the specified signature are now reported as MethodErrorReport in the :basic and :sound modes, and those whose matching methods are ambiguous are reported as AmbiguousMethodErrorReport:

  f(::Int) = 1
  g(x) = invoke(f, Tuple{String}, x) # reported: no method for `f(::String)`
  h(x) = @invoke f(x::Integer)       # reported: no method for `f(::Integer)`
  k(::Int, ::Any) = 1
  k(::Any, ::Int) = 2
  l(x) = @invoke k(x::Int, x::Int)   # reported: ambiguous `k(::Int, ::Int)`

... (truncated)

Changelog

Sourced from JET's changelog.

[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)`

• invoke calls that throw MethodError because no method matches the specified signature are now reported as MethodErrorReport in the :basic and :sound modes, and those whose matching methods are ambiguous are reported as AmbiguousMethodErrorReport:

  f(::Int) = 1
  g(x) = invoke(f, Tuple{String}, x) # reported: no method for `f(::String)`
  h(x) = @invoke f(x::Integer)       # reported: no method for `f(::Integer)`
  k(::Int, ::Any) = 1
  k(::Any, ::Int) = 2
  l(x) = @invoke k(x::Int, x::Int)   # reported: ambiguous `k(::Int, ::Int)`

• Top-level analysis now reports a @test that always fails, i.e. whose expression is inferred to evaluate to false or to a non-boolean value, and a @test_throws that always fails, i.e. whose expression is inferred to throw only exceptions that do not match the expected one. The errors in the

... (truncated)

Commits

• See full diff in compare view

Updates JLArrays to 0.4.2

Commits

• See full diff in compare view

Updates JET to 0.13.0

Release notes

Sourced from JET's releases.

v0.13.0

JET v0.13.0

Diff since v0.12.3

CHANGELOG

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

• invoke calls that throw MethodError because no method matches the specified signature are now reported as MethodErrorReport in the :basic and :sound modes, and those whose matching methods are ambiguous are reported as AmbiguousMethodErrorReport:

  f(::Int) = 1
  g(x) = invoke(f, Tuple{String}, x) # reported: no method for `f(::String)`
  h(x) = @invoke f(x::Integer)       # reported: no method for `f(::Integer)`
  k(::Int, ::Any) = 1
  k(::Any, ::Int) = 2
  l(x) = @invoke k(x::Int, x::Int)   # reported: ambiguous `k(::Int, ::Int)`

... (truncated)

Changelog

Sourced from JET's changelog.

[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)`

• invoke calls that throw MethodError because no method matches the specified signature are now reported as MethodErrorReport in the :basic and :sound modes, and those whose matching methods are ambiguous are reported as AmbiguousMethodErrorReport:

  f(::Int) = 1
  g(x) = invoke(f, Tuple{String}, x) # reported: no method for `f(::String)`
  h(x) = @invoke f(x::Integer)       # reported: no method for `f(::Integer)`
  k(::Int, ::Any) = 1
  k(::Any, ::Int) = 2
  l(x) = @invoke k(x::Int, x::Int)   # reported: ambiguous `k(::Int, ::Int)`

• Top-level analysis now reports a @test that always fails, i.e. whose expression is inferred to evaluate to false or to a non-boolean value, and a @test_throws that always fails, i.e. whose expression is inferred to throw only exceptions that do not match the expected one. The errors in the

... (truncated)

Commits

• See full diff in compare view

Updates DocStringExtensions to 0.10.2

Release notes

Sourced from DocStringExtensions's releases.

v0.10.2

DocStringExtensions v0.10.2

Diff since v0.10.1

See https://github.com/JuliaDocs/DocStringExtensions.jl/blob/master/CHANGELOG.md for a list of changes.

Merged pull requests:

• perf: drop the precompile workload and run the package interpreted (#314) (@​MichaelHatherly)
• Update version to 0.10.2 (#315) (@​MichaelHatherly)

Closed issues:

• Precompile workload slows loading of every dependent package (#313)

Changelog

Sourced from DocStringExtensions's changelog.

v0.10.2 - 2026-10-21

Changed

• Remove the precompilation workload and the PrecompileTools dependency, which made every package depending on DocStringExtensions slower to precompile and load. On Julia 1.6 and later the package runs interpreted, with inference on. Rendering the first docstring of a session takes about 0.2 s, against 1 s in v0.10.0 (#313, #314)

v0.10.1 - 2026-10-20

Changed

• Improved the TTFX of the package by reducing specializations and adding a precompilation workload (#309).

v0.10.0 - 2026-10-14

Breaking

• @template rejects a category no docstring belongs to, such as a misspelled name, with an ArgumentError. It used to store a template that never applied, so a package with such a category now fails to precompile until the category is corrected or removed (#223)
• @template throws an ArgumentError for a template string without $(DOCSTRING), including a plain string literal, when the template is defined. Some of these templates used to load and fail with a MethodError only when Julia displayed a docstring. A package that defines one now fails to precompile (#151)
• More docstrings get a template, and some get a different one. A docstring now gets its template when it sits in the same begin block as the @template (#288), documents a bare existing name such as "..." f (#291), or documents a parametric type's constructor (#226). A method defined through a const alias gets METHODS where it got CONSTANTS (#289). A function named like a macro, such as var"@f", no longer gets MACROS (#263). Bindings documented together each get their own category's template (#210). Where a docstring repeats by hand what its template prints, the text now appears twice

Added

• Add TYPEDMETHODLIST, which lists methods like METHODLIST but with argument and return types. TypedMethodList(returns = false) leaves out the return types (#150, #197)
• Add TypedMethodSignatures(returns = false), which renders typed signatures without return types (#159, #179)
• Add a returns option to MethodSignatures and MethodList that follows each signature with its inferred return type. MethodSignatures and TypedMethodSignatures also take a string, such as returns = "success::Bool", which they print after -> in place of the inferred type (#206, #246)
• Add the DOCSTRINGEXTENSIONS_RETURN_ARROW and DOCSTRINGEXTENSIONS_SIGNATURE_WIDTH environment variables. A reader sets them to change the arrow before return types, such as to →, and the width at which a signature wraps to one argument per line, 60 by default (#252, #267)
• Add a defaults = true option to MethodSignatures and TypedMethodSignatures that prints default argument values, with the methods generated for positional defaults collapsed into one signature (#19, #107, #194)
• Add a defaults = :brackets option to MethodSignatures and TypedMethodSignatures. It prints the collapsed signature without default values. Each optional positional argument appears in brackets. Any other symbol passed as defaults throws an ArgumentError (#206, #247)
• Add PUBLIC to list a module's public names, both exported and declared public (#190)
• Add INSTANCES to list the instances of an enum with their values. It supports @enum and EnumX.jl's @enumx (#171)
• Add SUBTYPES to list the direct subtypes of a type as links. It lists only subtypes defined in the type's own module or a module inside it (#47, #154, #227)
• Add BODY to print the body of the documented method definition as a Julia code block (#54, #237)
• Add NOTEMPLATE, which stops a module's @template applying to the docstring it appears in. TemplateOverride(category) applies the template for another category instead (#158, #240)
• Add the ABSTRACTTYPES template category for abstract types. A module without one documents abstract types with its TYPES template, as before (#147, #241)
• SIGNATURES and TYPEDSIGNATURES in the docstring of a macro print it as its caller writes it, such as @m a b. The __source__ and __module__ arguments and the inferred return type are left out. They printed nothing before. METHODLIST and TYPEDMETHODLIST list a macro the same way. For a vararg macro they printed its hidden arguments, and for any other macro nothing (#262)
• SIGNATURES and TYPEDSIGNATURES in the docstring of a struct list the constructors its definition creates. They printed nothing before (#71, #245)
• Declare the interface for writing an abbreviation public on Julia 1.11 and later: Abbreviation, format and interpolation. A new guide covers it (#86, #303)
• Declare the types that take abbreviation options public on Julia 1.11 and later, such as MethodSignatures and TypeFields. Each one appears on its topic's reference page (#303)
• Add TypeFields(; types, defaults), whose keywords match the other option types (#303)

Changed

• Signatures leave out a return type inferred as Any, as they already did for Nothing. -> Any says only that inference could not work out the type (#301, #298)
• The manual splits into Examples and Reference sections with one page per topic. Each example page prints its source above the rendered docstrings, and new pages cover PUBLIC, INSTANCES, and @template with DOCSTRING. The package docstring is rewritten. A Setup page covers adding the package, templates, and Documenter. The docstrings of the package, @template and every abbreviation except README and LICENSE carry examples as doctests, which the docs build checks against the real output. They replace hand-written samples that had drifted from it (#122, #215)
• SIGNATURES prints an unnamed argument with a declared type as ::T, as TYPEDSIGNATURES does, so foo(::Val{N}) no longer prints as foo(_). An untyped unnamed argument still prints as _ (#161, #235)
• TYPEDSIGNATURES and TYPEDMETHODLIST print the declared type of each keyword argument, such as f(x; n::Int64). An untyped keyword and a kwargs... keyword print without one (#97, #244)
• FIELDS and TYPEDFIELDS print each field's default value, such as retries::Int64 = 3, for structs defined with Base.@kwdef or a macro that uses the same syntax. TypeFields(defaults = false) hides them (#182, #245)
• @template applies a template when its docstring is defined, not when it is displayed, so a templated docstring no longer stores the documented expression in the package image. A docstring for a binding that does not exist yet keeps its template until display. Bindings documented together, such as @doc "..." (f, T), each get the template for their own category, where they all used the last binding's (#210)

... (truncated)

Commits

• See full diff in compare view

Updates JLArrays to 0.4.2

Commits

• See full diff in compare view

Updates JET to 0.13.0

Release notes

Sourced from JET's releases.

v0.13.0

JET v0.13.0

Diff since v0.12.3

CHANGELOG

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

• invoke calls that throw MethodError because no method matches the specified signature are now reported as MethodErrorReport in the :basic and :sound modes, and those whose matching methods are ambiguous are reported as AmbiguousMethodErrorReport:

  f(::Int) = 1
  g(x) = invoke(f, Tuple{String}, x) # reported: no method for `f(::String)`
  h(x) = @invoke f(x::Integer)       # reported: no method for `f(::Integer)`
  k(::Int, ::Any) = 1
  k(::Any, ::Int) = 2
  l(x) = @invoke k(x::Int, x::Int)   # reported: ambiguous `k(::Int, ::Int)`

... (truncated)

Changelog

Sourced from JET's changelog.

[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)`

• invoke calls that throw MethodError because no method matches the specified signature are now reported as MethodErrorReport in the :basic and :sound modes, and those whose matching methods are ambiguous are reported as AmbiguousMethodErrorReport:

  f(::Int) = 1
  g(x) = invoke(f, Tuple{String}, x) # reported: no method for `f(::String)`
  h(x) = @invoke f(x::Integer)       # reported: no method for `f(::Integer)`
  k(::Int, ::Any) = 1
  k(::Any, ::Int) = 2
  l(x) = @invoke k(x::Int, x::Int)   # reported: ambiguous `k(::Int, ::Int)`

• Top-level analysis now reports a @test that always fails, i.e. whose expression is inferred to evaluate to false or to a non-boolean value, and a @test_throws that always fails, i.e. whose expression is inferred to throw only exceptions that do not match the expected one. The errors in the

... (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 <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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 88.00%. Comparing base (e64b3a4) to head (2f8af1e).

❗ There is a different number of reports uploaded between BASE (e64b3a4) and HEAD (2f8af1e). Click for more details.

HEAD has 27 uploads less than BASE

Flag	BASE (e64b3a4)	HEAD (2f8af1e)
DI	57	42
DIT	12	0

Additional details and impacted files

@@             Coverage Diff             @@
##             main    #1084       +/-   ##
===========================================
- Coverage   98.21%   88.00%   -10.22%     
===========================================
  Files         143      111       -32     
  Lines        8246     5969     -2277     
===========================================
- Hits         8099     5253     -2846     
- Misses        147      716      +569     

Flag	Coverage Δ
DI	88.00% <ø> (-10.05%)	⬇️
DIT	?

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.