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: Tk v0.6.0 #8912

Merged
merged 1 commit into from
Feb 5, 2020
Merged

Conversation

JuliaRegistrator
Copy link
Contributor

UUID: 4225ea8a-3324-57e7-9ddc-5798a2cb9eab
Repo: https://github.com/JuliaGraphics/Tk.jl.git
Tree: a2adcdf08745f58bcc8a4bd70b0a15e7066fd96c

Registrator tree SHA: f50e50c1d2a1b9694b1d5749fdb25fef2ca4c291
JuliaRegistrator referenced this pull request in JuliaGraphics/Tk.jl Feb 5, 2020
@aviks
Copy link
Contributor

aviks commented Feb 5, 2020

So this will fail automerge checks, I would request a manual merge, without a three days wait.

The name Tk is short, but has a thirty year history. There is nothing else this package should be called. The Julia package itself has existed under this name for at least 7 years. It was removed during the Great Package Purge, and is asking for its legitimate position back!

@github-actions
Copy link
Contributor

github-actions bot commented Feb 5, 2020

Your new package pull request does not meet the following guidelines for auto-merging:

  • Name is not at least five characters long
  • Version number is not 0.0.1, 0.1.0, or 1.0.0
  • The following dependencies do not have a compat entry that has an upper bound: BinDeps, Cairo, Graphics, WinRPM. You may find CompatHelper helpful for keeping your compat entries up-to-date.Note: If your package works for the current version x.y.z of a dependency foo, then a compat entry foo = x.y.z implies a compatibility upper bound for packages following semver. You can additionally include earlier versions your package is compatible with. See https://julialang.github.io/Pkg.jl/v1/compatibility/ 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.


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.

@fredrikekre fredrikekre merged commit a41f468 into master Feb 5, 2020
@fredrikekre fredrikekre deleted the registrator/tk/4225ea8a/v0.6.0 branch February 5, 2020 11:40
@julia-tagbot
Copy link

julia-tagbot bot commented Feb 5, 2020

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

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.

3 participants