chore: release v19.0.0

[galargh]

No description provided.

[Copilot]

Pull Request Overview

This PR prepares the release of version 19.0.0 of the filecoin-proofs-api crate. The release includes bug fixes related to cache clearing functionality and layer data handling.

Key changes:

• Version bump from 18.1.0 to 19.0.0 across package and dependencies
• Updated changelog with release notes documenting the included fixes
• Updated version references for proper semantic versioning links

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
Cargo.toml	Updates package version to 19.0.0 and bumps dependency versions
CHANGELOG.md	Adds 19.0.0 release entry with fix descriptions and updates version links

[vmx]

Generally it looks OK, it depends on your workflow. I personally don't bump versions manually, but let cargo release figure it out. Though both ways work (e.g. the rust-libp2p team does manual version bumping).

[rvagg]

Also @galargh FYI we may be able to push forward soon with the auto-release process we were working on previously, see filecoin-project/ref-fvm#2185

[galargh]

Generally it looks OK, it depends on your workflow. I personally don't bump versions manually, but let cargo release figure it out. Though both ways work (e.g. the rust-libp2p team does manual version bumping).

That's really useful info! Thanks 🙏

I also realised that I won't be able to complete the release because:

1. I cannot build/package the crate on my machine as there are no NVIDIA drivers for macOS machines.
2. I'm not a member of proofs-crates-owners team. This one would be easier to fix.

So, as an alternative to this PR, I put together a workflow that runs cargo release in CI to create and publish a release - #110 To work, it would require CARGO_REGISTRY_TOKEN for one of the eligible users to be set up in the repository secrets.

To complete the release we can either do that or we have to find someone who'd be able to complete the process on their own machine. @BigLep WDYT?