Skip to content

Register #6

Closed
Closed

Description

@ChrisRackauckas

Activity

  1. JuliaRegistrator commented on Jul 5, 2019

    @JuliaRegistrator

    Registration pull request created: JuliaRegistries/General/1812

    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 Julia TagBot is installed, or can be done manually through the github interface, or via:

    git tag -a v0.1.0 -m "<description of version>" 86fbbee04fb5a9d3ff3962aedcec1485661e7539
    git push origin v0.1.0
    
  2. ChrisRackauckas commented on Sep 24, 2019

    @ChrisRackauckas
    MemberAuthor
  3. JuliaRegistrator commented on Sep 24, 2019

    @JuliaRegistrator

    Registration pull request created: JuliaRegistries/General/3788

    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 Julia TagBot is installed, or can be done manually through the github interface, or via:

    git tag -a v0.2.0 -m "<description of version>" 8e9c51f025227f853dbfd91046740a994dab4d2c
    git push origin v0.2.0
    
  4. ChrisRackauckas commented on Oct 11, 2019

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

    @JuliaRegistrator

    Registration pull request created: JuliaRegistries/General/4273

    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 Julia TagBot is installed, or can be done manually through the github interface, or via:

    git tag -a v0.3.0 -m "<description of version>" 659024663d9ce7cec830e9e30b8449619971c8b7
    git push origin v0.3.0
    
  6. ChrisRackauckas commented on Nov 27, 2019

    @ChrisRackauckas
    MemberAuthor
  7. JuliaRegistrator commented on Nov 27, 2019

    @JuliaRegistrator

    Registration pull request created: JuliaRegistries/General/5933

    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 Julia TagBot is installed, or can be done manually through the github interface, or via:

    git tag -a v1.0.0 -m "<description of version>" 24545607fd0786152a4f912c8219ed00f688581d
    git push origin v1.0.0
    
  8. ChrisRackauckas commented on Dec 2, 2019

    @ChrisRackauckas
    MemberAuthor
  9. JuliaRegistrator commented on Dec 2, 2019

    @JuliaRegistrator

    Registration pull request created: JuliaRegistries/General/6148

    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 Julia TagBot is installed, or can be done manually through the github interface, or via:

    git tag -a v1.1.0 -m "<description of version>" 22b66915b7d7e22f94a2a5ffac0770aa126c4c70
    git push origin v1.1.0
    
  10. ChrisRackauckas commented on Dec 18, 2019

    @ChrisRackauckas
    MemberAuthor
  11. JuliaRegistrator commented on Dec 18, 2019

    @JuliaRegistrator

    Registration pull request created: JuliaRegistries/General/6863

    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 Julia TagBot is installed, or can be done manually through the github interface, or via:

    git tag -a v1.2.0 -m "<description of version>" 401b2e1176ae310916ad97b761ee12618904f8e5
    git push origin v1.2.0
    
  12. ChrisRackauckas commented on Dec 18, 2019

    @ChrisRackauckas
    MemberAuthor
  13. JuliaRegistrator commented on Dec 18, 2019

    @JuliaRegistrator

    Registration pull request created: JuliaRegistries/General/6870

    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 Julia TagBot is installed, or can be done manually through the github interface, or via:

    git tag -a v1.2.1 -m "<description of version>" fb560dffbc1c1ef80d712106315ec8dd502b438f
    git push origin v1.2.1
    
  14. ChrisRackauckas commented on Mar 26, 2020

    @ChrisRackauckas
    MemberAuthor
  15. 84 remaining items

  16. JuliaRegistrator commented on Jul 31, 2025

    @JuliaRegistrator

    Registration pull request updated: JuliaRegistries/General/135685

    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 v3.8.0 -m "<description of version>" a29a8d26d149b38ab8caad2b594cf31a10529959
    git push origin v3.8.0
    
  17. ChrisRackauckas commented on Nov 3, 2025

    @ChrisRackauckas
    MemberAuthor
  18. JuliaRegistrator commented on Nov 3, 2025

    @JuliaRegistrator

    Registration pull request created: JuliaRegistries/General/141729

    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 v3.9.0 -m "<description of version>" c8041bbdb690f52938a95c5917cc6f034b950535
    git push origin v3.9.0
    
  19. ChrisRackauckas commented on Feb 20, 2026

    @ChrisRackauckas
    MemberAuthor
  20. JuliaRegistrator commented on Feb 20, 2026

    @JuliaRegistrator

    Registration pull request created: JuliaRegistries/General/148789

    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 v3.10.0 -m "<description of version>" b11ad1deb0f5b3d8f5d2cc69296309648249ac2e
    git push origin v3.10.0
    
  21. ChrisRackauckas commented on Feb 21, 2026

    @ChrisRackauckas
    MemberAuthor
  22. JuliaRegistrator commented on Feb 21, 2026

    @JuliaRegistrator

    Registration pull request created: JuliaRegistries/General/148880

    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 v3.11.0 -m "<description of version>" 2c856019a8ecb1cb9fe6e18a682d19d37ab7e2ef
    git push origin v3.11.0
    
  23. ChrisRackauckas commented on Feb 23, 2026

    @ChrisRackauckas
    MemberAuthor
  24. JuliaRegistrator commented on Feb 23, 2026

    @JuliaRegistrator

    Registration pull request created: JuliaRegistries/General/149042

    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 v3.12.0 -m "<description of version>" 5f881d7a043c588227140326151e79dc5fd48fcb
    git push origin v3.12.0
    
  25. ChrisRackauckas commented on Apr 6, 2026

    @ChrisRackauckas
    MemberAuthor
  26. JuliaRegistrator commented on Apr 6, 2026

    @JuliaRegistrator

    Registration pull request created: JuliaRegistries/General/152222

    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 v3.13.0 -m "<description of version>" 0af6962f758dc8da439e72139a86744c31b9ffca
    git push origin v3.13.0
    
  27. ChrisRackauckas commented on Apr 30, 2026

    @ChrisRackauckas
    MemberAuthor
  28. JuliaRegistrator commented on Apr 30, 2026

    @JuliaRegistrator

    Registration pull request created: JuliaRegistries/General/154405

    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 v3.14.0 -m "<description of version>" eb7669beb75449090a8bcbc38fa112624003484b
    git push origin v3.14.0
    
  29. ChrisRackauckas commented on May 9, 2026

    @ChrisRackauckas
    MemberAuthor
  30. JuliaRegistrator commented on May 9, 2026

    @JuliaRegistrator

    Registration pull request created: JuliaRegistries/General/155086

    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 v3.15.0 -m "<description of version>" 81ca01725b806d677d4ec6d10d0cca00fc9b6955
    git push origin v3.15.0
    
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