Skip to content

Commit

Permalink
Release 0.6.1
Browse files Browse the repository at this point in the history
  • Loading branch information
goerz committed Apr 22, 2024
1 parent f46a3b8 commit 125479b
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions Project.toml
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
name = "Krotov"
uuid = "b05dcdc7-62f6-4360-bf2c-0898bba419de"
authors = ["Michael Goerz <[email protected]>"]
version = "0.6.0+dev"
version = "0.6.1"

[deps]
Dates = "ade2ca70-3891-5945-98fb-dc099432e06a"
Expand All @@ -16,6 +16,6 @@ Dates = "1"
LinearAlgebra = "1"
Printf = "1"
ConcreteStructs = "0.2"
QuantumControlBase = ">=0.9.1"
QuantumControlBase = "0.9.3"
SparseArrays = "1"
julia = "1.9"

2 comments on commit 125479b

@goerz
Copy link
Member Author

@goerz goerz commented on 125479b Apr 22, 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/105344

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.6.1 -m "<description of version>" 125479bb03f2c83de167d6c3b3311352592fa825
git push origin v0.6.1

Please sign in to comment.