Open gaelforget opened 1 year ago
@JuliaRegistrator register()
Registration pull request created: JuliaRegistries/General/73552
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.15 -m "<description of version>" c7340c689e1756aca4e9533bb52522dffd56956c
git push origin v0.1.15
@gmaze
Just FYI the sequence above is how new release works automatically via the @JuliaRegistrator
bot
Error while trying to register: Action not recognized: bot
Error while trying to register: Action not recognized: bot
@gaelforget I just installed the https://github.com/JuliaComputing/Registrator.jl#install-registrator app at euroargodev level, so this action should be recognized now
Then the following happens (assuming the TagBot workflow is enabled) :
and Voila! as they say
It's pretty much the same for Conda, except it's happening on a dedicated repo eg for argopy: https://github.com/conda-forge/argopy-feedstock
@JuliaRegistrator register()
Registration pull request created: JuliaRegistries/General/95576
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.1.16 -m "<description of version>" dcc60566f2308a6e9f7506b7c51dad41424720d4
git push origin v0.1.16
@JuliaRegistrator register()
Registration pull request created: JuliaRegistries/General/95704
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.1.17 -m "<description of version>" 7221c63ae0e653e7cbb45eef6fd781b665fcc95a
git push origin v0.1.17
@JuliaRegistrator register()
Registration pull request created: JuliaRegistries/General/103953
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.1.18 -m "<description of version>" 60f66e64d9cbe50521cf138d9ec259b6cd4f17dd
git push origin v0.1.18
@JuliaRegistrator register()
Registration pull request created: JuliaRegistries/General/103957
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.1.19 -m "<description of version>" 656f95db42df881ff48c76079c6face616a370de
git push origin v0.1.19
@JuliaRegistrator register()
Registration pull request created: JuliaRegistries/General/113273
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.1.20 -m "<description of version>" e57d5c500142c985f4e9c06a2eefc01173798daa
git push origin v0.1.20
@JuliaRegistrator register()
Registration pull request created: JuliaRegistries/General/113609
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.1.21 -m "<description of version>" a2458881ab5fcce5d0644ef93c0b8223dcfc39a4
git push origin v0.1.21
@JuliaRegistrator register()