-
Notifications
You must be signed in to change notification settings - Fork 158
Prepare vello_cpu
0.0.1 release
#991
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
As a definitely uncontroversial baseline, I'd like for one of the crate owners of Vello to merge and publish this (or Laurenz). I think that any warning message should also be in the READMEs (now is probably a good time to setup |
44b5dc7
to
a6eaa4c
Compare
Signed-off-by: Nico Burns <nico@nicoburns.com>
Co-authored-by: Tom Churchman <thomas@kepow.org>
@@ -1,15 +1,14 @@ | |||
[package] | |||
name = "vello_common" | |||
version.workspace = true | |||
# When updating, also update the version in the workspace dependency in the root Cargo.toml | |||
version = "0.0.1" | |||
description = "Core data structures and utilities shared across the Vello rendering, including geometry processing and tiling logic." |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not changed here, but should this say "across the Vello renderer"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably. I don't care enough to change it - CI is already running, and it's getting late!
0.0.1
forvello_cpu
,vello_common
andvello_api
cratesvello_cpu
crate