Skip to content

Commit

Permalink
bump patch GeoInterfaceRecipes.jl patch version to 1.0.2
Browse files Browse the repository at this point in the history
  • Loading branch information
@rafaqz
rafaqz authored Dec 27, 2023
1 parent 1cf6004 commit 7071bb4
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion GeoInterfaceRecipes/Project.toml
View file
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
name = "GeoInterfaceRecipes"
uuid = "0329782f-3d07-4b52-b9f6-d3137cf03c7a"
authors = ["JuliaGeo and contributors"]
version = "1.0.1"
version = "1.0.2"

[deps]
GeoInterface = "cf35fbd7-0cd7-5166-be24-54bfbe79505f"
Expand Down

2 comments on commit 7071bb4

@rafaqz
Copy link
Member Author

@rafaqz rafaqz commented on 7071bb4 Dec 27, 2023

Choose a reason for hiding this comment

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

@JuliaRegistrator register subdir=GeoInterfaceRecipes

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

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 GeoInterfaceRecipes-v1.0.2 -m "<description of version>" 7071bb4873fb47f68d6cda37897991c815fa0068
git push origin GeoInterfaceRecipes-v1.0.2

Please sign in to comment.