Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

registration #1

Open
akjake616 opened this issue Jun 12, 2024 · 22 comments
Open

registration #1

akjake616 opened this issue Jun 12, 2024 · 22 comments

Comments

@akjake616
Copy link
Owner

@JuliaRegistrator register()

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/108780

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

@akjake616
Copy link
Owner Author

@JuliaRegistrator register

Release notes:

  • update usage for PlotlyGeometries v2
  • update to use concrete types in struct

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/110057

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>" 948a44d48782af843d8331fc25b72c3e217571ba
git push origin v1.0.1

@akjake616
Copy link
Owner Author

@JuliaRegistrator register

Release notes:

  • update usage for PlotlyGeometries v2
  • update to use concrete types in struct

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/110058

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.1.0 -m "<description of version>" 99ce328f774e79369cbd83c35e160986893b23ab
git push origin v1.1.0

@akjake616
Copy link
Owner Author

@JuliaRegistrator register

Release notes:

add save and load voxels
change certain terms

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/110569

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.1 -m "<description of version>" 297c66b4e97d71df5cf3f5ae683fd438bedc7ad3
git push origin v2.0.1

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

@JuliaRegistrator
Copy link

Registration pull request updated: JuliaRegistries/General/110569

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

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

@akjake616
Copy link
Owner Author

@JuliaRegistrator register

Release notes:

add save and load voxels
change certain terms

@JuliaRegistrator
Copy link

Registration pull request updated: JuliaRegistries/General/110559

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>" e9173137cbf96d57ef11efd7946ba930ae77cdb6
git push origin v2.0.0

1 similar comment
@JuliaRegistrator
Copy link

Registration pull request updated: JuliaRegistries/General/110559

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>" e9173137cbf96d57ef11efd7946ba930ae77cdb6
git push origin v2.0.0

Repository owner deleted a comment from JuliaRegistrator Jul 6, 2024
@JuliaRegistrator
Copy link

Registration pull request updated: JuliaRegistries/General/110559

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>" e9173137cbf96d57ef11efd7946ba930ae77cdb6
git push origin v2.0.0

@akjake616
Copy link
Owner Author

@JuliaRegistrator register

Release notes:

  • add assign_voxel method

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/110605

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

@akjake616
Copy link
Owner Author

@JuliaRegistrator register

Release notes:

  • update using keyword render

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/110717

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>" 999d06ea4d17798483b4c2707876ba68de60b78f
git push origin v2.2.0

@akjake616
Copy link
Owner Author

@JuliaRegistrator register()

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/110753

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.2.1 -m "<description of version>" 9fd5863d2daa2958ca37d989399c14b7153a75fe
git push origin v2.2.1

@akjake616
Copy link
Owner Author

@JuliaRegistrator register()

@JuliaRegistrator
Copy link

Registration pull request updated: JuliaRegistries/General/110753

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

@akjake616
Copy link
Owner Author

@JuliaRegistrator register()

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/110819

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants