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

Release #1

Open
szabo137 opened this issue Jul 6, 2022 · 23 comments
Open

Release #1

szabo137 opened this issue Jul 6, 2022 · 23 comments

Comments

@szabo137
Copy link
Member

szabo137 commented Jul 6, 2022

@JuliaRegistrator register()

@JuliaRegistrator
Copy link

Error while trying to register: Register Failed
@szabo137, it looks like you are not a publicly listed member/owner in the parent organization (QEDjl-project).
If you are a member/owner, you will need to change your membership to public. See GitHub Help

@szabo137
Copy link
Member Author

szabo137 commented Jul 6, 2022

@JuliaRegistrator register()

@JuliaRegistrator
Copy link

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

@szabo137
Copy link
Member Author

szabo137 commented Jul 6, 2022

@JuliaRegistrator register()

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/63773

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>" a5eaf5548788121c13a4139a013e640f75f4249c
git push origin v0.1.4

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

@szabo137
Copy link
Member Author

szabo137 commented Jul 6, 2022

@JuliaRegistrator register()

@JuliaRegistrator
Copy link

Registration pull request updated: JuliaRegistries/General/63773

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>" 5d54871ce5a4120e405fae00374066b1d176a019
git push origin v0.1.4

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

@szabo137 szabo137 changed the title Register Release Oct 18, 2023
@szabo137
Copy link
Member Author

@JuliaRegistrator register branch=main

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/93859

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.5 -m "<description of version>" 0bf6beb0819a50721de9c68d13ae5b8825f2466e
git push origin v0.1.5

@szabo137
Copy link
Member Author

@JuliaRegistrator register()

@JuliaRegistrator
Copy link

Error while trying to register: Version 0.1.5 already exists

@szabo137
Copy link
Member Author

@JuliaRegistrator register(branch="main")

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/99822

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.6 -m "<description of version>" f2241ee45ace8e15d3b25841c2f83d12411e3699
git push origin v0.1.6

@szabo137
Copy link
Member Author

@JuliaRegistrator register(branch="main")

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/109685

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

@szabo137
Copy link
Member Author

@JuliaRegistrator register(branch="main")

@JuliaRegistrator
Copy link

Registration pull request updated: JuliaRegistries/General/109685

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.2.0 -m "<description of version>" a4fcee5c75856db6e0e7f2567a02896c77356404
git push origin v0.2.0

@szabo137
Copy link
Member Author

@JuliaRegistrator register(branch="main")

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/109754

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.2.1 -m "<description of version>" 16472ce93235927f513865b1e044b91fa2218b32
git push origin v0.2.1

@AntonReinhard
Copy link
Member

@JuliaRegistrator register(branch="main")

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/110942

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.2.2 -m "<description of version>" 3af6d7e4a16ee32352b26e7c7b4dbc474edea66e
git push origin v0.2.2

@AntonReinhard
Copy link
Member

@JuliaRegistrator register(branch="main")

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/117956

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

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

3 participants