Skip to content

Register #13

Closed
Closed

Description

@ChrisRackauckas

Activity

  1. JuliaRegistrator commented on Jun 27, 2024

    @JuliaRegistrator

    Registration pull request created: JuliaRegistries/General/109873

    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.1.3 -m "<description of version>" b93f8a785eafc4c9147b81687ed25d298b6093e2
    git push origin v0.1.3
    
  2. ChrisRackauckas commented on Oct 5, 2024

    @ChrisRackauckas
    MemberAuthor
  3. JuliaRegistrator commented on Oct 5, 2024

    @JuliaRegistrator

    Registration pull request created: JuliaRegistries/General/116661

    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.1.4 -m "<description of version>" b8573fa935587ea5b45d32c12543a1c54bde4ba5
    git push origin v0.1.4
    
  4. ChrisRackauckas commented on Apr 30, 2025

    @ChrisRackauckas
    MemberAuthor
  5. JuliaRegistrator commented on Apr 30, 2025

    @JuliaRegistrator

    Registration pull request created: JuliaRegistries/General/130093

    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.1.5 -m "<description of version>" 3fc55e9d30481a4fd5f47229d20fe57d6c4e01d0
    git push origin v0.1.5
    
  6. ChrisRackauckas commented on Jan 14, 2026

    @ChrisRackauckas
    MemberAuthor
  7. JuliaRegistrator commented on Jan 14, 2026

    @JuliaRegistrator

    Registration pull request created: JuliaRegistries/General/146103

    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.1.6 -m "<description of version>" dbe724c7b07dec1ba9eec735018b1f33226e3eee
    git push origin v0.1.6
    
  8. oscardssmith commented on Sep 21, 2026

    @oscardssmith
    Member
  9. JuliaRegistrator commented on Sep 21, 2026

    @JuliaRegistrator

    Registration pull request created: JuliaRegistries/General/169015

    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.1.13 -m "<description of version>" 9d7af0e1eef788e3cf07eb05fc3af4f379d807aa
    git push origin v0.1.13
    
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