Repository navigation
Register #3
Description
Activity
Registration pull request created: JuliaRegistries/General/51405
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:
git tag -a v0.1.0 -m "<description of version>" a7eae509c5b3ac4223f87ff8f299c48991d354b2 git push origin v0.1.0@JuliaRegistrator register()
Registration pull request updated: JuliaRegistries/General/51405
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:
git tag -a v0.1.0 -m "<description of version>" a7eae509c5b3ac4223f87ff8f299c48991d354b2 git push origin v0.1.0@JuliaRegistrator register()
Registration pull request created: JuliaRegistries/General/97742
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.@JuliaRegistrator register Release notes: ## Breaking changes - blahTo add them here just re-invoke and the PR will be updated.
Tagging
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:
git tag -a v0.1.2 -m "<description of version>" 2eece853b7384a60174f9067f149b91f095301e9 git push origin v0.1.2Also, note the warning: Version 0.1.2 skips over 0.1.1
This can be safely ignored. However, if you want to fix this you can do so. Call register() again after making the fix. This will update the Pull request.@JuliaRegistrator register()
Registration pull request created: JuliaRegistries/General/97743
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.@JuliaRegistrator register Release notes: ## Breaking changes - blahTo add them here just re-invoke and the PR will be updated.
Tagging
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:
git tag -a v0.1.1 -m "<description of version>" 72bb83f1977d6427f9ccd81c8fd0391fdcb23354 git push origin v0.1.1@JuliaRegistrator register()
Registration pull request created: JuliaRegistries/General/106025
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.@JuliaRegistrator register Release notes: ## Breaking changes - blahTo add them here just re-invoke and the PR will be updated.
Tagging
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:
git tag -a v0.1.2 -m "<description of version>" b4053aa0026432f3fe18d754349331ced02d79da git push origin v0.1.2@JuliaRegistrator register()
Registration pull request created: JuliaRegistries/General/128090
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.@JuliaRegistrator register Release notes: ## Breaking changes - blahTo add them here just re-invoke and the PR will be updated.
Tagging
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:
git tag -a v0.1.3 -m "<description of version>" 1fa24d72d20539486d252e32a35401ce3efd87e1 git push origin v0.1.3@JuliaRegistrator register()
Registration pull request created: JuliaRegistries/General/163523
Recommendation: add release notes
Release notes help your users know what has changed in the new version. For breaking releases in particular, it's recommended to document what breaking changes were made (or point to where changes can be found, such as a changelog).
To add release notes, just add markdown formatted text underneath the comment after the text "Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the release that TagBot creates. i.e.
@JuliaRegistrator register Release notes: ## Breaking changes - blahTo add release notes to this registration, just re-invoke JuliaRegistrator and the PR will be updated.
Tagging
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:
git tag -a v0.1.4 -m "<description of version>" 682697ceeff14a9f8886b590d07e553d8683e012 git push origin v0.1.4
@JuliaRegistrator register()