package registration #6

Activity

1. JuliaRegistrator commented on Sep 26, 2025

   

   JuliaRegistrator

   on Sep 26, 2025

   More actions

   Registration pull request created: JuliaRegistries/General/139213

   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 v1.0.1 -m "<description of version>" f35a57760da5d7c6c18abcf4ee0c0207a0738ab2
   git push origin v1.0.1
   
2. subhk commented on Oct 2, 2025

   

   subhk

   on Oct 2, 2025

   OwnerAuthor

   More actions

   @JuliaRegistrator register
3. JuliaRegistrator commented on Oct 2, 2025

   

   JuliaRegistrator

   on Oct 2, 2025

   More actions

   Registration pull request created: JuliaRegistries/General/139592

   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 v1.0.2 -m "<description of version>" f63f114a23b2732832de2b472666f720cae78f6a
   git push origin v1.0.2
   
4. subhk commented on Jan 19, 2026

   

   subhk

   on Jan 19, 2026

   OwnerAuthor

   More actions

   @JuliaRegistrator register
5. JuliaRegistrator commented on Jan 19, 2026

   

   JuliaRegistrator

   on Jan 19, 2026

   More actions

   Registration pull request created: JuliaRegistries/General/146539

   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 v1.0.3 -m "<description of version>" 0092447a9bf59bc38e58139b84550a53854577bb
   git push origin v1.0.3
   
6. subhk

   closed this as completedon May 8, 2026