Add workspace readme to Cargo.toml

[0HyperCube]

Some of the crates use readme.workspace = true but there is no readme set in the workspace manifest.

This PR corrects this by adding the readme to the workspace.

This may be the cause of the error in the graphite build. In any case it is probably good to clean it up.

[Firestar99]

That probably got introduced in #553 when I merged cargo-gpu into this workspace & repo. I'm surprised to see a failure like this, cause that PR has been merged months ago and noone ever noticed. Is your CI using nightly and maybe the newest nightly starts to fail here?

Also, I'm trying to get a new rust-gpu version out asap, give me another day or so.

[0HyperCube]

The CI was using the v0.10.0-alpha.1 but was moved recently to the nightly (which is when the failure was introduced).

[Firestar99]

The weird thing is, cargo +nightly b -p spirv-std on main works, even if it is spanning a bunch of new warnings. Maybe rustc devs noticed this would break a bunch of crates and reverted it already?

$ cargo +nightly --version
cargo 1.101.0-nightly (3d7cf6e93 2026-09-25)

EDIT: I don't mind just merging this, I just would like to know if it actually solves your issue.

[0HyperCube]

Also, I'm trying to get a new rust-gpu version out asap, give me another day or so.

Thanks; I think this would probably be beneficial to avoid using a git commit (the previous release didn't work with the latest glam version so we chose to temporarily use a git commit).

The weird thing is, cargo +nightly b -p spirv-std on main works, even if it is spanning a bunch of new warnings. Maybe rustc devs noticed this would break a bunch of crates and reverted it already?

Yes it is quite weird; the shader builds work fine in graphite outside of the nix runner. It doesn't appear to matter which version of nightly is pinned (I changed it to fix a later build error). I think perhaps it is some property of nix where it tries to parses all the crates?

I have tested locally and can confirm that this patch does fix the issue.

Thanks for your help reviewing.

[timon-schelling]

Can also confirm this works. And the Nix build fails because crane (nix build helper for rust) inlines workspace attributes and is more strict about resolution that than cargo. Will also file this with crane.

EDIT: with this included builds successful again see https://github.com/GraphiteEditor/Graphite/actions/runs/36468782474/job/109085455481

[Firestar99]

I changed it so it's no longer inheriting the readme property, but the two crates using it just define it themselves. Inheriting this properly is weird since it's a path that's always relative to the crate's Cargo.toml, not the workspace's Cargo.toml.

@0HyperCube I see there's another branch called t to debug something? If something's broken in graphite (due to glam updates?) just let me know here or on discord and I'll have a look :D

[0HyperCube]

I changed it so it's no longer inheriting the readme property, but the two crates using it just define it themselves. Inheriting this properly is weird since it's a path that's always relative to the crate's Cargo.toml, not the workspace's Cargo.toml.

That is indeed rather strange behaviour.

@0HyperCube I see there's another branch called t to debug something? If something's broken in graphite (due to glam updates?) just let me know here or on discord and I'll have a look :D

This is indeed just a test and can be ignored. The graphite build now works fine with this branch.

[nazar-pc]

This is the default value, just remove it. There is even a lint for this (probably in pendantic set).