Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New version: GalacticOptim v0.1.3 #19941

Closed

Conversation

JuliaRegistrator
Copy link
Contributor

UUID: a75be94c-b780-496d-a8a9-0878b188d577
Repo: https://github.com/SciML/GalacticOptim.jl.git
Tree: f8a9b565214f36fbbf78fc44a0e46c3f4099ca59

Registrator tree SHA: 58e84c9733c0606ca53349dbce519209d8a8402b
@github-actions
Copy link
Contributor

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

  • Does not meet sequential version number guideline: version 0.1.3 skips over 0.1.2
  • The following dependencies do not have a compat entry that has an upper bound: Flux, ProgressLogging, Tracker. You may find CompatHelper helpful for keeping your compat entries up-to-date.Note: If your package works for the current version x.y.z of a dependency foo, then a compat entry foo = x.y.z implies a compatibility upper bound for packages following semver. You can additionally include earlier versions your package is compatible with. See https://julialang.github.io/Pkg.jl/v1/compatibility/ for details.

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.


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.

@DilumAluthge DilumAluthge deleted the registrator/galacticoptim/a75be94c/v0.1.3 branch August 21, 2020 19:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants