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.

Sign up for GitHub

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

Jump to bottom

New version: VisClaw v0.7.5 #61556

Closed
wants to merge 1 commit into from
Closed

New version: VisClaw v0.7.5 #61556

wants to merge 1 commit into from

Conversation

JuliaRegistrator
Copy link
Contributor

@JuliaRegistrator
New version: VisClaw v0.7.5
4c62e29 
UUID: d5c85fe6-8620-4d3a-96f0-ac478d4f5d38
Repo: https://github.com/hydrocoast/VisClaw.jl.git
Tree: be955b91ba6a94d1f00dcd00ddda6ac224a9df27

Registrator tree SHA: 8e1a5ac2695627143951512d700c7e3c445102ec
@JuliaRegistrator JuliaRegistrator mentioned this pull request Jun 2, 2022
Closed
@JuliaRegistrator JuliaRegistrator temporarily deployed to stopwatch June 2, 2022 09:42 Inactive
@github-actions
Copy link
Contributor

github-actions bot commented Jun 2, 2022

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:

  • I was not able to load the package (i.e. import VisClaw failed). See the CI logs 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.

After you have fixed the AutoMerge issues, simple 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.

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.

@giordano
Copy link
Member

giordano commented Jun 3, 2022

@hydrocoast please see the message above. Once you fix the automerge issues you can register again the new revision without changing the version number and this pull request will be automatically updated.

[noblock]

@hydrocoast
Copy link

hydrocoast commented Jun 4, 2022 •
edited
Loading

Thank you for the notification. It may take some time to fix the CI settings, so you can close it without merging; I will register again after the Automarge and CI problems are fixed.

@giordano giordano closed this Jun 4, 2022
@giordano giordano deleted the registrator/visclaw/d5c85fe6/v0.7.5 branch June 4, 2022 08:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
patch release
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@JuliaRegistrator @giordano @hydrocoast