Skip to content

Commit

Permalink
Bump version to v0.3.3
Browse files Browse the repository at this point in the history
  • Loading branch information
liuyxpp committed Dec 25, 2023
1 parent 6a0a2d9 commit 354e089
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 2 deletions.
3 changes: 2 additions & 1 deletion .gitignore
Original file line number Diff line number Diff line change
@@ -1,3 +1,4 @@
.DS_Store
Manifest.toml
docs/build
docs/build
docs/misc
2 changes: 1 addition & 1 deletion Project.toml
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
name = "MakiePublication"
uuid = "dde8697e-0d61-460d-88dd-856f66710dd1"
authors = ["Yi-Xin Liu <[email protected]>"]
version = "0.3.2"
version = "0.3.3"

[deps]
ColorSchemes = "35d6a980-a343-548e-a6ea-1d62b119f2f4"
Expand Down

2 comments on commit 354e089

@liuyxpp
Copy link
Owner Author

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

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.3 -m "<description of version>" 354e089ed6438d363b0c5a9d758a916e3488c374
git push origin v0.3.3

Please sign in to comment.