-
-
Notifications
You must be signed in to change notification settings - Fork 14
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 Release #9
Comments
Release when you need to. If a repo is sitting for a bit with some unreleased commits I usually make sure they end up released. |
Okay, thanks. |
@JuliaRegistrator register() |
Registration pull request created: JuliaRegistries/General/3590 After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version. This will be done automatically if Julia TagBot is installed, or can be done manually through the github interface, or via:
|
@JuliaRegistrator register() |
Registration pull request created: JuliaRegistries/General/82238 After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version. This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
|
@JuliaRegistrator register() |
Registration pull request created: JuliaRegistries/General/113613 Tip: Release NotesDid you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
To add them here just re-invoke and the PR will be updated. TaggingAfter the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version. This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
|
I've added some additional functionality in the last days but do not plan to add more in the next few days. Shall/can we release a new version?
How shall we generally proceed with releasing a new version?
The text was updated successfully, but these errors were encountered: