Skip to content

New version: SovovaMulti v1.0.24 - #150261

Closed
JuliaRegistrator wants to merge 1 commit into
masterfrom
registrator-sovovamulti-0cf59ef5-v1.0.24-9cf7987c30
Closed

New version: SovovaMulti v1.0.24#150261
JuliaRegistrator wants to merge 1 commit into
masterfrom
registrator-sovovamulti-0cf59ef5-v1.0.24-9cf7987c30

Conversation

@JuliaRegistrator

Copy link
Copy Markdown
Contributor
First fully functional version.

UUID: 0cf59ef5-fec3-4aea-9b72-567761fff152
Repo: https://github.com/lmiq/SovovaMulti.jl.git
Tree: 35bdfc0dc70e8016130b63a0af5a9029f5d4d63b

Registrator tree SHA: 50f504d641745716a5b3eabaf681d3a4937d2ae3
@github-actions

Copy link
Copy Markdown
Contributor

Hello, I am an automated registration bot. I help manage the registration process by checking your registration against a set of AutoMerge guidelines. If all these guidelines are met, this pull request will be merged automatically, completing your registration. It is strongly recommended to follow the guidelines, since otherwise the pull request needs to be manually reviewed and merged by a human.

1. AutoMerge Guidelines which are not met ❌

  • Does not meet sequential version number guideline: version 1.0.24 skips over 1.0.1. If this was not a mistake and you wish to merge this PR anyway, write a comment that says [merge approved].
  • A patch release is not allowed to narrow the supported ranges of Julia versions. The ranges have changed from Pkg.Versions.VersionRange[VersionRange("1.10.0 - 1")] (in 1.0.0) to Pkg.Versions.VersionRange[VersionRange("1.12.0 - 1")] (in 1.0.24).

2. Needs action: here's what to do next

  1. Please try to update your package to conform to these guidelines. The General registry's README has an FAQ that can help figure out how to do so.
  2. After you have fixed the AutoMerge issues, simply retrigger Registrator, the same way you did in the initial registration. This will automatically update this pull request. You do not need to change the version number in your Project.toml file (unless the AutoMerge issue is that you skipped a version number).

If you need help fixing the AutoMerge issues, or want your pull request to be manually merged instead, please post a comment explaining what you need help with or why you would like this pull request to be manually merged. Then, send a message to the #pkg-registration channel in the public Julia Slack for better visibility.

3. To pause or stop registration

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.

Tip: You can edit blocking comments to add [noblock] in order to unblock auto-merging.

@github-actions

Copy link
Copy Markdown
Contributor

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. It would also be helpful if you could post a message in the #pkg-registration channel of the JuliaLang Slack (https://julialang.org/slack/), to increase visibility. [noblock]

@github-actions github-actions Bot added the stale label Apr 11, 2026
@github-actions

Copy link
Copy Markdown
Contributor

This pull request has been inactive for more than 30 days and has automatically been closed. Feel free to register your package or version again once you fix the AutoMerge issues. If you need help, you can ask in the #pkg-registration channel of the JuliaLang Slack (https://julialang.org/slack/). [noblock]

@github-actions github-actions Bot closed this Apr 18, 2026
@github-actions
github-actions Bot deleted the registrator-sovovamulti-0cf59ef5-v1.0.24-9cf7987c30 branch April 18, 2026 12:27
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.

1 participant