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 package #3

Open
waltergu opened this issue Apr 29, 2019 · 115 comments
Open

Register package #3

waltergu opened this issue Apr 29, 2019 · 115 comments

Comments

@waltergu
Copy link
Member

Register new package versions by @JuliaRegistrator register()

@JuliaRegistrator
Copy link

Registration pull request updated: JuliaRegistries/General/374

After the above pull request is merged, it is recommended that you create
a tag on this repository for the registered package version:

git tag -a v0.1.0 -m "<description of version>" 2bdd348f5f7f9f1c8f6f6df2f138c920275498cd
git push origin v0.1.0

@waltergu
Copy link
Member Author

@JuliaRegistrator register()

@JuliaRegistrator
Copy link

Registration pull request updated: JuliaRegistries/General/374

After the above pull request is merged, it is recommended that you create
a tag on this repository for the registered package version:

git tag -a v0.1.0 -m "<description of version>" 44de9929798d17c20959efddaf44edead1a7d988
git push origin v0.1.0

@waltergu
Copy link
Member Author

waltergu commented May 3, 2019

@JuliaRegistrator register()

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/518

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 Julia TagBot is installed, or can be done manually through the github interface, or via:

git tag -a v0.1.1 -m "<description of version>" 4d49d9e7f7f2fc6b15784bf92d0e8bc8dbadee78
git push origin v0.1.1

@waltergu
Copy link
Member Author

waltergu commented May 8, 2019

@JuliaRegistrator register()

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/612

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 Julia TagBot is installed, or can be done manually through the github interface, or via:

git tag -a v0.1.2 -m "<description of version>" 378cbbfd78939894e1a85a80f696b4243e9acb69
git push origin v0.1.2

@waltergu
Copy link
Member Author

waltergu commented May 8, 2019

@JuliaRegistrator register()

@JuliaRegistrator
Copy link

Registration pull request updated: JuliaRegistries/General/612

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 Julia TagBot is installed, or can be done manually through the github interface, or via:

git tag -a v0.1.2 -m "<description of version>" 988d2fc56deba5afd5d5bfffd18022b5824988b0
git push origin v0.1.2

@waltergu
Copy link
Member Author

@JuliaRegistrator register()

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/21850

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

@waltergu
Copy link
Member Author

@JuliaRegistrator register()

@JuliaRegistrator
Copy link

Registration pull request updated: JuliaRegistries/General/21850

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

@waltergu
Copy link
Member Author

@JuliaRegistrator register()

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/37441

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>" 6aefabd91b8dfada05b2c2917144efc88b85a030
git push origin v0.2.0

@waltergu
Copy link
Member Author

@JuliaRegistrator register()

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/43178

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>" 70c30ae25995b2d174cbe451245ab9b5df6af91d
git push origin v0.3.0

@waltergu
Copy link
Member Author

@JuliaRegistrator register()

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/43552

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.4.0 -m "<description of version>" 8d9cbc40d90edfc278f3c08e5d6b34a6dbde8666
git push origin v0.4.0

@waltergu
Copy link
Member Author

@JuliaRegistrator register()

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/44759

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.5.0 -m "<description of version>" 03f9a13dc5df2d54e0810d9a5da69bec60fd1632
git push origin v0.5.0

@waltergu
Copy link
Member Author

@JuliaRegistrator register()

@waltergu
Copy link
Member Author

@JuliaRegistrator register()

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/105166

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.9.14 -m "<description of version>" 8b1ab78cd16ac0223f77b01a5eb3bc00ba532a6b
git push origin v0.9.14

@waltergu
Copy link
Member Author

@JuliaRegistrator register()

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/107733

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

@waltergu
Copy link
Member Author

@JuliaRegistrator register()

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/117641

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.10.0 -m "<description of version>" 1267f318e76a8319681304e6941161484e395968
git push origin v0.10.0

@waltergu
Copy link
Member Author

@JuliaRegistrator register()

Release notes:

Breaking changes

Such changes do affect the public interfaces that users interact with.

Fermion/boson/spin/phonon indexes and operators

  • Construction of fermion/boson/spin/phonon indexes and operators are changed. 𝕗 (\bbf<tab> ferimion), 𝕓 (\bbb<tab>, boson), 𝕊 (\bbS<tab>, spin), 𝕦 (\bbu<tab>, displacement of lattice vibration) and 𝕡 (\bbp<tab>, momentum of lattice vibration) are the new interfaces to construct and display such indexes and operators.

  • Underlying types to implement fermion/boson/spin/phonon indexes and operators are renamed: 1) the abstract type IID => InternalIndex, and the concrete types FID => FockIndex, SID => SpinIndex, PID => PhononIndex; 2) CompositeIndex => CoordinatedIndex.

  • The :iid attribute of Index now is renamed to :internal.

Coupling

  • A new type, Pattern, is introduced to represent the coupling pattern in a Coupling.
  • Construction of Coupling with constraints now uses a new macro, @pattern. The old @indexes macro is removed.
  • Coupling with different types of Indexes now must be initialized with the @pattern macro.
  • The :site attribute of an Index used to construct a Coupling can no longer be an integer; it must now be either a : or an Ordinal to clearly indicate that it represents the ordinal in a bond.

Quantum numbers

Quantum numbers are completely redesigned.

Mechanism changes

Such changes typically do not affect the public interfaces that users interact with, but they are significant for developers looking to extend this package.

  • New function Patternrule is introduced to implement default rules for coupling patterns.
  • Interface of script, which is used to support latex-formatted output of operators, is changed.
  • Interface of expand for a Coupling is changed.
  • Interfaces of Toolkit.VectorSpace are changed.

@JuliaRegistrator
Copy link

Registration pull request updated: JuliaRegistries/General/117641

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

@waltergu
Copy link
Member Author

@JuliaRegistrator register()

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/120364

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

@waltergu
Copy link
Member Author

waltergu commented Dec 3, 2024

@JuliaRegistrator register()

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/120592

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

@waltergu
Copy link
Member Author

waltergu commented Dec 3, 2024

@JuliaRegistrator register()

@JuliaRegistrator
Copy link

Registration pull request updated: JuliaRegistries/General/120592

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

@waltergu
Copy link
Member Author

waltergu commented Dec 3, 2024

@JuliaRegistrator register()

@JuliaRegistrator
Copy link

Registration pull request updated: JuliaRegistries/General/120592

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.10.2 -m "<description of version>" 09fb4bb8eef972f4633848fa910f7c6fb7104323
git push origin v0.10.2

@waltergu
Copy link
Member Author

waltergu commented Dec 3, 2024

@JuliaRegistrator register()

@JuliaRegistrator
Copy link

Error while trying to register: Version 0.10.2 already exists

@waltergu
Copy link
Member Author

waltergu commented Dec 5, 2024

@JuliaRegistrator register()

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/120700

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.10.3 -m "<description of version>" 8f4d5aebbac9408ed6464fcaadfaf12ae54a02f9
git push origin v0.10.3

@waltergu
Copy link
Member Author

waltergu commented Dec 7, 2024

@JuliaRegistrator register()

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/120880

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.10.4 -m "<description of version>" 28da326d4088d86d178a54b7446b454a4ac349dd
git push origin v0.10.4

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