Register in General

[cortner]

@JuliaRegistrator register branch=dev-v0.0.1

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/107194

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>" 671416272b319315c47f5983fdd4381b0a1435ba
git push origin v0.0.1

[cortner]

@JuliaRegistrator register branch=dev-v0.0.2

[cortner]

@JuliaRegistrator register branch=dev-v0.0.2

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/107466

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>" 046c4bb9bd48a1211283858e592ed9ec665810c1
git push origin v0.0.2

[cortner]

@JuliaRegistrator register

Release notes:

• State and DState are not PState and VState
• nicer output
• prototype AtomsBase compatibility

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/107468

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.3 -m "<description of version>" 700f399a62208edb8f8fb98619e5ebb53ad3e902
git push origin v0.0.3

[cortner]

@JuliaRegistrator register

Release notes:

• State and DStateare nowPStateandVState`
• nicer output
• prototype AtomsBase compatibility

[JuliaRegistrator]

Registration pull request updated: JuliaRegistries/General/107468

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

[cortner]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/107708

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

[cortner]

@JuliaRegistrator register

Release notes:

• introduce setproperty, which makes a single change to a particle and then returns a new instance
• extended list of standardized properties with standardized symbols and names
• automatic generation of interface using meta-programming which makes it easy to extend the list of standardized properties

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/107771

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.5 -m "<description of version>" ed347b92423972cd2a777a43e3cc0c8d73c075f7
git push origin v0.0.5

[cortner]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/111544

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.6 -m "<description of version>" 683c0e3dfd51d4e20f7dc390fdd66bb58d23c590
git push origin v0.0.6

[cortner]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/114403

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