Skip to content

Commit

Permalink
update compat
Browse files Browse the repository at this point in the history
  • Loading branch information
arhik committed Nov 19, 2023
1 parent b06c2b0 commit e28fc20
Showing 1 changed file with 2 additions and 0 deletions.
2 changes: 2 additions & 0 deletions Project.toml
Original file line number Diff line number Diff line change
Expand Up @@ -34,6 +34,7 @@ ColorTypes = "^0.11"
CoordinateTransformations = "^0.6"
DataStructures = "^0.18"
Debugger = "^0.7"
FreeTypeAbstraction = "^0.10"
GLFW = "^3.4"
GLFW_jll = "^3.3"
GeometryBasics = "^0.4"
Expand All @@ -44,6 +45,7 @@ Quaternions = "^0.7"
Reexport = "^1.2"
Rotations = "^1.3"
StaticArrays = "^1.5"
WGPUCanvas = "^0.1.1"
WGPUCore = "^0.1"
WGPUNative = "^0.1"
WGSLTypes = "^0.1"
Expand Down

2 comments on commit e28fc20

@arhik
Copy link
Member Author

@arhik arhik commented on e28fc20 Nov 19, 2023

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 updated: JuliaRegistries/General/95600

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.1 -m "<description of version>" e28fc2070ce06fba5a485567ed3da407156d86ac
git push origin v0.1.1

Please sign in to comment.