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 #1

Open
mongibellili opened this issue Jul 9, 2024 · 17 comments
Open

Register #1

mongibellili opened this issue Jul 9, 2024 · 17 comments

Comments

@mongibellili
Copy link
Owner

@JuliaRegistrator register()

@JuliaRegistrator
Copy link

Error while trying to register: "Pre-release version not allowed"

@mongibellili
Copy link
Owner Author

@JuliaRegistrator register()

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/110827

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>" db4a5315cf12f65864a5a0ed6412adcbe77aea44
git push origin v1.0.0

@mongibellili
Copy link
Owner Author

@JuliaRegistrator register()

Release notes:

Initial release

  • The solver supports these algorithms (qss1,2;liqss1,2;nmliqss1,2)

@JuliaRegistrator
Copy link

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

@mongibellili
Copy link
Owner Author

@JuliaRegistrator register()

@JuliaRegistrator
Copy link

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

@mongibellili
Copy link
Owner Author

@JuliaRegistrator register()

@JuliaRegistrator
Copy link

Error while trying to register: "Project file should contain name, uuid and version"

@mongibellili
Copy link
Owner Author

@JuliaRegistrator register()

@JuliaRegistrator
Copy link

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

@mongibellili
Copy link
Owner Author

@JuliaRegistrator register branch=main

@JuliaRegistrator
Copy link

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

@mongibellili
Copy link
Owner Author

@JuliaRegistrator register()

Release notes:

Initial release
The solver supports these algorithms (qss1,2;liqss1,2;nmliqss1,2)

@JuliaRegistrator
Copy link

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

@mongibellili
Copy link
Owner Author

@JuliaRegistrator register()

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/110834

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

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