Open ufechner7 opened 2 years ago
@JuliaRegistrator register
@JuliaRegistrator register
Registration pull request created: JuliaRegistries/General/61050
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>" 086dbb282df929935c77baea68dfbdca3e2fbdb4
git push origin v0.1.0
@JuliaRegistrator register
Error while trying to register: "Tag with name v0.1.0
already exists and points to a different commit"
@JuliaRegistrator register
Registration pull request created: JuliaRegistries/General/61250
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>" ab230f04e1e47db2cda4427b709cef450bbcf6be
git push origin v0.1.1
@JuliaRegistrator register
Registration pull request created: JuliaRegistries/General/61266
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>" f0469a60667aae6daf91a18bdacac6bb089a825f
git push origin v0.1.2
@JuliaRegistrator register
Error while trying to register: "Tag with name v0.1.2
already exists and points to a different commit"
@JuliaRegistrator register
Registration pull request created: JuliaRegistries/General/62979
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>" fd321ed19f39ab1d69c16912aef4e305ad774285
git push origin v0.1.3
@JuliaRegistrator register
Registration pull request created: JuliaRegistries/General/62992
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>" 8125784b11689bbc83fcbbf1ec3d6d0f9295fc4b
git push origin v0.1.4
@JuliaRegistrator register
Error while trying to register: "Tag with name v0.1.4
already exists and points to a different commit"
@JuliaRegistrator register
Registration pull request created: JuliaRegistries/General/63129
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.5 -m "<description of version>" bdf89ce01e471330ccf9cbe5c55c1588b7351824
git push origin v0.1.5
@JuliaRegistrator register
Registration pull request created: JuliaRegistries/General/63562
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.6 -m "<description of version>" 244392dd2e4e64abc65d9bc875585cc40a09f263
git push origin v0.1.6
@JuliaRegistrator register
Registration pull request created: JuliaRegistries/General/81261
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.7 -m "<description of version>" f9ea76ce48ecdb2355977e961a909eb6303e3170
git push origin v0.1.7
@JuliaRegistrator register
Registration pull request created: JuliaRegistries/General/103057
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
- blah
To add them here just re-invoke and the PR will be updated.
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.2.0 -m "<description of version>" bedfbbd09e3524741278ced0bf5e15b716895a7c
git push origin v0.2.0
@JuliaRegistrator register
Registration pull request created: JuliaRegistries/General/103186
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
- blah
To add them here just re-invoke and the PR will be updated.
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.2.1 -m "<description of version>" de5f14b1b09b195ffaef13ed44ac88aebf7caf55
git push origin v0.2.1
@JuliaRegistrator register
Registration pull request created: JuliaRegistries/General/103909
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
- blah
To add them here just re-invoke and the PR will be updated.
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.2.2 -m "<description of version>" f3de6ad61b90a1e786f10a1dda3a2abd15f74a6b
git push origin v0.2.2
@JuliaRegistrator register
Registration pull request created: JuliaRegistries/General/103951
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.3.0 -m "<description of version>" 029afa2fa4deb4c28a71f4e75e42ffe1e2ad7e7a
git push origin v0.3.0
Registration pull request updated: JuliaRegistries/General/103951
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.3.0 -m "<description of version>" 029afa2fa4deb4c28a71f4e75e42ffe1e2ad7e7a
git push origin v0.3.0
Registration pull request updated: JuliaRegistries/General/103951
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.3.0 -m "<description of version>" 029afa2fa4deb4c28a71f4e75e42ffe1e2ad7e7a
git push origin v0.3.0
Registration pull request updated: JuliaRegistries/General/103951
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.3.0 -m "<description of version>" 029afa2fa4deb4c28a71f4e75e42ffe1e2ad7e7a
git push origin v0.3.0
@JuliaRegistrator register
Registration pull request updated: JuliaRegistries/General/103951
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.3.0 -m "<description of version>" ff4af2ed6ec9ae43247f1c74d34cd6cce4cac7f4
git push origin v0.3.0
@JuliaRegistrator register
Release notes:
Registration pull request created: JuliaRegistries/General/103964
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.3.1 -m "<description of version>" 27acf3fd275e02a1dd76f8e2476f349e3a1cfe53
git push origin v0.3.1
@JuliaRegistrator register
Registration pull request created: JuliaRegistries/General/103966
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
- blah
To add them here just re-invoke and the PR will be updated.
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.3.2 -m "<description of version>" 34c2b962e84bfd3376165c32d0329bce52797849
git push origin v0.3.2
@JuliaRegistrator register
Registration pull request created: JuliaRegistries/General/103967
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
- blah
To add them here just re-invoke and the PR will be updated.
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.3.3 -m "<description of version>" beb0c2a2ffad760d23a8d36fc210c743d7e6f3e5
git push origin v0.3.3
@JuliaRegistrator register
Registration pull request updated: JuliaRegistries/General/103967
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
- blah
To add them here just re-invoke and the PR will be updated.
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.3.3 -m "<description of version>" 0277ed2141ed14fe610fd8487d82add294df97fb
git push origin v0.3.3
@JuliaRegistrator register
Release notes:
Registration pull request created: JuliaRegistries/General/103993
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.3.4 -m "<description of version>" 5303d4caef7173b3f88d14f4a32e22e4ccd8c356
git push origin v0.3.4
@JuliaRegistrator register
Registration pull request created: JuliaRegistries/General/104200
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
- blah
To add them here just re-invoke and the PR will be updated.
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.3.5 -m "<description of version>" 28967de0f9db1cca06670e92ef2af09cedd29607
git push origin v0.3.5
@JuliaRegistrator register
Release notes:
Registration pull request created: JuliaRegistries/General/104212
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.3.6 -m "<description of version>" 9caee055e434743af85f7347613ddbed049c7147
git push origin v0.3.6
https://github.com/JuliaRegistries/General/pull/61020