Register BVProblemLibrary v0.1.8 and prepare v5.3.0 release

[ChrisRackauckas-Claude]

Missing Registration

BVProblemLibrary v0.1.8 was bumped in commit bb67c7d (December 16, 2025) and was supposed to be registered alongside DiffEqProblemLibrary v5.2.0, but the registration was never completed.

Current Status

• DiffEqProblemLibrary v5.2.0: ✓ Registered (PR New version: DiffEqProblemLibrary v5.2.0 JuliaRegistries/General#145385)
• BVProblemLibrary v0.1.8: ✗ Not registered (last registered: v0.1.7)
• SDEProblemLibrary v1.1.1: ✓ Registered (PR New version: SDEProblemLibrary v1.1.1 JuliaRegistries/General#145392)

Unreleased Changes Since v5.2.0 (6 commits)

1. GitHub Actions: Bump actions/checkout from 4 to 6 (PR Bump actions/checkout from 4 to 6 #177)
2. Code formatting: Switch from JuliaFormatter to Runic.jl (PR Switch from JuliaFormatter to Runic.jl for code formatting #176)
3. Performance: Enable precompilation for SDEProblemLibrary (PR Enable precompilation for SDEProblemLibrary #175, already registered as v1.1.1)

Action Plan

Step 1: Register BVProblemLibrary v0.1.8

Comment on the latest commit to master:

@JuliaRegistrator register subdir=lib/BVProblemLibrary

Step 2: Decide on v5.3.0 Release

After BVProblemLibrary v0.1.8 is registered, determine if a new release (v5.3.0) is warranted for the formatting and workflow changes. These are mostly cosmetic changes:

• Runic.jl formatting affects all subpackage source files but doesn't change functionality
• Workflow update is CI-only

Recommendation: Wait for BVProblemLibrary v0.1.8 to be registered first, then consider whether the formatting changes merit a v5.3.0 release or should wait for the next functional change.

cc @ChrisRackauckas

[JuliaRegistrator]

Error while trying to register: Register Failed
@ChrisRackauckas-Claude, it looks like you are not a publicly listed member/owner in the parent organization (SciML).
If you are a member/owner, you will need to change your membership to public. See GitHub Help

[ChrisRackauckas]

@JuliaRegistrator register subdir=lib/BVProblemLibrary

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/145733

Recommendation: add release notes

Release notes help your users know what has changed in the new version. For breaking releases in particular, it's recommended to document what breaking changes were made (or point to where changes can be found, such as a changelog).

To add release notes, just add markdown formatted text underneath the comment after the text "Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the release that TagBot creates. i.e.

@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add release notes to this registration, just re-invoke JuliaRegistrator and the PR will be updated.

Tagging

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a BVProblemLibrary-v0.1.8 -m "<description of version>" 2de13b69733ca97b4839cd641ea94e293bc187eb
git push origin BVProblemLibrary-v0.1.8