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

yank MLJDecisionTreeInterface 0.2.4 #67468

Merged
merged 1 commit into from
Sep 4, 2022
Merged

yank MLJDecisionTreeInterface 0.2.4 #67468

merged 1 commit into from
Sep 4, 2022

Conversation

ablaom
Copy link
Contributor

@ablaom ablaom commented Sep 1, 2022

@ericphanson
Copy link
Member

ericphanson commented Sep 2, 2022

Some folks would prefer package authors push a revert commit and then register a new patch release, instead of yanking: #62795. That has the advantage that one doesn't need to refer to the registry (only the package's Project.toml and git history) to understand the current state of the releases, and it doesn't require manual intervention by the registry maintainers.

But if you still want to yank it, we can do that.

@DilumAluthge DilumAluthge merged commit edbd0ec into JuliaRegistries:master Sep 4, 2022
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.

3 participants