Skip to content

Register #13

Closed
Closed
Register#13

Description

@ChrisRackauckas
ChrisRackauckas
opened on Jul 30, 2019

@JuliaRegistrator register()

Activity

  1. JuliaRegistrator commented on Jul 30, 2019

    @JuliaRegistrator
    JuliaRegistrator
    on Jul 30, 2019

    Registration pull request updated: JuliaRegistries/General/2368

    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>" 0f88f6f06cd60863e7feaa464aaeb29cfe016747
git push origin v1.1.0

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

  2. ChrisRackauckas
    closed this as completedon Jul 30, 2019

  3. ChrisRackauckas commented on Nov 15, 2019

    @ChrisRackauckas
    ChrisRackauckas
    on Nov 15, 2019
    MemberAuthor

    @JuliaRegistrator register()

  4. JuliaRegistrator commented on Nov 15, 2019

    @JuliaRegistrator
    JuliaRegistrator
    on Nov 15, 2019

    Registration pull request created: JuliaRegistries/General/5441

    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 v2.0.0 -m "<description of version>" 1fbc9836b09a6c893e259596055fa33018d903df
git push origin v2.0.0

  5. ChrisRackauckas commented on Nov 27, 2019

    @ChrisRackauckas
    ChrisRackauckas
    on Nov 27, 2019
    MemberAuthor

    @JuliaRegistrator register()

  6. JuliaRegistrator commented on Nov 27, 2019

    @JuliaRegistrator
    JuliaRegistrator
    on Nov 27, 2019

    Registration pull request updated: JuliaRegistries/General/5441

    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 v2.0.0 -m "<description of version>" c9622ad93c361ef7a86f0d2d461549797fc3abb3
git push origin v2.0.0

  7. ChrisRackauckas commented on Dec 12, 2019

    @ChrisRackauckas
    ChrisRackauckas
    on Dec 12, 2019
    MemberAuthor

    @JuliaRegistrator register()

  8. JuliaRegistrator commented on Dec 12, 2019

    @JuliaRegistrator
    JuliaRegistrator
    on Dec 12, 2019

    Registration pull request created: JuliaRegistries/General/6589

    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 v2.1.0 -m "<description of version>" 39356943a41db88aa3738bd407372499ba05349e
git push origin v2.1.0

  9. ChrisRackauckas commented on Dec 24, 2019

    @ChrisRackauckas
    ChrisRackauckas
    on Dec 24, 2019
    MemberAuthor

    @JuliaRegistrator register()

  10. JuliaRegistrator commented on Dec 24, 2019

    @JuliaRegistrator
    JuliaRegistrator
    on Dec 24, 2019

    Registration pull request created: JuliaRegistries/General/7113

    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 v2.2.0 -m "<description of version>" cceb14c8d0e63b460d962536b124b6b4a4829dda
git push origin v2.2.0

  11. ChrisRackauckas commented on Dec 27, 2019

    @ChrisRackauckas
    ChrisRackauckas
    on Dec 27, 2019
    MemberAuthor

    @JuliaRegistrator register()

  12. JuliaRegistrator commented on Dec 27, 2019

    @JuliaRegistrator
    JuliaRegistrator
    on Dec 27, 2019

    Registration pull request created: JuliaRegistries/General/7189

    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 v2.3.0 -m "<description of version>" eb25d87d975b45cd1aafd6fc2903b4887333ea1b
git push origin v2.3.0

  13. ChrisRackauckas commented on Dec 28, 2019

    @ChrisRackauckas
    ChrisRackauckas
    on Dec 28, 2019
    MemberAuthor

    @JuliaRegistrator register()

  14. JuliaRegistrator commented on Dec 28, 2019

    @JuliaRegistrator
    JuliaRegistrator
    on Dec 28, 2019

    Registration pull request created: JuliaRegistries/General/7235

    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 v2.3.1 -m "<description of version>" 072c037565aa19caef316affb2ee819e5fdf05e6
