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 with General #3

Open
cortner opened this issue Jan 16, 2024 · 12 comments
Open

Register with General #3

cortner opened this issue Jan 16, 2024 · 12 comments

Comments

@cortner
Copy link
Member

cortner commented Jan 16, 2024

I assume people are happy to start with 0.0.1, I don't think this is a 0.1.0 yet.

@mfherbst
Copy link
Member

I don't mind. Would be good to have it registered, though 👍.

@rkurchin
Copy link

Fine by me as well!

@cortner
Copy link
Member Author

cortner commented Jan 16, 2024

@JuliaRegistrator register

@JuliaRegistrator
Copy link

Error while trying to register: Error in (Julia)Project.toml: Package 'EmpiricalPotentials' with UUID: 38527215-9240-4c91-a638-d4250620c9e2 not found in registry or stdlib

@cortner
Copy link
Member Author

cortner commented Jan 16, 2024

ok, seems we need to register EmpiricalPotentials first ...

@cortner
Copy link
Member Author

cortner commented Jan 16, 2024

@cortner
Copy link
Member Author

cortner commented Jan 21, 2024

@JuliaRegistrator register

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/99240

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

@mfherbst
Copy link
Member

mfherbst commented Aug 9, 2024

@JuliaRegistrator register

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/112714

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

@mfherbst
Copy link
Member

@JuliaRegistrator register

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/112861

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

4 participants