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: GivEmXL v0.2.7 #121865

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

Conversation

JuliaRegistrator
Copy link
Contributor

  • Registering package: GivEmXL
  • Repository: https://github.com/Eben60/GivEmXL.jl
  • Created by: @Eben60
  • Version: v0.2.7
  • Commit: 453eb11958bec9f9a3f555a3631a65e18c91a880
  • Git reference: HEAD
  • Description: This Julia package helps you in creating redistributable Julia packages for "somewhat interactive" use, which optionally use files in Excel format for data input and output.

UUID: dcf505f5-2bf4-45cb-8fef-5f56a3c0e7fc
Repo: https://github.com/Eben60/GivEmXL.jl.git
Tree: 987a9661c86d2155a9002c4019dd5ce23efed08e

Registrator tree SHA: 191228b6dd8b9d0e2965ae3e705fe54c51dcfee8
@JuliaRegistrator JuliaRegistrator force-pushed the registrator-givemxl-dcf505f5-v0.2.7-b40fff7564 branch from aba4ea0 to 85a9f30 Compare December 22, 2024 21:29
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 0.2.7 skips over 0.2.6. If this was not a mistake and you wish to merge this PR anyway, write a comment that says [merge approved].

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.

@Eben60
Copy link

Eben60 commented Dec 22, 2024

wrong version number set, sorry. The commit with correct version 0.2.6 is in the meanwhile merged:
JuliaTagBot merged commit e455a09 into master.

This one can be deleted.

@JuliaTagBot JuliaTagBot added the AutoMerge: last run blocked by comment PR blocked by one or more comments lacking the string [noblock]. label Dec 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
AutoMerge: last run blocked by comment PR blocked by one or more comments lacking the string [noblock]. patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants