Register the version-sync releases (#1287)

[ChrisRackauckas]

Registering the 25 subpackage versions bumped in #1287, plus SimpleOptimization.

OptimizationBase first — every other subpackage depends on it — then the rest.

[ChrisRackauckas]

@JuliaRegistrator register subdir=lib/OptimizationBase

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/163063

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 OptimizationBase-v5.2.4 -m "<description of version>" 06a10aa9933e4316155b571948fcabb43251f0e1
git push origin OptimizationBase-v5.2.4

[ChrisRackauckas]

@JuliaRegistrator register subdir=lib/OptimizationAuglag

[ChrisRackauckas]

@JuliaRegistrator register subdir=lib/OptimizationBBO

[ChrisRackauckas]

@JuliaRegistrator register subdir=lib/OptimizationCMAEvolutionStrategy

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/163064

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 OptimizationAuglag-v2.0.3 -m "<description of version>" 06a10aa9933e4316155b571948fcabb43251f0e1
git push origin OptimizationAuglag-v2.0.3

[ChrisRackauckas]

@JuliaRegistrator register subdir=lib/OptimizationEvolutionary

[ChrisRackauckas]

@JuliaRegistrator register subdir=lib/OptimizationGCMAES

[ChrisRackauckas]

@JuliaRegistrator register subdir=lib/OptimizationLBFGSB

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/163065

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 OptimizationBBO-v0.4.10 -m "<description of version>" 06a10aa9933e4316155b571948fcabb43251f0e1
git push origin OptimizationBBO-v0.4.10

[ChrisRackauckas]

@JuliaRegistrator register subdir=lib/OptimizationMOI

[ChrisRackauckas]

@JuliaRegistrator register subdir=lib/OptimizationMadNLP