Skip to content

Commit

Permalink
bump version
Browse files Browse the repository at this point in the history
  • Loading branch information
@bgctw
bgctw committed Jan 16, 2024
1 parent 638e6c3 commit aa6b2c3
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion Project.toml
View file
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
name = "DistributionFits"
uuid = "45214091-1ed4-4409-9bcf-fdb48a05e921"
authors = ["Thomas Wutzler <[email protected]> and contributors"]
version = "0.3.7-DEV"
version = "0.3.7"

[deps]
Distributions = "31c24e10-a181-5473-b8eb-7969acd0382f"
Expand Down

2 comments on commit aa6b2c3

@bgctw
Copy link
Owner Author

@bgctw bgctw commented on aa6b2c3 Jan 16, 2024

Choose a reason for hiding this comment

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

@JuliaRegistrator register

  • implement fit_mean_Σ for Normal, MvNormal, LogNormal, MvLogNormal

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

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.7 -m "<description of version>" aa6b2c365b0abc6459e597a6cc6aab5708b61fac
git push origin v0.3.7

Please sign in to comment.