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 package: PRAS v0.7.0 #121156

Merged
merged 1 commit into from
Dec 13, 2024

Conversation

JuliaRegistrator
Copy link
Contributor

@JuliaRegistrator JuliaRegistrator commented Dec 10, 2024

@GordStephen
Copy link

GordStephen commented Dec 10, 2024

Note that the automerge checks won't pass because of the package name, but consensus in #120172 and #120786 seems to be that we can get an exception for this? [noblock]

Copy link
Contributor

github-actions bot commented Dec 10, 2024

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. New package registration

Please make sure that you have read the package naming guidelines.

2. AutoMerge Guidelines which are not met ❌

  • Name does not meet all of the following: starts with an upper-case letter, ASCII alphanumerics only, not all letters are upper-case.
  • Name is not at least 5 characters long

3. 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.

4. 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.

@GordStephen
Copy link

GordStephen commented Dec 10, 2024

Whoops, looks like we're missing compat bounds for Reexport, let me fix that. [noblock]

Update: fixed

@JuliaTagBot JuliaTagBot added the AutoMerge: last run blocked by comment PR blocked by one or more comments lacking the string [noblock]. label Dec 10, 2024
@JuliaTagBot JuliaTagBot removed the AutoMerge: last run blocked by comment PR blocked by one or more comments lacking the string [noblock]. label Dec 10, 2024
UUID: 05348d2-1c52-11e9-35e3-9d51842d34b9
Repo: https://github.com/NREL/PRAS.git
Tree: 31fed7232c439c8def5897a4bcb788e72c3f3ec2

Registrator tree SHA: 17aec322677d9b81cdd6b9b9236b09a3f1374c6a
@fredrikekre
Copy link
Member

#121152 (comment)

@fredrikekre fredrikekre merged commit 2f81439 into master Dec 13, 2024
16 of 19 checks passed
@fredrikekre fredrikekre deleted the registrator-pras-05348d26-v0.7.0-6526c84471 branch December 13, 2024 14:43
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.

5 participants