search

control-toolbox / CTFlows.jl

Flows: classical, Hamiltonian, from OCP and more
MIT License
0 stars 1 forks source link

Go to general registry 🤞 #27

Closed ocots closed 6 days ago

ocots commented 1 week ago
ocots commented 1 week ago

@JuliaRegistrator register()

JuliaRegistrator commented 1 week ago

Error while trying to register: Error in (Julia)Project.toml: Package 'CTBase' with UUID: 54762871-cc72-4466-b8e8-f6c8b58076cd not found in registry or stdlib

ocots commented 1 week ago

Checkout @PierreMartinon @jbcaillau

JuliaRegistrator commented 1 week ago

Registration pull request created: JuliaRegistries/General/110818

Tip: Release Notes

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.

Tagging

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>" 072356af88a52ff9f4210793cdb703563b4448a2
git push origin v0.4.5

Also, note the warning: This looks like a new registration that registers version 0.4.5. 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 commented 1 week ago

Registration pull request updated: JuliaRegistries/General/110818

Tip: Release Notes

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.

Tagging

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>" 6534a9100043fd32a7c81dc7382e2b18c64e9833
git push origin v0.4.5

Also, note the warning: This looks like a new registration that registers version 0.4.5. 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.