Skip to content

Commit

Permalink
Update Project.toml (#140)
Browse files Browse the repository at this point in the history
  • Loading branch information
kose-y authored Jan 12, 2025
1 parent 16eaf43 commit 255fa6a
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion Project.toml
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@ name = "SnpArrays"
uuid = "4e780e97-f5bf-4111-9dc4-b70aaf691b06"
keywords = ["GWAS", "Genome-wide association studies", "binary plink"]
authors = ["Hua Zhou <[email protected]>", "Seyoon Ko <[email protected]>", "Douglas Bates <[email protected]>", "OpenMendel Team"]
version = "0.3.23"
version = "0.3.22"

[deps]
Adapt = "79e6a3ab-5dfb-504d-930d-738a2a938a0e"
Expand Down

2 comments on commit 255fa6a

@kose-y
Copy link
Member Author

@kose-y kose-y commented on 255fa6a Jan 12, 2025

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

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.22 -m "<description of version>" 255fa6a6ca221ceb68a31c4cd760c288f2186757
git push origin v0.3.22

Please sign in to comment.