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

Register #8

Open
terasakisatoshi opened this issue Dec 22, 2024 · 14 comments
Open

Register #8

terasakisatoshi opened this issue Dec 22, 2024 · 14 comments

Comments

@terasakisatoshi
Copy link
Member

No description provided.

@terasakisatoshi
Copy link
Member Author

@JuliaRegistrator register

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/121837

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

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

@terasakisatoshi
Copy link
Member Author

@JuliaRegistrator register

@JuliaRegistrator
Copy link

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

@terasakisatoshi
Copy link
Member Author

@JuliaRegistrator register

@JuliaRegistrator
Copy link

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

@terasakisatoshi
Copy link
Member Author

@JuliaRegistrator register

@JuliaRegistrator
Copy link

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

@terasakisatoshi
Copy link
Member Author

@JuliaRegistrator register

@JuliaRegistrator
Copy link

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

@terasakisatoshi
Copy link
Member Author

@JuliaRegistrator register

@JuliaRegistrator
Copy link

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

@terasakisatoshi
Copy link
Member Author

@JuliaRegistrator register

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/121840

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>" aa6e982d5ae494c8b5eee8ae1d5fb200a5f37697
git push origin v0.1.3

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

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