Skip to content

Commit

Permalink
set version to v0.4.11
Browse files Browse the repository at this point in the history
  • Loading branch information
@JoshuaLampert
JoshuaLampert committed Nov 28, 2023
1 parent 62a86e0 commit ddeff93
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion Project.toml
View file
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
name = "P4est"
uuid = "7d669430-f675-4ae7-b43e-fab78ec5a902"
authors = ["Michael Schlottke-Lakemper <michael@sloede.com>", "Hendrik Ranocha <mail@ranocha.de>", "Joshua Lampert <joshua.lampert@uni-hamburg.de>"]
version = "0.4.11-pre"
version = "0.4.11"

[deps]
CEnum = "fa961155-64e5-5f13-b03f-caf6b980ea82"
Expand Down

2 comments on commit ddeff93

@JoshuaLampert
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@JuliaRegistrator register

@JuliaRegistrator
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Registration pull request created: JuliaRegistries/General/96075

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

Please sign in to comment.