Skip to content

Register package #1

Closed
Closed
Register package#1

Description

@terasakisatoshi
terasakisatoshi
opened on May 18, 2025

@JuliaRegistrator register

Activity

  1. JuliaRegistrator commented on May 18, 2025

    @JuliaRegistrator
    JuliaRegistrator
    on May 18, 2025

    Registration pull request created: JuliaRegistries/General/131246

    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.0 -m "<description of version>" a52814328fc064cfc074d7c8bf8812d81f4d0537
git push origin v0.1.0

  2. terasakisatoshi commented on May 18, 2025

    @terasakisatoshi
    terasakisatoshi
    on May 18, 2025
    MemberAuthor

    @JuliaRegistrator register

  3. JuliaRegistrator commented on May 18, 2025

    @JuliaRegistrator
    JuliaRegistrator
    on May 18, 2025

    Registration pull request updated: JuliaRegistries/General/131246

    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.0 -m "<description of version>" 57f9f99abb69a3dfc09013eb30cb1ac346a3f367
git push origin v0.1.0

  4. terasakisatoshi commented on May 19, 2025

    @terasakisatoshi
    terasakisatoshi
    on May 19, 2025
    MemberAuthor

    @JuliaRegistrator register

  5. JuliaRegistrator commented on May 19, 2025

    @JuliaRegistrator
    JuliaRegistrator
    on May 19, 2025

    Registration pull request updated: JuliaRegistries/General/131246

    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.0 -m "<description of version>" e273c47c806f91a072c9aedd47ecf48fc0424507
git push origin v0.1.0

  6. terasakisatoshi commented on May 20, 2025

    @terasakisatoshi
    terasakisatoshi
    on May 20, 2025
    MemberAuthor

    @JuliaRegistrator register

  7. JuliaRegistrator commented on May 20, 2025

    @JuliaRegistrator
    JuliaRegistrator
    on May 20, 2025

    Registration pull request updated: JuliaRegistries/General/131246

    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.0 -m "<description of version>" 84a4748e5c4a03c528d6b90edb024ec87dbc7221
git push origin v0.1.0

  8. terasakisatoshi commented on May 20, 2025

    @terasakisatoshi
    terasakisatoshi
    on May 20, 2025
    MemberAuthor

    @JuliaRegistrator register

  9. JuliaRegistrator commented on May 20, 2025

    @JuliaRegistrator
    JuliaRegistrator
    on May 20, 2025

    Registration pull request updated: JuliaRegistries/General/131246

    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.0 -m "<description of version>" 49c33172c4465c26320681af4c7786ea4feb1d73
git push origin v0.1.0

  10. terasakisatoshi commented on May 25, 2025

    @terasakisatoshi
    terasakisatoshi
    on May 25, 2025
    MemberAuthor

    Done

  11. terasakisatoshi
    closed this as completedon May 25, 2025

  12. terasakisatoshi commented on Jun 2, 2025

    @terasakisatoshi
    terasakisatoshi
    on Jun 2, 2025
    MemberAuthor

    @JuliaRegistrator register

  13. JuliaRegistrator commented on Jun 2, 2025

    @JuliaRegistrator
    JuliaRegistrator
    on Jun 2, 2025

    Registration pull request created: JuliaRegistries/General/132155

    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.1 -m "<description of version>" be3d5f42a26a5f4db95c12375fb07408c16771b9
git push origin v0.1.1

  14. terasakisatoshi commented on Oct 19, 2025

    @terasakisatoshi
    terasakisatoshi
    on Oct 19, 2025
    MemberAuthor

    @JuliaRegistrator register

  15. JuliaRegistrator commented on Oct 19, 2025

    @JuliaRegistrator
    JuliaRegistrator
    on Oct 19, 2025

    Registration pull request created: JuliaRegistries/General/140726

    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.2 -m "<description of version>" 82f574a47990ad93b2f82c9e06182124496d380e
git push origin v0.1.2

  16. terasakisatoshi commented on Jan 7, 2026

    @terasakisatoshi
    terasakisatoshi
    on Jan 7, 2026
    MemberAuthor

    @JuliaRegistrator register

  17. JuliaRegistrator commented on Jan 7, 2026

    @JuliaRegistrator
    JuliaRegistrator
    on Jan 7, 2026

    Registration pull request created: JuliaRegistries/General/145661

    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.3 -m "<description of version>" 39a5cbed70cc86c3aab9f8a723991411ea05603a
git push origin v0.1.3

  18. terasakisatoshi commented on Sep 24, 2026

    @terasakisatoshi
    terasakisatoshi
    on Sep 24, 2026
    MemberAuthor

    @JuliaRegistrator register

  19. JuliaRegistrator commented on Sep 24, 2026

    @JuliaRegistrator
    JuliaRegistrator
    on Sep 24, 2026

    Registration pull request created: JuliaRegistries/General/169297

    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.4 -m "<description of version>" da981b35346d8a26e5d62daa2aaa1815fc6c8f01
git push origin v0.1.4
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