New version: Optimization v3.21.3

[JuliaRegistrator]

• Registering package: Optimization
• Repository: https://github.com/SciML/Optimization.jl
• Created by: @Vaibhavdixit02
• Version: v3.21.3
• Commit: 28028fe62ed1fa1b37343603e45c2a507b42eb81
• Reviewed by: @Vaibhavdixit02
• Reference: Register SciML/Optimization.jl#16 (comment)
• Description: Mathematical Optimization in Julia. Local, global, gradient-based and derivative-free. Linear, Quadratic, Convex, Mixed-Integer, and Nonlinear Optimization in one simple, fast, and differentiable interface.

[github-actions]

Your new version pull request does not meet the guidelines for auto-merging. Please make sure that you have read the General registry README and the AutoMerge guidelines. The following guidelines were not met:

• The following dependencies do not have a [compat] entry that is upper-bounded and only includes a finite number of breaking releases: SciMLBase

Note that the guidelines are only required for the pull request to be merged automatically. However, it is strongly recommended to follow them, since otherwise the pull request needs to be manually reviewed and merged by a human.

After you have fixed the AutoMerge issues, simply retrigger Registrator, which will automatically update this pull request. You do not need to change the version number in your Project.toml file (unless of course the AutoMerge issue is that you skipped a version number, in which case you should change the version number).

If you do not want to fix the AutoMerge issues, please post a comment explaining why you would like this pull request to be manually merged. Then, send a message to the #pkg-registration channel in the Julia Slack to ask for help. Include a link to this pull request.

---

If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text [noblock] in your comment. You can edit blocking comments, adding [noblock] to them in order to unblock auto-merging.

[DilumAluthge]

[noblock]

Looks like there is a merge conflict.

@Vaibhavdixit02 Can you re-trigger Registrator? This will fix the merge conflict.

[github-actions]

This pull request has been inactive for 30 days and will be automatically closed 7 days from now. If this pull request should not be closed, please either (1) fix the AutoMerge issues and re-trigger Registrator, which will automatically update the pull request, or (2) post a comment explaining why you would like this pull request to be manually merged. [noblock]

[DilumAluthge]

[noblock]

Looks like there is a merge conflict.

@Vaibhavdixit02 Can you re-trigger Registrator? This will fix the merge conflict.

[github-actions]

This pull request has been inactive for 30 days and will be automatically closed 7 days from now. If this pull request should not be closed, please either (1) fix the AutoMerge issues and re-trigger Registrator, which will automatically update the pull request, or (2) post a comment explaining why you would like this pull request to be manually merged. [noblock]

[DilumAluthge]

[noblock]

Looks like there is a merge conflict.

@Vaibhavdixit02 Can you re-trigger Registrator? This will fix the merge conflict.

[Vaibhavdixit02]

[noblock]

Hey @DilumAluthge this is actually a pretty old version (we are now at 2.24.3) so I don't think it matters? I am good with closing this, though I am very surprised I missed your pings above and this failed to get merged sorry about that

[DilumAluthge]

No worries at all! Cool, I'll close this.