Open ufechner7 opened 2 years ago
Registration pull request updated: JuliaRegistries/General/103218
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>" c60c62210fee64421608444813b5a7dd3a961a85
git push origin v0.5.3
@JuliaRegistrator register()
Registration pull request created: JuliaRegistries/General/103567
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.6.0 -m "<description of version>" 0d53fc7e8b55a9cd0a9b2568f1a59450def658f3
git push origin v0.6.0
@JuliaRegistrator register()
Registration pull request created: JuliaRegistries/General/103640
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.6.1 -m "<description of version>" d2fe9ce0c345fc1a84a3aa702be91739940839fb
git push origin v0.6.1
@JuliaRegistrator register()
Registration pull request created: JuliaRegistries/General/103645
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.6.2 -m "<description of version>" 0b6f4fcc3c7738f90e1614d993ad221de27b9e87
git push origin v0.6.2
@JuliaRegistrator register()
Registration pull request created: JuliaRegistries/General/103717
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.6.3 -m "<description of version>" 587330f2ec232cb2adf827822513d30db3860a42
git push origin v0.6.3
@JuliaRegistrator register()
Registration pull request created: JuliaRegistries/General/103856
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.6.4 -m "<description of version>" 832bcaed9602d41f74614c5318649ec08e1921a5
git push origin v0.6.4
@JuliaRegistrator register()
Release notes:
Registration pull request created: JuliaRegistries/General/104130
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.6.5 -m "<description of version>" 44250c63408bffd67abe4b5bc87641523abc1c72
git push origin v0.6.5
@JuliaRegistrator register()
Release notes:
log_level
to settings.yaml
and Settings structRegistration pull request created: JuliaRegistries/General/104292
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.6.6 -m "<description of version>" 3090aafa0f1e0c1ccc6fcbfd12c11064a5b4374a
git push origin v0.6.6
@JuliaRegistrator register()
Release notes:
Registration pull request created: JuliaRegistries/General/104875
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.6.7 -m "<description of version>" 9eb142b3e4a4403642c219a14ed46379c04bfa87
git push origin v0.6.7
Registration pull request updated: JuliaRegistries/General/104875
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.6.7 -m "<description of version>" 9eb142b3e4a4403642c219a14ed46379c04bfa87
git push origin v0.6.7
@JuliaRegistrator register()
Release notes:
systems.yaml
file as parameterproject
in systems.yaml
was replaced with the key sim_settings
wc_settings
was added to systems.yaml
Registration pull request created: JuliaRegistries/General/105008
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.6.8 -m "<description of version>" 2d14be5c7d23806c9e53dbeccb4b1d8ea7062c62
git push origin v0.6.8
@JuliaRegistrator register()
Release notes:
Registration pull request created: JuliaRegistries/General/105023
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.6.9 -m "<description of version>" 32cbcc8700d5da2104077e2b4de9810c919ada41
git push origin v0.6.9
@JuliaRegistrator register()
Release notes:
rel_compr_stiffness
and rel_damping
in settings.yaml load_log
and save_log
have the new, optional, named parameter path
to specify the file path;
if not specified, the default data path is used.Registration pull request created: JuliaRegistries/General/105318
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.6.11 -m "<description of version>" 039ee909c5ec271d08d3ceb3fdc79da33736ade6
git push origin v0.6.11
Also, note the warning: Version 0.6.11 skips over 0.6.10 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.
Registration pull request updated: JuliaRegistries/General/105318
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.6.11 -m "<description of version>" 039ee909c5ec271d08d3ceb3fdc79da33736ade6
git push origin v0.6.11
Also, note the warning: Version 0.6.11 skips over 0.6.10 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:
rel_compr_stiffness
and rel_damping
in settings.yaml load_log
and save_log
have the new, optional, named parameter path
to specify the file path;
if not specified, the default data path is used.Registration pull request created: JuliaRegistries/General/105319
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.6.10 -m "<description of version>" f57da156cfaae7d71f76a76bfaffe78fc7f656a6
git push origin v0.6.10
Registration pull request updated: JuliaRegistries/General/105319
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.6.10 -m "<description of version>" f57da156cfaae7d71f76a76bfaffe78fc7f656a6
git push origin v0.6.10
Registration pull request updated: JuliaRegistries/General/105319
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.6.10 -m "<description of version>" f57da156cfaae7d71f76a76bfaffe78fc7f656a6
git push origin v0.6.10
@JuliaRegistrator register()
Release notes:
export_log()
support now the named parameter path
to specify the directory
load_log()
works now when a fully qualified filename is passed Registration pull request updated: JuliaRegistries/General/105318
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.6.11 -m "<description of version>" 113d0b9f822bcdd6c16fafb95ada887bd1e21acc
git push origin v0.6.11
@JuliaRegistrator register()
Release notes:
Registration pull request created: JuliaRegistries/General/109236
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.6.12 -m "<description of version>" 325036d357cca4dd5157a1505fb544f411b1a1d8
git push origin v0.6.12
@JuliaRegistrator register()
Release notes:
Registration pull request created: JuliaRegistries/General/109351
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.6.13 -m "<description of version>" 29856767306b459f3344205bfe33edd2dbeef0c0
git push origin v0.6.13
@JuliaRegistrator register()
Release notes:
path
Registration pull request created: JuliaRegistries/General/109437
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.6.14 -m "<description of version>" f5a24c69f1365632a3343064111119170a9d77fa
git push origin v0.6.14
@JuliaRegistrator register()
Release notes:
Registration pull request created: JuliaRegistries/General/109521
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.6.15 -m "<description of version>" 19f693ca2227d44a80830735481f481697c112e9
git push origin v0.6.15
@JuliaRegistrator register()
Release notes:
width_3l
Registration pull request created: JuliaRegistries/General/109724
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.6.16 -m "<description of version>" bdd2b3a020f6afabb5e75bdd93fde642beed50f5
git push origin v0.6.16
@JuliaRegistrator register()
Release notes:
winch_model
, drum_radius
, gear_ratio
, inertia_motor
kps4_3l
is missingRegistration pull request created: JuliaRegistries/General/111669
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.7.1 -m "<description of version>" ff79edc911c22901de3049c9f0834264399fd6a9
git push origin v0.7.1
Also, note the warning: Version 0.7.1 skips over 0.7.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:
winch_model
, drum_radius
, gear_ratio
, inertia_motor
kps4_3l
is missingRegistration pull request created: JuliaRegistries/General/111672
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.7.0 -m "<description of version>" 3816c76c074d958ddfd28db48b06a9460b5b8773
git push origin v0.7.0
@JuliaRegistrator register()
Release notes:
f_coulomb
and c_vf
for the friction of the winchError while trying to register: Version 0.7.0 already exists
@JuliaRegistrator register()
Release notes:
f_coulomb
and c_vf
for the friction of the winchRegistration pull request updated: JuliaRegistries/General/111669
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.7.1 -m "<description of version>" 054a9b5133116b578a198064b782c1f91fe238fa
git push origin v0.7.1
@JuliaRegistrator register()
Release notes:
@JuliaRegistrator register()