Open ufechner7 opened 2 years ago
Registration pull request created: JuliaRegistries/General/59309
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>" e5999400f03fae7f78c6b7a9971fcbf534d4c0d2
git push origin v0.1.0
@JuliaRegistrator register
Registration pull request created: JuliaRegistries/General/61727
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>" d47cdd371a8137605e7c5f5744d2fbe930ae5d7d
git push origin v0.1.1
@JuliaRegistrator register
Registration pull request updated: JuliaRegistries/General/61727
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>" 8729dd895b1e36e427efa92df64509fa547f0797
git push origin v0.1.1
@JuliaRegistrator register
Registration pull request updated: JuliaRegistries/General/61727
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>" 51b1bf3303aac490cc8e0d2a97764c7b399fdb11
git push origin v0.1.1
@JuliaRegistrator register
Registration pull request created: JuliaRegistries/General/62123
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>" 6f36e4c48b18a881ca3b0cbfbba6c2ac42e214a1
git push origin v0.1.2
@JuliaRegistrator register
Registration pull request updated: JuliaRegistries/General/62123
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>" c728e5a4790bab639c4e9cafe756ea626f342661
git push origin v0.1.2
@JuliaRegistrator register
Registration pull request updated: JuliaRegistries/General/62123
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>" 599a46dd728ac3e03a4b6b3e30eaf050dfc2edd6
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/62208
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>" 26e8b5f8db8907da40e56a36294de44c11f5c9d9
git push origin v0.1.3
@JuliaRegistrator register
Registration pull request created: JuliaRegistries/General/62640
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>" b48e92f96e065dd0e8fe5bb5df234153513cf84f
git push origin v0.1.4
@JuliaRegistrator register
Registration pull request created: JuliaRegistries/General/62978
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>" d9dd6102593d94334e93e6ba910d322d25e86112
git push origin v0.1.5
@JuliaRegistrator register
Registration pull request created: JuliaRegistries/General/63111
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>" 83767b5f7e4b95297ffe317dcf6409ca4b81748d
git push origin v0.1.6
@JuliaRegistrator register
Registration pull request created: JuliaRegistries/General/63561
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>" 908f4d8d10768579e80d6157107bf4215195c51d
git push origin v0.1.7
@JuliaRegistrator register
Registration pull request created: JuliaRegistries/General/103055
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>" 48972773029cce00e925ce6a93e8024b5b73fbeb
git push origin v0.2.0
@JuliaRegistrator register
Error while trying to register: Version 0.2.0 already exists
@JuliaRegistrator register
Registration pull request created: JuliaRegistries/General/103864
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>" 5ecb7747acceb2a1388586fb0ecc8342ca6d1700
git push origin v0.2.1
@JuliaRegistrator register
Release notes:
autopilot.jl
was vastly improvedError while trying to register: Version 0.2.1 already exists
@JuliaRegistrator register
Release notes:
autopilot.jl
was vastly improvedRegistration pull request created: JuliaRegistries/General/104155
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>" 2f52ab997f6f9911a8fa97558475dc58f0c75397
git push origin v0.2.2
Registration pull request updated: JuliaRegistries/General/104155
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>" 2f52ab997f6f9911a8fa97558475dc58f0c75397
git push origin v0.2.2
@JuliaRegistrator register
Release notes:
flightpathplanner.jl
in flightpathplanner.jl
and flightpathcalculator.jl
flightpathplanner2.jl
and flightpathcalculator2.jl
;t_sim
using the GUIplot_elev_az2
and plot_side_view2
that omit the first power cycleplot_elev_az3
, plot_side_view3
and plot_front_view3
that omit the first two power cyclesaerodynamics
that plots the lift-over-drag of the kitefig8
to plot_control
kiteobservers.jl
which provides the type KiteObserver
and methods to
determine deviations from the desired flight pathlearning.jl
that provides the method train()
that implements iterative learning
of a vector of flight path corrections Registration pull request created: JuliaRegistries/General/106262
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.3 -m "<description of version>" 8e16738aa9335d238a2c6950e3354bbc8363fd96
git push origin v0.2.3
@JuliaRegistrator register
Registration pull request updated: JuliaRegistries/General/106262
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.3 -m "<description of version>" 06bb1c07c5e019b0abfaba3e55d74b48ceb9c2cc
git push origin v0.2.3
@JuliaRegistrator register
Release notes:
corr_vec
to all fpp_settings_xxx.yaml
fileskiteobserver.jl
to use this correction vectorhydra10_951
and hydra20_600
hydra20_920
work correctly now; key change: set k_c2_high to 6.0Registration pull request created: JuliaRegistries/General/109281
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.4 -m "<description of version>" ad68d98043cc3335a18b9351556be939c8451b3c
git push origin v0.2.4
@JuliaRegistrator register
Release notes:
Registration pull request created: JuliaRegistries/General/109815
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.5 -m "<description of version>" 31cb82bfb9c92626879ee8c380a70975d1ca406e
git push origin v0.2.5
@JuliaRegistrator register
Release notes:
Registration pull request created: JuliaRegistries/General/110197
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.6 -m "<description of version>" ecc38376acd926c0f27d88778b7703a3e400503d
git push origin v0.2.6
@JuliaRegistrator register
Release notes:
Registration pull request created: JuliaRegistries/General/110964
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.7 -m "<description of version>" edb9b6af486393afb56a021af03eaea56dc59f7c
git push origin v0.2.7
@JuliaRegistrator register
Release notes:
Registration pull request created: JuliaRegistries/General/111934
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.8 -m "<description of version>" 8a1e1de78c43131f777fd9bb5dc7d9e2bbc0bb45
git push origin v0.2.8
@JuliaRegistrator register