Bump PETSc in /

[dependabot]

Updates the requirements on and PETSc to permit the latest version.
Updates PETSc to 0.5.0

Release notes

Sourced from PETSc's releases.

v0.5.0

PETSc v0.5.0

Diff since v0.4.14

PETSc.jl 0.5 wraps PETSc 3.25.4 and requires Julia 1.12. It is a breaking release: the high-level API is renamed following the naming conventions in the manual (deprecated names forward with a warning until 0.6), only types and constructors are exported, and the low-level LibPETSc wrappers return their outputs.

Upgrading from 0.4: https://juliaparallel.github.io/PETSc.jl/stable/man/upgrading/ Full release notes: https://juliaparallel.github.io/PETSc.jl/stable/man/release_notes/

Merged pull requests:

• Add age tracking to PetscOptions (#270) (@​filoferra)
• Fix block setindex! on Mat: wrong array rank, and row-major values (#271) (@​filoferra)
• Cleanup v05 (#272) (@​filoferra)
• Reset the RegisterAllCalled flags with a one-byte store (#273) (@​filoferra)
• Docs for the v0.5 release: drop the plan files and the proposal banner (#274) (@​filoferra)
• CHANGELOG: #270, #271, and the 0.4.14 names that 0.5 drops (#275) (@​filoferra)
• Docs: add upgrade guide from 0.4, and the CHANGELOG as release notes (#276) (@​filoferra)
• Check that the library is initialized in the DMDA, DMStag and more (#277) (@​filoferra)

Changelog

Sourced from PETSc's changelog.

v0.5.0

PETSc.jl 0.5 wraps PETSc 3.25.4 (PETSc_jll 3.25) and requires Julia 1.12. The low-level LibPETSc bindings are regenerated by a new rules-based generator (wrapping/, see wrapping/WRAPPING.md) that can be rerun for every PETSc release; the hand edits that used to live in src/autowrapped/ are expressed as rules and overrides. This changes the calling convention of many LibPETSc functions.

Breaking changes (low-level LibPETSc)

• Outputs are returned, not written into caller-supplied handles or Refs. PCCreate(petsclib, comm) returns the PC; KSPGetPC(petsclib, ksp) returns the PC; DMPlexDistribute(petsclib, dm, overlap) returns (sf, dmParallel); ISSorted(petsclib, is) returns a PetscBool; PetscSFGetGraph(petsclib, sf) returns (nroots, nleaves, ilocal, iremote). About 480 functions changed this way (wrapping/DEVIATIONS.md lists every category).
• XDestroy takes the handle or a Ref to it: PetscViewerDestroy(petsclib, viewer).
• String enums are Julia Strings. PCSetType(petsclib, pc, "ilu") works directly; Base.unsafe_convert(Ptr{Int8}, "ilu") is no longer accepted, and the hand-written String overloads (src/string_wrappers*.jl) are gone. The registered names are constants: LibPETSc.PCMG == "mg", LibPETSc.KSPGMRES, LibPETSc.MATSEQAIJ, ... XGetType returns a String ("" when unset).
• PetscKSP -> KSP, PetscSNES -> SNES, AbstractPetscKSP -> AbstractKSP, AbstractPetscSNES -> AbstractSNES; AbstractPETScMemBackend -> AbstractPetscMemBackend (PR #260 naming conventions). The old names remain as deprecated aliases until v0.6.
• Input arguments accept abstract types (AbstractPetscVec, AbstractVector{<:Number}, Integer), returned handles are concrete (PR #263). A call with unsupported argument types throws instead of silently returning nothing.
• Callbacks and contexts are Ptr{Cvoid}; const T *x inputs are Vector{T}; char[] inputs are String; const char *x[] outputs return a String.
• PETSc-owned output arrays with a documented length come back as Vectors (arrays of handles as Vector{IS} etc.); those without one return the raw pointer.
• PetscSplitOwnership*, PetscSortRemoveDups* and the nmax of PetscOptionsGet*Array take and return their in/out scalar.
• 95 header-inline functions and macros without a symbol in libpetsc (PetscStrcmp, PetscTime, VecSetValue, MatSetValue, PetscOptionsBegin, ...) are no longer wrapped.
• Deprecated enum values are not emitted. KSPSetDMActive takes the KSPDMActive flag (PETSc 3.25).

High-level API renamed (naming conventions)

The high-level interface follows docs/src/man/naming.md from v0.5 on. Roughly a hundred names change, and the full rename table is at the end of that page — what follows is what the changes are and how to move.

The register and the shims. scripts/renames.jl is the register: a plain list of old => new pairs plus the internal and unchanged-public sets. src/deprecations.jl, src/public_names.jl, src/audit_names.jl and test/test_deprecations.jl are generated from it by scripts/generate_renames.jl, so they cannot drift apart, and scripts/api_surface.jl --check (run by the test suite) fails if a binding is in none of its sets. Every renamed name keeps a forwarding shim that warns once per call site — through @warn, not Base.depwarn, so it prints whatever --depwarn is set to — and the shims are removed in v0.6.

Exports. PETSc now exports only types and construction entry points:

export LibPETSc
export DMDA, DMStag, DMPlex
export PetscVec, PetscMat, PetscOptions
export KSP, SNES, TS
export petsclibs

v0.4 exported twelve functions and no types at all. audit_petsc_file, set_petsclib, set_library!, unset_library!, library_info, AbstractPetscMemBackend, AbstractPETScMemBackend, determine_memtype, get_petsc_arrays, restore_petsc_arrays and dmda_star_fd_coloring lose their export (HostBackend was exported but never defined). No shim can help here: the replacements are not exported either, so using PETSc code qualifies the call (PETSc.set_library!) or imports the name. The rest of the API is marked public, so names(PETSc) reports it without exporting it.

Construction goes through the type. PetscVec(petsclib, …) replaces VecSeq and as_petsc_vec; PetscMat(petsclib, …) replaces MatSeqAIJ, MatSeqDense, MatCreateSeqAIJ, MatSeqAIJWithArrays and MatAIJ; PetscOptions replaces Options; PetscLibType(path; …) replaces set_petsclib. KSP, SNES and TS are types rather than factory functions, so ksp isa PETSc.KSP holds.

A typed DM hierarchy. DMDA{L,N}, DMStag{L,N} and DMPlex{L} are concrete types under LibPETSc.AbstractPetscDM, not one type with a runtime string flavour. Code annotated ::PetscDM no longer matches — use AbstractPetscDM. PETSc.narrow(dm) turns a low-level handle into the typed one; it queries PETSc, so its return type is a wide Union and hot code should narrow once behind a function barrier. The nine DM-flavour @asserts are gone: dispatch enforces what they checked.

Borrowed handles. A reader that hands back a PETSc object owned by another object — dm(ksp), solution(snes), local_coordinates(dm), tolerances(ts)'s vectors — returns a borrowed handle: no finalizer, and destroy! on it is a no-op (PETSc.owns tells the two apart). Nothing changed at runtime; destroying such a handle was corrupting the owner's already. destroy is now destroy!, per the mutation convention.

Type names are Symbol. type_name on a Vec, Mat, KSP, SNES, TS or DM returns a Symbol, or nothing when PETSc has no type for the object yet, so type_name(ksp) == "gmres" is now false; compare against :gmres. The new set_type!(obj, :gmres) covers Vec, Mat, KSP, SNES and DM as well as TS, and set_type!(obj, "gmres") warns until v0.6. This break has no shim on the reader side.

Argument order, and petsclib dropped. The written vector leads, the DM follows it, and the library is recovered from the object: project_function!(X, dm, time, funcs, ctxs, mode), project_field!(X, dm, time, U, funcs, mode), global_to_local!(lvec, dm, gvec, mode), local_to_global!(gvec, dm, lvec, mode), l2diff(dm, time, funcs, ctxs, X), add_boundary!(dm, …), add_natural_boundary!(dm, …), set_snes_local_fem!(dm), save_vtk!(vec, filename), star_fd_coloring(da). The v0.4 spellings forward and warn, but a call passed through invoke or a function reference is not caught.

... (truncated)

Commits

• 1889553 Merge remote-tracking branch 'upstream/main' into merge-main-into-v05
• ab3c9e3 CHANGELOG: #270, #271, and the 0.4.14 names that 0.5 drops (#275)
• 8395003 Docs: add upgrade guide from 0.4, and the CHANGELOG as release notes (#276)
• 14d0f4d Check that the library is initialized in the DMDA, DMStag and more (#277)
• af1846d Docs for the v0.5 release: drop the plan files and the proposal banner (#274)
• 9637f0a Reset the RegisterAllCalled flags with a one-byte store (#273)
• b9a8d58 Remove Windows user instructions from README
• 3f4a349 Update README.md
• 00b0153 Update DOI badge in README.md
• 4bc3019 Fix block setindex! on Mat: wrong array rank, and row-major values (#271)
• Additional commits viewable in compare view

Updates PETSc to 0.5.0

Release notes

Sourced from PETSc's releases.

v0.5.0

PETSc v0.5.0

Diff since v0.4.14

PETSc.jl 0.5 wraps PETSc 3.25.4 and requires Julia 1.12. It is a breaking release: the high-level API is renamed following the naming conventions in the manual (deprecated names forward with a warning until 0.6), only types and constructors are exported, and the low-level LibPETSc wrappers return their outputs.

Upgrading from 0.4: https://juliaparallel.github.io/PETSc.jl/stable/man/upgrading/ Full release notes: https://juliaparallel.github.io/PETSc.jl/stable/man/release_notes/

Merged pull requests:

• Add age tracking to PetscOptions (#270) (@​filoferra)
• Fix block setindex! on Mat: wrong array rank, and row-major values (#271) (@​filoferra)
• Cleanup v05 (#272) (@​filoferra)
• Reset the RegisterAllCalled flags with a one-byte store (#273) (@​filoferra)
• Docs for the v0.5 release: drop the plan files and the proposal banner (#274) (@​filoferra)
• CHANGELOG: #270, #271, and the 0.4.14 names that 0.5 drops (#275) (@​filoferra)
• Docs: add upgrade guide from 0.4, and the CHANGELOG as release notes (#276) (@​filoferra)
• Check that the library is initialized in the DMDA, DMStag and more (#277) (@​filoferra)

Changelog

Sourced from PETSc's changelog.

v0.5.0

PETSc.jl 0.5 wraps PETSc 3.25.4 (PETSc_jll 3.25) and requires Julia 1.12. The low-level LibPETSc bindings are regenerated by a new rules-based generator (wrapping/, see wrapping/WRAPPING.md) that can be rerun for every PETSc release; the hand edits that used to live in src/autowrapped/ are expressed as rules and overrides. This changes the calling convention of many LibPETSc functions.

Breaking changes (low-level LibPETSc)

• Outputs are returned, not written into caller-supplied handles or Refs. PCCreate(petsclib, comm) returns the PC; KSPGetPC(petsclib, ksp) returns the PC; DMPlexDistribute(petsclib, dm, overlap) returns (sf, dmParallel); ISSorted(petsclib, is) returns a PetscBool; PetscSFGetGraph(petsclib, sf) returns (nroots, nleaves, ilocal, iremote). About 480 functions changed this way (wrapping/DEVIATIONS.md lists every category).
• XDestroy takes the handle or a Ref to it: PetscViewerDestroy(petsclib, viewer).
• String enums are Julia Strings. PCSetType(petsclib, pc, "ilu") works directly; Base.unsafe_convert(Ptr{Int8}, "ilu") is no longer accepted, and the hand-written String overloads (src/string_wrappers*.jl) are gone. The registered names are constants: LibPETSc.PCMG == "mg", LibPETSc.KSPGMRES, LibPETSc.MATSEQAIJ, ... XGetType returns a String ("" when unset).
• PetscKSP -> KSP, PetscSNES -> SNES, AbstractPetscKSP -> AbstractKSP, AbstractPetscSNES -> AbstractSNES; AbstractPETScMemBackend -> AbstractPetscMemBackend (PR #260 naming conventions). The old names remain as deprecated aliases until v0.6.
• Input arguments accept abstract types (AbstractPetscVec, AbstractVector{<:Number}, Integer), returned handles are concrete (PR #263). A call with unsupported argument types throws instead of silently returning nothing.
• Callbacks and contexts are Ptr{Cvoid}; const T *x inputs are Vector{T}; char[] inputs are String; const char *x[] outputs return a String.
• PETSc-owned output arrays with a documented length come back as Vectors (arrays of handles as Vector{IS} etc.); those without one return the raw pointer.
• PetscSplitOwnership*, PetscSortRemoveDups* and the nmax of PetscOptionsGet*Array take and return their in/out scalar.
• 95 header-inline functions and macros without a symbol in libpetsc (PetscStrcmp, PetscTime, VecSetValue, MatSetValue, PetscOptionsBegin, ...) are no longer wrapped.
• Deprecated enum values are not emitted. KSPSetDMActive takes the KSPDMActive flag (PETSc 3.25).

High-level API renamed (naming conventions)

The high-level interface follows docs/src/man/naming.md from v0.5 on. Roughly a hundred names change, and the full rename table is at the end of that page — what follows is what the changes are and how to move.

The register and the shims. scripts/renames.jl is the register: a plain list of old => new pairs plus the internal and unchanged-public sets. src/deprecations.jl, src/public_names.jl, src/audit_names.jl and test/test_deprecations.jl are generated from it by scripts/generate_renames.jl, so they cannot drift apart, and scripts/api_surface.jl --check (run by the test suite) fails if a binding is in none of its sets. Every renamed name keeps a forwarding shim that warns once per call site — through @warn, not Base.depwarn, so it prints whatever --depwarn is set to — and the shims are removed in v0.6.

Exports. PETSc now exports only types and construction entry points:

export LibPETSc
export DMDA, DMStag, DMPlex
export PetscVec, PetscMat, PetscOptions
export KSP, SNES, TS
export petsclibs

v0.4 exported twelve functions and no types at all. audit_petsc_file, set_petsclib, set_library!, unset_library!, library_info, AbstractPetscMemBackend, AbstractPETScMemBackend, determine_memtype, get_petsc_arrays, restore_petsc_arrays and dmda_star_fd_coloring lose their export (HostBackend was exported but never defined). No shim can help here: the replacements are not exported either, so using PETSc code qualifies the call (PETSc.set_library!) or imports the name. The rest of the API is marked public, so names(PETSc) reports it without exporting it.

Construction goes through the type. PetscVec(petsclib, …) replaces VecSeq and as_petsc_vec; PetscMat(petsclib, …) replaces MatSeqAIJ, MatSeqDense, MatCreateSeqAIJ, MatSeqAIJWithArrays and MatAIJ; PetscOptions replaces Options; PetscLibType(path; …) replaces set_petsclib. KSP, SNES and TS are types rather than factory functions, so ksp isa PETSc.KSP holds.

A typed DM hierarchy. DMDA{L,N}, DMStag{L,N} and DMPlex{L} are concrete types under LibPETSc.AbstractPetscDM, not one type with a runtime string flavour. Code annotated ::PetscDM no longer matches — use AbstractPetscDM. PETSc.narrow(dm) turns a low-level handle into the typed one; it queries PETSc, so its return type is a wide Union and hot code should narrow once behind a function barrier. The nine DM-flavour @asserts are gone: dispatch enforces what they checked.

Borrowed handles. A reader that hands back a PETSc object owned by another object — dm(ksp), solution(snes), local_coordinates(dm), tolerances(ts)'s vectors — returns a borrowed handle: no finalizer, and destroy! on it is a no-op (PETSc.owns tells the two apart). Nothing changed at runtime; destroying such a handle was corrupting the owner's already. destroy is now destroy!, per the mutation convention.

Type names are Symbol. type_name on a Vec, Mat, KSP, SNES, TS or DM returns a Symbol, or nothing when PETSc has no type for the object yet, so type_name(ksp) == "gmres" is now false; compare against :gmres. The new set_type!(obj, :gmres) covers Vec, Mat, KSP, SNES and DM as well as TS, and set_type!(obj, "gmres") warns until v0.6. This break has no shim on the reader side.

Argument order, and petsclib dropped. The written vector leads, the DM follows it, and the library is recovered from the object: project_function!(X, dm, time, funcs, ctxs, mode), project_field!(X, dm, time, U, funcs, mode), global_to_local!(lvec, dm, gvec, mode), local_to_global!(gvec, dm, lvec, mode), l2diff(dm, time, funcs, ctxs, X), add_boundary!(dm, …), add_natural_boundary!(dm, …), set_snes_local_fem!(dm), save_vtk!(vec, filename), star_fd_coloring(da). The v0.4 spellings forward and warn, but a call passed through invoke or a function reference is not caught.

... (truncated)

Commits

• 1889553 Merge remote-tracking branch 'upstream/main' into merge-main-into-v05
• ab3c9e3 CHANGELOG: #270, #271, and the 0.4.14 names that 0.5 drops (#275)
• 8395003 Docs: add upgrade guide from 0.4, and the CHANGELOG as release notes (#276)
• 14d0f4d Check that the library is initialized in the DMDA, DMStag and more (#277)
• af1846d Docs for the v0.5 release: drop the plan files and the proposal banner (#274)
• 9637f0a Reset the RegisterAllCalled flags with a one-byte store (#273)
• b9a8d58 Remove Windows user instructions from README
• 3f4a349 Update README.md
• 00b0153 Update DOI badge in README.md
• 4bc3019 Fix block setindex! on Mat: wrong array rank, and row-major values (#271)
• Additional commits viewable in compare view

Updates PETSc to 0.5.0

Release notes

Sourced from PETSc's releases.

v0.5.0

PETSc v0.5.0

Diff since v0.4.14

PETSc.jl 0.5 wraps PETSc 3.25.4 and requires Julia 1.12. It is a breaking release: the high-level API is renamed following the naming conventions in the manual (deprecated names forward with a warning until 0.6), only types and constructors are exported, and the low-level LibPETSc wrappers return their outputs.

Upgrading from 0.4: https://juliaparallel.github.io/PETSc.jl/stable/man/upgrading/ Full release notes: https://juliaparallel.github.io/PETSc.jl/stable/man/release_notes/

Merged pull requests:

• Add age tracking to PetscOptions (#270) (@​filoferra)
• Fix block setindex! on Mat: wrong array rank, and row-major values (#271) (@​filoferra)
• Cleanup v05 (#272) (@​filoferra)
• Reset the RegisterAllCalled flags with a one-byte store (#273) (@​filoferra)
• Docs for the v0.5 release: drop the plan files and the proposal banner (#274) (@​filoferra)
• CHANGELOG: #270, #271, and the 0.4.14 names that 0.5 drops (#275) (@​filoferra)
• Docs: add upgrade guide from 0.4, and the CHANGELOG as release notes (#276) (@​filoferra)
• Check that the library is initialized in the DMDA, DMStag and more (#277) (@​filoferra)

Changelog

Sourced from PETSc's changelog.

v0.5.0

PETSc.jl 0.5 wraps PETSc 3.25.4 (PETSc_jll 3.25) and requires Julia 1.12. The low-level LibPETSc bindings are regenerated by a new rules-based generator (wrapping/, see wrapping/WRAPPING.md) that can be rerun for every PETSc release; the hand edits that used to live in src/autowrapped/ are expressed as rules and overrides. This changes the calling convention of many LibPETSc functions.

Breaking changes (low-level LibPETSc)

• Outputs are returned, not written into caller-supplied handles or Refs. PCCreate(petsclib, comm) returns the PC; KSPGetPC(petsclib, ksp) returns the PC; DMPlexDistribute(petsclib, dm, overlap) returns (sf, dmParallel); ISSorted(petsclib, is) returns a PetscBool; PetscSFGetGraph(petsclib, sf) returns (nroots, nleaves, ilocal, iremote). About 480 functions changed this way (wrapping/DEVIATIONS.md lists every category).
• XDestroy takes the handle or a Ref to it: PetscViewerDestroy(petsclib, viewer).
• String enums are Julia Strings. PCSetType(petsclib, pc, "ilu") works directly; Base.unsafe_convert(Ptr{Int8}, "ilu") is no longer accepted, and the hand-written String overloads (src/string_wrappers*.jl) are gone. The registered names are constants: LibPETSc.PCMG == "mg", LibPETSc.KSPGMRES, LibPETSc.MATSEQAIJ, ... XGetType returns a String ("" when unset).
• PetscKSP -> KSP, PetscSNES -> SNES, AbstractPetscKSP -> AbstractKSP, AbstractPetscSNES -> AbstractSNES; AbstractPETScMemBackend -> AbstractPetscMemBackend (PR #260 naming conventions). The old names remain as deprecated aliases until v0.6.
• Input arguments accept abstract types (AbstractPetscVec, AbstractVector{<:Number}, Integer), returned handles are concrete (PR #263). A call with unsupported argument types throws instead of silently returning nothing.
• Callbacks and contexts are Ptr{Cvoid}; const T *x inputs are Vector{T}; char[] inputs are String; const char *x[] outputs return a String.
• PETSc-owned output arrays with a documented length come back as Vectors (arrays of handles as Vector{IS} etc.); those without one return the raw pointer.
• PetscSplitOwnership*, PetscSortRemoveDups* and the nmax of PetscOptionsGet*Array take and return their in/out scalar.
• 95 header-inline functions and macros without a symbol in libpetsc (PetscStrcmp, PetscTime, VecSetValue, MatSetValue, PetscOptionsBegin, ...) are no longer wrapped.
• Deprecated enum values are not emitted. KSPSetDMActive takes the KSPDMActive flag (PETSc 3.25).

High-level API renamed (naming conventions)

The high-level interface follows docs/src/man/naming.md from v0.5 on. Roughly a hundred names change, and the full rename table is at the end of that page — what follows is what the changes are and how to move.

The register and the shims. scripts/renames.jl is the register: a plain list of old => new pairs plus the internal and unchanged-public sets. src/deprecations.jl, src/public_names.jl, src/audit_names.jl and test/test_deprecations.jl are generated from it by scripts/generate_renames.jl, so they cannot drift apart, and scripts/api_surface.jl --check (run by the test suite) fails if a binding is in none of its sets. Every renamed name keeps a forwarding shim that warns once per call site — through @warn, not Base.depwarn, so it prints whatever --depwarn is set to — and the shims are removed in v0.6.

Exports. PETSc now exports only types and construction entry points:

export LibPETSc
export DMDA, DMStag, DMPlex
export PetscVec, PetscMat, PetscOptions
export KSP, SNES, TS
export petsclibs

v0.4 exported twelve functions and no types at all. audit_petsc_file, set_petsclib, set_library!, unset_library!, library_info, AbstractPetscMemBackend, AbstractPETScMemBackend, determine_memtype, get_petsc_arrays, restore_petsc_arrays and dmda_star_fd_coloring lose their export (HostBackend was exported but never defined). No shim can help here: the replacements are not exported either, so using PETSc code qualifies the call (PETSc.set_library!) or imports the name. The rest of the API is marked public, so names(PETSc) reports it without exporting it.

Construction goes through the type. PetscVec(petsclib, …) replaces VecSeq and as_petsc_vec; PetscMat(petsclib, …) replaces MatSeqAIJ, MatSeqDense, MatCreateSeqAIJ, MatSeqAIJWithArrays and MatAIJ; PetscOptions replaces Options; PetscLibType(path; …) replaces set_petsclib. KSP, SNES and TS are types rather than factory functions, so ksp isa PETSc.KSP holds.

A typed DM hierarchy. DMDA{L,N}, DMStag{L,N} and DMPlex{L} are concrete types under LibPETSc.AbstractPetscDM, not one type with a runtime string flavour. Code annotated ::PetscDM no longer matches — use AbstractPetscDM. PETSc.narrow(dm) turns a low-level handle into the typed one; it queries PETSc, so its return type is a wide Union and hot code should narrow once behind a function barrier. The nine DM-flavour @asserts are gone: dispatch enforces what they checked.

Borrowed handles. A reader that hands back a PETSc object owned by another object — dm(ksp), solution(snes), local_coordinates(dm), tolerances(ts)'s vectors — returns a borrowed handle: no finalizer, and destroy! on it is a no-op (PETSc.owns tells the two apart). Nothing changed at runtime; destroying such a handle was corrupting the owner's already. destroy is now destroy!, per the mutation convention.

Type names are Symbol. type_name on a Vec, Mat, KSP, SNES, TS or DM returns a Symbol, or nothing when PETSc has no type for the object yet, so type_name(ksp) == "gmres" is now false; compare against :gmres. The new set_type!(obj, :gmres) covers Vec, Mat, KSP, SNES and DM as well as TS, and set_type!(obj, "gmres") warns until v0.6. This break has no shim on the reader side.

Argument order, and petsclib dropped. The written vector leads, the DM follows it, and the library is recovered from the object: project_function!(X, dm, time, funcs, ctxs, mode), project_field!(X, dm, time, U, funcs, mode), global_to_local!(lvec, dm, gvec, mode), local_to_global!(gvec, dm, lvec, mode), l2diff(dm, time, funcs, ctxs, X), add_boundary!(dm, …), add_natural_boundary!(dm, …), set_snes_local_fem!(dm), save_vtk!(vec, filename), star_fd_coloring(da). The v0.4 spellings forward and warn, but a call passed through invoke or a function reference is not caught.

... (truncated)

Commits

• 1889553 Merge remote-tracking branch 'upstream/main' into merge-main-into-v05
• ab3c9e3 CHANGELOG: #270, #271, and the 0.4.14 names that 0.5 drops (#275)
• 8395003 Docs: add upgrade guide from 0.4, and the CHANGELOG as release notes (#276)
• 14d0f4d Check that the library is initialized in the DMDA, DMStag and more (#277)
• af1846d Docs for the v0.5 release: drop the plan files and the proposal banner (#274)
• 9637f0a Reset the RegisterAllCalled flags with a one-byte store (#273)
• b9a8d58 Remove Windows user instructions from README
• 3f4a349 Update README.md
• 00b0153 Update DOI badge in README.md
• 4bc3019 Fix block setindex! on Mat: wrong array rank, and row-major values (#271)
• Additional commits viewable 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