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: Example v2.0.0 #121629

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

JuliaRegistrator
Copy link
Contributor

Check out my new features!

UUID: 7876af07-990d-54b4-ab0e-23690620f79a
Repo: https://github.com/JuliaLang/Example.jl.git
Tree: b8a4316d5160b9c6eafdc5d320d80d8140c73b68

Registrator tree SHA: 17aec322677d9b81cdd6b9b9236b09a3f1374c6a
Copy link
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 2.0.0 skips over 1.0.0. If this was not a mistake and you wish to merge this PR anyway, write a comment that says [merge approved].

  • This is a breaking change, but no release notes have been provided. Please add release notes that explain the breaking change.

    Example of adding release notes with breaking notice

    If you are using the comment bot @JuliaRegistrator, you can add release notes to this registration by re-triggering registration while specifying release notes:

    @JuliaRegistrator register
    
    Release notes:
    
    ## Breaking changes
    
    - Explanation of breaking change, ideally with upgrade tips
    - ...
    

    If you are using JuliaHub, trigger registration the same way you did the first time, but enter release notes that specify the breaking changes.

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.

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