Open ufechner7 opened 2 years ago
@JuliaRegistrator register
Registration pull request created: JuliaRegistries/General/102620
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.5.0 -m "<description of version>" 7f8c09afc72e6ede0475e03f8702cc9c19ab270f
git push origin v0.5.0
@JuliaRegistrator register
Registration pull request created: JuliaRegistries/General/102628
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.5.1 -m "<description of version>" a73a1423b22788f547bc73f25fc077c519fcd82e
git push origin v0.5.1
@JuliaRegistrator register
Registration pull request created: JuliaRegistries/General/102762
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.5.2 -m "<description of version>" 78d7d6aaaa0dfd1334bbaa80f7c9a18bb4a7686b
git push origin v0.5.2
@JuliaRegistrator register
Registration pull request created: JuliaRegistries/General/103000
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.5.3 -m "<description of version>" d20e11db78b4ba12b88b723030ebf2494122d14d
git push origin v0.5.3
@JuliaRegistrator register
Error while trying to register: Version 0.5.3 already exists
@JuliaRegistrator register
Registration pull request created: JuliaRegistries/General/103585
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.5.4 -m "<description of version>" f370cb18b426eee22fc0b91f9a8fe98353d8ebf4
git push origin v0.5.4
@JuliaRegistrator register
Registration pull request created: JuliaRegistries/General/103728
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.5.5 -m "<description of version>" 2da3f433001d6a088fb4ec4934e0040fa6de2eb9
git push origin v0.5.5
@JuliaRegistrator register
Release notes:
Registration pull request created: JuliaRegistries/General/103911
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.6 -m "<description of version>" 4f5e4d0b5c886730aa8a671c8ca3fcc776945496
git push origin v0.5.6
@JuliaRegistrator register
Release notes:
Registration pull request created: JuliaRegistries/General/103977
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.7 -m "<description of version>" 460aa10c954dfb51548729445044361134ea7af0
git push origin v0.5.7
@JuliaRegistrator register
Release notes:
Registration pull request created: JuliaRegistries/General/103998
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.8 -m "<description of version>" 1e55a41f83a0c66770896628fc83ad3f5296fb10
git push origin v0.5.8
@JuliaRegistrator register
Registration pull request created: JuliaRegistries/General/104003
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.5.9 -m "<description of version>" 2c37bdc1c4a8776a6e0b1cfc773ac4d6e050e05a
git push origin v0.5.9
@JuliaRegistrator register
Release notes:
This requires to add the following line to the settings.yaml file: solver: "DFBDF"
The new solver is much faster, has a lot less memory allocations and is also much more stable in difficult situations.
Registration pull request created: JuliaRegistries/General/104142
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.5.10 -m "<description of version>" 2973a89f59972fad436eb1c95ddec396be8f0568
git push origin v0.5.10
Registration pull request updated: JuliaRegistries/General/104142
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.10 -m "<description of version>" 2973a89f59972fad436eb1c95ddec396be8f0568
git push origin v0.5.10
@JuliaRegistrator register
Release notes:
DImplicitEuler
solver, which is not very accurate,
but because it is well known it can serve as referencemax_order
for the DFBDF
Registration pull request created: JuliaRegistries/General/104255
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.11 -m "<description of version>" 17bf0433a716c768166d536800b51048b393852e
git push origin v0.5.11
@JuliaRegistrator register
Release notes:
KPS4_3L
, which is now only a copy of KPS4
, but shall implement a kite with the steering
lines going to the groundRegistration pull request created: JuliaRegistries/General/104884
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.5.12 -m "<description of version>" 8b28dfb4c61070c12d68420ca3126b515575da87
git push origin v0.5.12
Registration pull request updated: JuliaRegistries/General/104884
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.12 -m "<description of version>" 8b28dfb4c61070c12d68420ca3126b515575da87
git push origin v0.5.12
@JuliaRegistrator register
Release notes:
rel_compr_stiffness
and rel_damping
from settings.yaml Registration pull request created: JuliaRegistries/General/105320
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.13 -m "<description of version>" 6387dbff854aebf04ef6c85fbeaad28113a6fd21
git push origin v0.5.13
@JuliaRegistrator register
Release notes:
Registration pull request created: JuliaRegistries/General/106213
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.14 -m "<description of version>" ea832486caf738e5961d0f785b35ba9923fefeb1
git push origin v0.5.14
@JuliaRegistrator register
Release notes:
Registration pull request created: JuliaRegistries/General/109240
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.15 -m "<description of version>" 0e30d24417661f7e3ca338bd04ad274e8e7d8477
git push origin v0.5.15
@JuliaRegistrator register
Release notes:
Registration pull request created: JuliaRegistries/General/109743
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.16 -m "<description of version>" b2f2859214f7c2911ee0c86ef6fdf994a854b5cf
git push origin v0.5.16
@JuliaRegistrator register