Register

[ChrisRackauckas]

@JuliaRegistrator register() branch=0.2

[ChrisRackauckas]

@JuliaRegistrator register() branch=0.2

[ChrisRackauckas]

@JuliaRegistrator register() branch=1.0

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/138381

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 v0.2.0 -m "<description of version>" a4d793c895d4b91b253ed14d825c67f8cd894431
git push origin v0.2.0

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/138382

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 v1.0.0 -m "<description of version>" aa495257895134269f3ed90e3fae023c47c346eb
git push origin v1.0.0

[ChrisRackauckas]

@JuliaRegistrator register() branch=2.0

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/138383

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 v2.0.0 -m "<description of version>" c9c82bed0e627111f3072e5e0fe094837b2fc82d
git push origin v2.0.0

Also, note the warning: Version 2.0.0 skips over 1.0.0
This can be safely ignored. However, if you want to fix this you can do so. Call register() again after making the fix. This will update the Pull request.

[ChrisRackauckas]

@JuliaRegistrator register() branch=0.2

Release notes:

Breaking changes

• Support completely changed to updated SymbolicUtils.jl packages

[JuliaRegistrator]

Registration pull request updated: JuliaRegistries/General/138381

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 v0.2.0 -m "<description of version>" a4d793c895d4b91b253ed14d825c67f8cd894431
git push origin v0.2.0

[ChrisRackauckas]

@JuliaRegistrator register() branch=1.0

Release notes:

Breaking changes

• Library was updated to use Symbolics.jl with a new generalized interface.

[JuliaRegistrator]

Registration pull request updated: JuliaRegistries/General/138382

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 v1.0.0 -m "<description of version>" aa495257895134269f3ed90e3fae023c47c346eb
git push origin v1.0.0

[ChrisRackauckas]

@JuliaRegistrator register() branch=2.0

Release notes:

Breaking changes

• Interface was changed to support multiple integration methods and documented according to a style of multiple integration methods.

@JuliaRegistrator register()

Release notes:

Breaking changes

• Rule-based integration method was added, along with lots of dependencies for the new method set.

[JuliaRegistrator]

Registration pull request updated: JuliaRegistries/General/138383

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 v2.0.0 -m "<description of version>" c9c82bed0e627111f3072e5e0fe094837b2fc82d
git push origin v2.0.0

Also, note the warning: Version 2.0.0 skips over 1.0.0
This can be safely ignored. However, if you want to fix this you can do so. Call register() again after making the fix. This will update the Pull request.