Skip to content

Commit

Permalink
Merge pull request #132 from spine-tools/clizbe-patch-1
Browse files Browse the repository at this point in the history
Release 0.15.0
  • Loading branch information
clizbe authored Oct 9, 2024
2 parents 49e2fc2 + fe63dc5 commit 06dd177
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion Project.toml
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
name = "SpineInterface"
uuid = "0cda1612-498a-11e9-3c92-77fa82595a4f"
authors = ["Spine Project consortium <[email protected]>"]
version = "0.14.8"
version = "0.15.0"

[deps]
DataStructures = "864edb3b-99cc-5e75-8d2d-829cb0a9cfe8"
Expand Down

2 comments on commit 06dd177

@clizbe
Copy link
Member Author

@clizbe clizbe commented on 06dd177 Oct 9, 2024

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/116905

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.15.0 -m "<description of version>" 06dd177e9ce1eb9ad7a24091bcb726410225c32c
git push origin v0.15.0

Also, note the warning: This looks like a new registration that registers version 0.15.0.
Ideally, you should register an initial release with 0.0.1, 0.1.0 or 1.0.0 version numbers
This can be safely ignored. However, if you want to fix this you can do so. Call register() again after making the fix. This will update the Pull request.

Please sign in to comment.