Register pending versions

[ChrisRackauckas]

Triggering registration for the versions already merged to master.

• DiffEqProblemLibrary v5.3.0

Commit-comment triggers on this repo have gone unanswered (JuliaRegistrator appears not to receive commit_comment events here), and PR comments are disabled for Registrator, so this issue is the working trigger path. It will be closed once the registrations land.

[ChrisRackauckas]

@JuliaRegistrator register branch=master

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/165574

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 v5.3.0 -m "<description of version>" c3eddb588df566047fcd4a3438fc92ab78211b61
git push origin v5.3.0

[ChrisRackauckas]

Registrations triggered and completed. Closing — this issue existed only because JuliaRegistrator was not receiving commit_comment events for this repository, so the usual trigger on the release commit went unanswered.