Repository navigation
Increment Version #82
Description
Activity
Registration pull request created: JuliaRegistries/General/110567
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.11.5 -m "<description of version>" dda6c95fdbe47bf390fe13c03c5f39fb046abd84 git push origin v0.11.5@JuliaRegistrator register()
Registration pull request created: JuliaRegistries/General/113154
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.11.6 -m "<description of version>" c015ca4f701b290f35ca22a55eff320a7b508dbf git push origin v0.11.6@JuliaRegistrator register()
Registration pull request created: JuliaRegistries/General/113244
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.11.7 -m "<description of version>" b2dbcb0de43b0d1b3f730ca04e5dfe0681a8ffc7 git push origin v0.11.7@JuliaRegistrator register()
Registration pull request created: JuliaRegistries/General/113968
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.11.8 -m "<description of version>" 003199aef23f8f5c39e2035fd0a048d576ad3e50 git push origin v0.11.8@JuliaRegistrator register()
Registration pull request created: JuliaRegistries/General/114090
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.11.9 -m "<description of version>" 42f316c04073f19007a4d8f28a17c62d16bed598 git push origin v0.11.9@JuliaRegistrator register()
Registration pull request created: JuliaRegistries/General/114220
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.11.10 -m "<description of version>" cd6311e28473112d9c9d9c5c94c06f79956eded1 git push origin v0.11.10@JuliaRegistrator register()
Registration pull request created: JuliaRegistries/General/117209
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.11.11 -m "<description of version>" 0f8f1c5277bce8a4fa9ea05cc7373329fe0d5bb5 git push origin v0.11.11@JuliaRegistrator register()
16 remaining items
Error while trying to register: "Pre-release version not allowed"
@JuliaRegistrator register()
Registration pull request created: JuliaRegistries/General/133232
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.12.4 -m "<description of version>" 8a2fede77526f2b44143b87d7cf111dcc9d8542c git push origin v0.12.4@JuliaRegistrator register()
Registration pull request created: JuliaRegistries/General/134349
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.12.5 -m "<description of version>" 71f27871f17c270a8ad2f3a62283030806cf3b96 git push origin v0.12.5@JuliaRegistrator register()
Registration pull request created: JuliaRegistries/General/134506
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.12.6 -m "<description of version>" 4fd93a8c0e475aa020ef73e63ad6db6dfc2ed585 git push origin v0.12.6@JuliaRegistrator register
Release notes:
Breaking changes
- added argument checks on all constructors
- added checks for negative/NaN rts
Registration pull request created: JuliaRegistries/General/141272
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.13.0 -m "<description of version>" 05256fc2acdd6ab51575b73e6e2a2d78a77a0512 git push origin v0.13.0@JuliaRegistrator register()
Registration pull request created: JuliaRegistries/General/150548
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.13.1 -m "<description of version>" 08c667d24b3fe1126a82a0c8ff9b203c5df2a722 git push origin v0.13.1@JuliaRegistrator register()
Registration pull request created: JuliaRegistries/General/150594
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.13.2 -m "<description of version>" 91372f84741c751b2019d8eceee56a2ef842f414 git push origin v0.13.2@JuliaRegistrator register()
Registration pull request created: JuliaRegistries/General/161490
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.13.3 -m "<description of version>" 0014dcdc00566111b6912ab6c301e5c2296b61a1 git push origin v0.13.3
@JuliaRegistrator register()