Skip to content

Register #21

Closed
Closed

Description

@ChrisRackauckas

Activity

  1. JuliaRegistrator commented on May 13, 2022

    @JuliaRegistrator

    Error while trying to register: "Tag with name v1.1.5 already exists and points to a different commit"

  2. ChrisRackauckas commented on May 13, 2022

    @ChrisRackauckas
    MemberAuthor
  3. JuliaRegistrator commented on May 13, 2022

    @JuliaRegistrator

    Registration pull request created: JuliaRegistries/General/60191

    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 v1.2.0 -m "<description of version>" 0546ddbdd4443ffc1662523b5df2f10c71833197
    git push origin v1.2.0
    

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

  4. ChrisRackauckas commented on May 13, 2022

    @ChrisRackauckas
    MemberAuthor
  5. JuliaRegistrator commented on May 13, 2022

    @JuliaRegistrator

    Registration pull request updated: JuliaRegistries/General/60191

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

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

  6. ChrisRackauckas commented on Jul 20, 2022

    @ChrisRackauckas
    MemberAuthor
  7. JuliaRegistrator commented on Jul 20, 2022

    @JuliaRegistrator

    Registration pull request created: JuliaRegistries/General/64646

    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 v1.2.1 -m "<description of version>" 0cdae4072acd9974cd04c05d6b4fb68adb1c884a
    git push origin v1.2.1
    
  8. ChrisRackauckas commented on Jul 20, 2022

    @ChrisRackauckas
    MemberAuthor
  9. JuliaRegistrator commented on Jul 20, 2022

    @JuliaRegistrator

    Error while trying to register: "Tag with name v1.2.1 already exists and points to a different commit"

  10. ChrisRackauckas commented on Jul 20, 2022

    @ChrisRackauckas
    MemberAuthor
  11. JuliaRegistrator commented on Jul 20, 2022

    @JuliaRegistrator

    Registration pull request updated: JuliaRegistries/General/64646

    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 v1.2.1 -m "<description of version>" 9944785b58a558276fbda0d933034afd8ae4d306
    git push origin v1.2.1
    
  12. ChrisRackauckas commented on Jul 20, 2022

    @ChrisRackauckas
    MemberAuthor
  13. JuliaRegistrator commented on Jul 20, 2022

    @JuliaRegistrator

    Registration pull request updated: JuliaRegistries/General/64646

    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 v1.2.1 -m "<description of version>" 919bffcda972c702525b3ebd327ec702cda5fe36
    git push origin v1.2.1
    
  14. ChrisRackauckas commented on Jul 20, 2022

    @ChrisRackauckas
    MemberAuthor
  15. JuliaRegistrator commented on Jul 20, 2022

    @JuliaRegistrator

    Registration pull request updated: JuliaRegistries/General/64646

    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 v1.2.1 -m "<description of version>" 275cde924039c9fdbd1f04651025c349599213d5
    git push origin v1.2.1
    
  16. ChrisRackauckas commented on Jul 11, 2024

    @ChrisRackauckas
    MemberAuthor
  17. JuliaRegistrator commented on Jul 11, 2024

    @JuliaRegistrator

    Registration pull request created: JuliaRegistries/General/110848

    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 v2.0.0 -m "<description of version>" 19fb9c754680a1c3baedd9576ced3fe2bc99b3b5
    git push origin v2.0.0
    
  18. ChrisRackauckas commented on Feb 20, 2026

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

    @JuliaRegistrator

    Registration pull request created: JuliaRegistries/General/148834

    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 v2.2.0 -m "<description of version>" 5040563ce0a0412e0ec1559ce65106dae23d446c
    git push origin v2.2.0
    
  20. ChrisRackauckas commented on Apr 13, 2026

    @ChrisRackauckas
    MemberAuthor
  21. JuliaRegistrator commented on Apr 13, 2026

    @JuliaRegistrator

    Registration pull request created: JuliaRegistries/General/152876

    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 v2.3.0 -m "<description of version>" b8033711906b4be37b86f5963e3883d72611cea5
    git push origin v2.3.0
    
  22. ChrisRackauckas commented on Apr 14, 2026

    @ChrisRackauckas
    MemberAuthor
  23. JuliaRegistrator commented on Apr 14, 2026

    @JuliaRegistrator

    Registration pull request created: JuliaRegistries/General/152931

    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 v2.4.0 -m "<description of version>" 6fc04330d4abcb5d4985ab60c1db0cdffc204565
    git push origin v2.4.0
    
  24. ChrisRackauckas commented on May 6, 2026

    @ChrisRackauckas
    MemberAuthor
  25. JuliaRegistrator commented on May 6, 2026

    @JuliaRegistrator

    Registration pull request created: JuliaRegistries/General/154807

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

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

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