Skip to content

Commit

Permalink
Add missing compat entries
Browse files Browse the repository at this point in the history
  • Loading branch information
@bgroenks96
bgroenks96 committed Apr 16, 2024
1 parent 668cb10 commit 7da58d9
Showing 1 changed file with 3 additions and 0 deletions.
3 changes: 3 additions & 0 deletions Project.toml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -67,6 +67,7 @@ DimensionalData = "0.26"
Distributions = "0.25"
DynamicHMC = "3"
EnsembleKalmanProcesses = "1"
FileIO = "1"
ForwardDiff = "0.10"
JLD2 = "0.4"
KernelFunctions = "0.10"
Expand All @@ -85,7 +86,9 @@ SciMLBase = "1,2"
Statistics = "1"
StatsBase = "0.34"
StatsFuns = "1"
Tables = "1"
UnPack = "1"
Zygote = "0.6"
julia = "1.6,1.7,1.8,1.9,1.10"

[extras]
Expand Down

2 comments on commit 7da58d9

@bgroenks96
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 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 updated: JuliaRegistries/General/105005

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

Please sign in to comment.