-
Notifications
You must be signed in to change notification settings - Fork 465
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: StatsBase v0.31.0 #1762
Conversation
JuliaRegistrator
commented
Jul 3, 2019
- Registering package: StatsBase
- Repository: https://github.com/JuliaStats/StatsBase.jl
- Created by: @ararslan
- Version: v0.31.0
- Commit: e2ceeec803e4cec70d59d8a86a6d2445e2707158
- Reviewed by: @ararslan
- Reference: JuliaStats/StatsBase.jl@e2ceeec#commitcomment-34178265
UUID: 2913bbd-ae8a-5f71-8c99-4fb6c76f3a91 Repo: https://github.com/JuliaStats/StatsBase.jl.git Tree: 2b6ca97be7ddfad5d9f16a13fe277d29f3d11c23 Registrator tree SHA: 3358484330f361397979cc5f65a9354333511e25
Since `eweights` is now being exported we should bump the minor version number
0.30.1? Or is this truly breaking this time? |
This is breaking because it changes the package exports and may introduce collisions as discussed here: |
It adds a feature, that adds an export: |
We've also talked about this in the julia slack in general. The preference seems to be that new exports should not be point releases, but shouldn't require a major release on post-1.0 packages. The ideal is that StatsBase will hit 1.0 sooner rather than later. |
I tried to create a release but ran into this error:
To retry, comment on this PR with the phrase |
TagBot tag |
I tried to create a release but ran into this error:
To retry, comment on this PR with the phrase |
Oh, for some reason TagBot was only enabled for a few repos. TagBot tag |
TagBot tag |
@ararslan I already just manually made the tag |
Oh, okay. Thanks :) |