Skip to content

Commit

Permalink
for tagging a new release
Browse files Browse the repository at this point in the history
  • Loading branch information
rveltz committed Dec 7, 2024
1 parent a2c3989 commit c748778
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 = "BifurcationKit"
uuid = "0f109fa4-8a5d-4b75-95aa-f515264e7665"
authors = ["Romain Veltz <[email protected]>"]
version = "0.4.4"
version = "0.4.5"

[deps]
Accessors = "7d9f7c33-5ae7-4f3b-8dc6-eff91059b697"
Expand Down

2 comments on commit c748778

@rveltz
Copy link
Member Author

@rveltz rveltz commented on c748778 Dec 7, 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/120899

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.5 -m "<description of version>" c74877876b39f55270890ec32217efeb7392fb3c
git push origin v0.4.5

Please sign in to comment.