git push origin v2.3.1

  15. ChrisRackauckas commented on Feb 2, 2020

    @ChrisRackauckas
    ChrisRackauckas
    on Feb 2, 2020
    MemberAuthor

    @JuliaRegistrator register()

  16. 161 remaining items

  17. JuliaRegistrator commented on Jul 23, 2026

    @JuliaRegistrator
    JuliaRegistrator
    on Jul 23, 2026

    Registration pull request created: JuliaRegistries/General/162114

    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 v7.28.0 -m "<description of version>" 80e3539d27a16383ec614ddc0c0c59dd871cc2c6
git push origin v7.28.0

  18. ChrisRackauckas commented on Jul 24, 2026

    @ChrisRackauckas
    ChrisRackauckas
    on Jul 24, 2026
    MemberAuthor

    @JuliaRegistrator register()

  19. JuliaRegistrator commented on Jul 24, 2026

    @JuliaRegistrator
    JuliaRegistrator
    on Jul 24, 2026

    Registration pull request created: JuliaRegistries/General/162191

    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 v7.28.1 -m "<description of version>" d76728450a04afd5f41f1a21880f8ef767ab5657
git push origin v7.28.1

  20. ChrisRackauckas commented on Jul 24, 2026

    @ChrisRackauckas
    ChrisRackauckas
    on Jul 24, 2026
    MemberAuthor

    @JuliaRegistrator register()

  21. JuliaRegistrator commented on Jul 24, 2026

    @JuliaRegistrator
    JuliaRegistrator
    on Jul 24, 2026

    Registration pull request updated: JuliaRegistries/General/162191

    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 v7.28.1 -m "<description of version>" d76728450a04afd5f41f1a21880f8ef767ab5657
git push origin v7.28.1

  22. ChrisRackauckas commented on Jul 24, 2026

    @ChrisRackauckas
    ChrisRackauckas
    on Jul 24, 2026
    MemberAuthor

    @JuliaRegistrator register()

  23. JuliaRegistrator commented on Jul 24, 2026

    @JuliaRegistrator
    JuliaRegistrator
    on Jul 24, 2026

    Registration pull request updated: JuliaRegistries/General/162191

    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 v7.28.1 -m "<description of version>" d76728450a04afd5f41f1a21880f8ef767ab5657
git push origin v7.28.1

  24. ChrisRackauckas commented on Aug 1, 2026

    @ChrisRackauckas
    ChrisRackauckas
    on Aug 1, 2026
    MemberAuthor

    @JuliaRegistrator register()

  25. JuliaRegistrator commented on Aug 1, 2026

    @JuliaRegistrator
    JuliaRegistrator
    on Aug 1, 2026

    Error while trying to register: Version 7.28.1 already exists

  26. ChrisRackauckas commented on Aug 14, 2026

    @ChrisRackauckas
    ChrisRackauckas
    on Aug 14, 2026
    MemberAuthor

    @JuliaRegistrator register()

  27. JuliaRegistrator commented on Aug 14, 2026

    @JuliaRegistrator
    JuliaRegistrator
    on Aug 14, 2026

    Registration pull request created: JuliaRegistries/General/164512

    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 v7.29.0 -m "<description of version>" 6950d2a35ff47da3d2f39d1a544161948775d192
git push origin v7.29.0

  28. ChrisRackauckas commented on Aug 18, 2026

    @ChrisRackauckas
    ChrisRackauckas
    on Aug 18, 2026
    MemberAuthor

    @JuliaRegistrator register()

  29. JuliaRegistrator commented on Aug 18, 2026

    @JuliaRegistrator
    JuliaRegistrator
    on Aug 18, 2026

    Registration pull request created: JuliaRegistries/General/164820

    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 v7.30.0 -m "<description of version>" 995c24dc2b977f14758a2dcfeb4cd27109ad1e8d
git push origin v7.30.0

  30. ChrisRackauckas commented on Aug 30, 2026

    @ChrisRackauckas
    ChrisRackauckas
    on Aug 30, 2026
    MemberAuthor

    @JuliaRegistrator register()

  31. JuliaRegistrator commented on Aug 30, 2026

    @JuliaRegistrator
    JuliaRegistrator
    on Aug 30, 2026

    Registration pull request created: JuliaRegistries/General/166613

    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 v7.30.1 -m "<description of version>" 97b9fe8ec6d6e7afc530579a6daa90a4b9c7f49b
git push origin v7.30.1
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