QEDjl-project / QuantumElectrodynamics.jl

[WIP] QuantumElectrodynamics.jl: A strong-field particle physics framework
https://qedjl-project.github.io/QuantumElectrodynamics.jl/
MIT License
8 stars 3 forks source link

Release #50

Open AntonReinhard opened 1 month ago

AntonReinhard commented 1 month ago

@JuliaRegistrator register(branch="main")

JuliaRegistrator commented 1 month ago

Registration pull request created: JuliaRegistries/General/114341

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>" 268cf009f76ecd2e45dd319a08a9bc21d4033c58
git push origin v0.1.0
AntonReinhard commented 1 month ago

@JuliaRegistrator register(branch="main")

JuliaRegistrator commented 1 month ago

Registration pull request updated: JuliaRegistries/General/114341

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>" 1f8179d03f5f4f778cab605759f88956bd6e07dc
git push origin v0.1.0
AntonReinhard commented 1 month ago

@JuliaRegistrator register(branch="main")

JuliaRegistrator commented 1 month ago

Registration pull request updated: JuliaRegistries/General/114341

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>" 1f2078f8c05903b7a34024460a7de4a843b53826
git push origin v0.1.0
AntonReinhard commented 1 month ago

@JuliaRegistrator register(branch="main")

JuliaRegistrator commented 1 month ago

Registration pull request updated: JuliaRegistries/General/114341

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>" c43e326e7c2fbe4829b22560dc06320500cdeb3a
git push origin v0.1.0
AntonReinhard commented 3 weeks ago

@JuliaRegistrator register(branch="main")

JuliaRegistrator commented 3 weeks ago

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

AntonReinhard commented 3 weeks ago

@JuliaRegistrator register(branch="main")

JuliaRegistrator commented 3 weeks ago

Registration pull request created: JuliaRegistries/General/115082

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>" d3808746ae2899ba56dc54fde993407254061b06
git push origin v0.1.0