Skip to content

Commit

Permalink
Merge pull request #28 from gpeairs/patch-1
Browse files Browse the repository at this point in the history
Use newer JLL
  • Loading branch information
ahojukka5 authored Nov 1, 2023
2 parents c27b275 + 24c53d9 commit f8d606b
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions Project.toml
Original file line number Diff line number Diff line change
@@ -1,13 +1,13 @@
name = "Gmsh"
uuid = "705231aa-382f-11e9-3f0c-b7cb4346fdeb"
authors = ["Jukka Aho <ahojukka5@gmail.com>"]
version = "0.2.2"
version = "0.3.0"

[deps]
gmsh_jll = "630162c2-fc9b-58b3-9910-8442a8a132e6"

[compat]
gmsh_jll = "=4.10.2"
gmsh_jll = "=4.11.1"
julia = "1"

[extras]
Expand Down

2 comments on commit f8d606b

@fredrikekre
Copy link
Collaborator

Choose a reason for hiding this comment

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

@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/95253

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

Please sign in to comment.