Skip to content

Commit

Permalink
3.6.1 [skip ci]
Browse files Browse the repository at this point in the history
  • Loading branch information
@t-bltg
t-bltg committed Dec 22, 2023
1 parent b380865 commit 98bb30c
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion Project.toml
View file
Expand Up @@ -3,7 +3,7 @@ uuid = "b8865327-cd53-5732-bb35-84acbb429228"
license = "MIT"
desc = "Unicode-based scientific plotting for working in the terminal"
authors = ["Christof Stocker <stocker.christof@gmail.com>", "T Bltg <tf.bltg@gmail.com>"]
version = "3.6.0"
version = "3.6.1"

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

2 comments on commit 98bb30c

@t-bltg
Copy link
Member Author

@t-bltg t-bltg commented on 98bb30c Dec 22, 2023

Choose a reason for hiding this comment

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

@JuliaRegistrator register

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

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 v3.6.1 -m "<description of version>" 98bb30c5509856df21558f262c9e990b60f0744a
git push origin v3.6.1

Please sign in to comment.