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: OhMyREPL v0.5.3 #4422

Merged
1 commit merged into from
Oct 16, 2019
Merged

Conversation

JuliaRegistrator
Copy link
Contributor

UUID: 5fb14364-9ced-5910-84b2-373655c76a03
Repo: https://github.com/KristofferC/OhMyREPL.jl.git
Tree: 8857a079cb486e1f4f148a616505743ede7ec95c

Registrator tree SHA: f50e50c1d2a1b9694b1d5749fdb25fef2ca4c291
JuliaRegistrator referenced this pull request in KristofferC/OhMyREPL.jl Oct 16, 2019
@ghost
Copy link

ghost commented Oct 16, 2019

Your new version pull request met all of the guidelines for automatic merging.

I will automatically merge this pull request during the next cron job.

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


On a separate note, I see that you are registering a release with a version number of the form v0.X.Y.

Does your package have a stable public API? If so, then it's time for you to register version v1.0.0 of your package. (This is not a requirement. It's just a recommendation.)

If your package does not yet have a stable public API, then of course you are not yet ready to release version v1.0.0.


[noblock]

@ghost
Copy link

ghost commented Oct 16, 2019

The mandatory waiting period has elapsed.

Your pull request is ready to merge.

I will now merge this pull request.


[noblock]

@ghost ghost merged commit 7bfc486 into master Oct 16, 2019
@ghost ghost deleted the registrator/ohmyrepl/5fb14364/v0.5.3 branch October 16, 2019 10:06
@julia-tagbot
Copy link

julia-tagbot bot commented Oct 16, 2019

I've created release v0.5.3, here it is.

This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant