New version: OneRule v0.6.1

[JuliaRegistrator]

• Registering package: OneRule
• Repository: https://github.com/roland-KA/OneRule.jl
• Created by: @roland-KA
• Version: v0.6.1
• Commit: 9fe43283461c1084a922eb14d5589b42bd08bd47
• Reviewed by: @roland-KA
• Reference: JuliaAI/OneRule.jl@9fe4328#commitcomment-173991787
• Description: Implementation of the 1-Rule data mining algorithm using the Julia programming language
• Release notes:

No breaking changes

[github-actions]

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 are all met! ✅

Your new version registration met all of the guidelines for auto-merging and is scheduled to be merged in the next round (~20 minutes).

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

[roland-KA]

[merge approved]

[roland-KA]

[merge approved]

[roland-KA]

[merge approved]

[roland-KA]

I need help from a human being. The registrator bot constantly blocks registration, stating that there was a breaking change. But there was no breaking change.

I've just updated the version form 0.5 to 0.6 (or 0.6.1 now), because a compat-entry has changed and because the package is now based on Julia LTS 1.10.

[goerz]

Going from 0.5 to 0.6 is a breaking release, and must have release notes to reflect that. I think the bot just searches for the word “breaking” in the release notes. So adding a sentence “No breaking changes” should do the trick

[roland-KA]

I already added such a comment to release v0.6.1. That didn't help. I've done it now also for v0.6.0.
[noblock]

[roland-KA]

[merge approved]

[goerz]

I already added such a comment to release v0.6.1

I'm not sure where you're adding these comments… I'm not seeing them, and apparently neither is JuliaRegistrator. The usual way to register a new version is to comment on the commit that should be tagged, i.e. JuliaAI/OneRule.jl@9fe4328 — as you already did 2 weeks ago (but you forgot the release notes there).

On that comment thread you need to have a comment like

@JuliaRegistrator register

Release notes:

No breaking changes

You should also not be having a v0.6.1 tag. Tags must be created after a release has been registered, and you have TagBot set up to handle that automatically.

It also seems like you're skipping the 0.6 release — You could still register that by commenting for the JuliaRegistrator bot (with release notes!) on JuliaAI/OneRule.jl@38ccec8. Then come back to 0.6.1 afterwards.

[roland-KA]

Well, I'm adding the release notes within the release notes of GitHub (as is common on that platform). I don't understand why the register bot needs them elsewhere.

And yes, I'v skipped 0.6 because I forgot to mention the register bot on that step. I didn't know, that this can be done also afterwards. Therefore I've created 0.6.1.

[noblock]

[roland-KA]

@JuliaRegistrator register

Release notes:

No breaking changes

[goerz]

Ah, okay, that explains why you’re having a problem: you’re approaching this the wrong way around. For Julia packages, you don’t create tags or GitHub releases manually. TagBot does that for you after a release is registered. The only thing you do to initiate a release is to comment on the commit you want to have tagged with instructions to the registration bot. Those instructions must include the release notes. The bot will then create a registration PR for you. If that PR automerges, the TagBot workflow in your repo will then create both the tag and the release on GitHub. That release will include the release notes you initially passed to the registrator. It doesn’t work the other way around; again, because tags must me created after registration, not before.

If there is an issue with automerge, (as in this case: missing release notes) you can give further instruction to the registrator to fix them. That will then update the existing PR. Commenting with instructions to the bot on the PR as you tried to do above does nothing. You have to comment on the commit.

Does that clear things up a bit?

[roland-KA]

@goerz Thanks for the explanation! That really clarifies things. I haven't registered a new release for quite a time, so I wasn't familiar with that workflow anymore.

And I envy other ecosystems, where these things seem to me much simpler (like e.g. Rust https://doc.rust-lang.org/cargo/reference/publishing.html).

[goerz]

I totally agree that the Julia package release process is pretty weird. Wasn’t my idea! 😉