Open korenmiklos opened 3 months ago
Error while trying to register: "Tag with name v0.4.0
already exists and points to a different commit"
@JuliaRegistrator register()
Registration pull request created: JuliaRegistries/General/110353
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.4.1 -m "<description of version>" 53e86547785f9648d758c89bb92abf7c8bb7da90
git push origin v0.4.1
Also, note the warning: This looks like a new registration that registers version 0.4.1. Ideally, you should register an initial release with 0.0.1, 0.1.0 or 1.0.0 version numbers 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 updated: JuliaRegistries/General/110353
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.4.1 -m "<description of version>" 53e86547785f9648d758c89bb92abf7c8bb7da90
git push origin v0.4.1
Also, note the warning: This looks like a new registration that registers version 0.4.1. Ideally, you should register an initial release with 0.0.1, 0.1.0 or 1.0.0 version numbers 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.
I added a compat string to RDatasets
@JuliaRegistrator register
Registration pull request updated: JuliaRegistries/General/110353
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.4.1 -m "<description of version>" 00869d6d09ed3cd3327138ab455b740134652333
git push origin v0.4.1
Also, note the warning: This looks like a new registration that registers version 0.4.1. Ideally, you should register an initial release with 0.0.1, 0.1.0 or 1.0.0 version numbers 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/110398
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.4.3 -m "<description of version>" 3305cff28c43e3949edec2542daa70d9d5f61f38
git push origin v0.4.3
Also, note the warning: This looks like a new registration that registers version 0.4.3. Ideally, you should register an initial release with 0.0.1, 0.1.0 or 1.0.0 version numbers 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/110740
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.4.5 -m "<description of version>" 6faf5f61bbf639965637766840b014cb341b26af
git push origin v0.4.5
Also, note the warning: Version 0.4.5 skips over 0.4.4 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
Error while trying to register: Version 0.4.5 already exists
@JuliaRegistrator register
Registration pull request created: JuliaRegistries/General/110815
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.4.6 -m "<description of version>" c7677b03b1f0361f05a60b353a7d8047cef1a636
git push origin v0.4.6
@JuliaRegistrator register
Registration pull request created: JuliaRegistries/General/110934
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.4.7 -m "<description of version>" 88bb0044ddf8b8cd4c47bf8c10ee63313637a7d8
git push origin v0.4.7
@JuliaRegistrator register
Registration pull request created: JuliaRegistries/General/111110
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.4.8 -m "<description of version>" 26aae122acd18d4534977afabbe2342c4ca0788f
git push origin v0.4.8
@JuliaRegistrator register
Release notes:
New features implemented:
@clear
@use "fname.dta", clear
@describe
@list varlist
~f(x)
to stop vectorization of f()
cond()
functionTests passing: 425/425
] test
runs without errorsRegistration pull request created: JuliaRegistries/General/111838
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.5.1 -m "<description of version>" 8e4b39942d379a2665591a4d9c43810de220aa57
git push origin v0.5.1
Also, note the warning: Version 0.5.1 skips over 0.5.0 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
Release notes:
generate
, egen
and replace
, removed setdf
from the end to avoid copying the entire df. @mvencode
(#176)@save
(#179)474/474
Also see test/speed.jl
(I should turn this into a unit test!)
] test
runs without errorsNew features implemented in the API and updated speed benchmarks.
Registration pull request created: JuliaRegistries/General/115869
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.5.2 -m "<description of version>" de27b4c7783e929519360ed1897f8de24619aefe
git push origin v0.5.2
@JuliaRegistrator register()