Skip to content

Register #2

Closed
Closed

Description

@ChrisRackauckas

Activity

  1. JuliaRegistrator commented on Sep 4, 2020

    @JuliaRegistrator

    Registration pull request created: JuliaRegistries/General/20817

    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>" 4ee2192da1d173d11eb2f719aea4b4e043c3073b
    git push origin v0.1.0
    
  2. ChrisRackauckas commented on Sep 11, 2020

    @ChrisRackauckas
    MemberAuthor
  3. JuliaRegistrator commented on Sep 11, 2020

    @JuliaRegistrator

    Registration pull request created: JuliaRegistries/General/21215

    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>" e51174fcd117b59b45af25021fdf6c88a9ce406a
    git push origin v0.2.0
    
  4. ChrisRackauckas commented on Sep 14, 2020

    @ChrisRackauckas
    MemberAuthor
  5. JuliaRegistrator commented on Sep 14, 2020

    @JuliaRegistrator

    Registration pull request created: JuliaRegistries/General/21346

    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.3.0 -m "<description of version>" ac079dd7053cb4704b788e4ec18980ec212e40bd
    git push origin v0.3.0
    
  6. ChrisRackauckas commented on Sep 15, 2020

    @ChrisRackauckas
    MemberAuthor
  7. JuliaRegistrator commented on Sep 15, 2020

    @JuliaRegistrator

    Registration pull request created: JuliaRegistries/General/21401

    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.3.1 -m "<description of version>" 77a26378d0cfd9ca8baa8b891db784a436abcd81
    git push origin v0.3.1
    
  8. ChrisRackauckas commented on Sep 15, 2020

    @ChrisRackauckas
    MemberAuthor
  9. JuliaRegistrator commented on Sep 15, 2020

    @JuliaRegistrator

    Registration pull request created: JuliaRegistries/General/21410

    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.3.2 -m "<description of version>" bbfaf6020886cba415387c3554363d48db1aa4a7
    git push origin v0.3.2
    
  10. ChrisRackauckas commented on Oct 5, 2020

    @ChrisRackauckas
    MemberAuthor
  11. JuliaRegistrator commented on Oct 5, 2020

    @JuliaRegistrator

    Registration pull request created: JuliaRegistries/General/22414

    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.0 -m "<description of version>" c4801a62eb416bd194c3ff349f98e84d67132195
    git push origin v0.4.0
    
  12. ChrisRackauckas commented on Oct 23, 2020

    @ChrisRackauckas
    MemberAuthor
  13. JuliaRegistrator commented on Oct 23, 2020

    @JuliaRegistrator

    Registration pull request created: JuliaRegistries/General/23547

    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>" 2a3f7345b926a26121a7d45b4158a691faa307af
    git push origin v0.4.1
    
  14. ChrisRackauckas commented on Jan 4, 2021

    @ChrisRackauckas
    MemberAuthor
  15. 32 remaining items

  16. JuliaRegistrator commented on Apr 8, 2026

    @JuliaRegistrator

    Registration pull request created: JuliaRegistries/General/152423

    Recommendation: add release notes

    Release notes help your users know what has changed in the new version. For breaking releases in particular, it's recommended to document what breaking changes were made (or point to where changes can be found, such as a changelog).

    To add release notes, 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 release notes to this registration, just re-invoke JuliaRegistrator 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.5.18 -m "<description of version>" fc434d7c70a81f2c0a42f999d9db06c876b64fdb
    git push origin v0.5.18
    
  17. ChrisRackauckas commented on May 20, 2026

    @ChrisRackauckas
    MemberAuthor
  18. JuliaRegistrator commented on May 20, 2026

    @JuliaRegistrator

    Registration pull request created: JuliaRegistries/General/155899

    Recommendation: add release notes

    Release notes help your users know what has changed in the new version. For breaking releases in particular, it's recommended to document what breaking changes were made (or point to where changes can be found, such as a changelog).

    To add release notes, 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 release notes to this registration, just re-invoke JuliaRegistrator 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.5.19 -m "<description of version>" 7875fe3d8fb0d58e0a3493e845fc190e510a3bf6
    git push origin v0.5.19
    
  19. ChrisRackauckas commented on Jun 26, 2026

    @ChrisRackauckas
    MemberAuthor
  20. JuliaRegistrator commented on Jun 26, 2026

    @JuliaRegistrator

    Registration pull request created: JuliaRegistries/General/159204

    Recommendation: add release notes

    Release notes help your users know what has changed in the new version. For breaking releases in particular, it's recommended to document what breaking changes were made (or point to where changes can be found, such as a changelog).

    To add release notes, 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 release notes to this registration, just re-invoke JuliaRegistrator 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.5.22 -m "<description of version>" 2673ba1c9936076e71f477fa5a7c60c6125e7817
    git push origin v0.5.22
    

    Also, note the warning: Version 0.5.22 skips over 0.5.21
    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.

  21. ChrisRackauckas commented on Jun 26, 2026

    @ChrisRackauckas
    MemberAuthor
  22. JuliaRegistrator commented on Jun 26, 2026

    @JuliaRegistrator

    Registration pull request created: JuliaRegistries/General/159209

    Recommendation: add release notes

    Release notes help your users know what has changed in the new version. For breaking releases in particular, it's recommended to document what breaking changes were made (or point to where changes can be found, such as a changelog).

    To add release notes, 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 release notes to this registration, just re-invoke JuliaRegistrator 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.5.21 -m "<description of version>" 217cdf0c01a73a2077750c243338a9100cc8d530
    git push origin v0.5.21
    
  23. ChrisRackauckas commented on Aug 3, 2026

    @ChrisRackauckas
    MemberAuthor
  24. JuliaRegistrator commented on Aug 3, 2026

    @JuliaRegistrator

    Error while trying to register: Version 0.5.23 already exists

  25. ChrisRackauckas commented on Aug 3, 2026

    @ChrisRackauckas
    MemberAuthor
  26. JuliaRegistrator commented on Aug 3, 2026

    @JuliaRegistrator

    Registration pull request created: JuliaRegistries/General/163232

    Recommendation: add release notes

    Release notes help your users know what has changed in the new version. For breaking releases in particular, it's recommended to document what breaking changes were made (or point to where changes can be found, such as a changelog).

    To add release notes, 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 release notes to this registration, just re-invoke JuliaRegistrator 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.5.24 -m "<description of version>" d7fdff8d643ac814f6173bcece311e31140c7b11
    git push origin v0.5.24
    
  27. ChrisRackauckas commented on Aug 23, 2026

    @ChrisRackauckas
    MemberAuthor
  28. JuliaRegistrator commented on Aug 23, 2026

    @JuliaRegistrator

    Registration pull request created: JuliaRegistries/General/165475

    Recommendation: add release notes

    Release notes help your users know what has changed in the new version. For breaking releases in particular, it's recommended to document what breaking changes were made (or point to where changes can be found, such as a changelog).

    To add release notes, 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 release notes to this registration, just re-invoke JuliaRegistrator 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.5.26 -m "<description of version>" e3a7e8010887a48d8828c545c4127ada1a16be30
    git push origin v0.5.26
    

    Also, note the warning: Version 0.5.26 skips over 0.5.25
    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.

  29. ChrisRackauckas commented on Aug 23, 2026

    @ChrisRackauckas
    MemberAuthor
  30. JuliaRegistrator commented on Aug 23, 2026

    @JuliaRegistrator

    Registration pull request created: JuliaRegistries/General/165476

    Recommendation: add release notes

    Release notes help your users know what has changed in the new version. For breaking releases in particular, it's recommended to document what breaking changes were made (or point to where changes can be found, such as a changelog).

    To add release notes, 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 release notes to this registration, just re-invoke JuliaRegistrator 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.5.25 -m "<description of version>" a1367415d319611c645eb4b1752662b89e88b497
    git push origin v0.5.25
    
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions