chore: release v0.10.0 (#106)

Release v0.9.0 (#97)

I don't have permission to actually publish to crates.io, so somebody
else will need to do that.

Signed-off-by: Nico Burns <nico@nicoburns.com>

chore: release version (#90)

Wait for #89  to merge

chore: release v0.8 (#86)

chore: release 0.7.0 (#77)

Release 0.7.0

chore: release 0.6 (#67)

Publish version 0.6

chore: bump version (#52)

I will push a release after this.

chore: release 0.4.0 (#45)

Release 0.4.0

Enable non-linear easing (#42)

It seems to me that most of the work to get non-linear easing is already
done.

In order to check what is left to be done I removed the linear-only
enforcement, created a simple example with 3 key frames and compared the
results with lottielab.com editor:

![easing_compare_before](https://github.com/user-attachments/assets/0e7a5df6-f10f-4c45-a31f-f15c75cc8ff2)

I have found that:
- only the easing curves from first two key frames seem to affect the
animation as rendered in lottielab.
- [Lottie
spec](https://lottie.github.io/lottie-spec/latest/specs/properties/)
mentions that: "_All keyframes MUST have an i and o value, unless It is
the last keyframe in the sequence OR ..._"
- This comment mentions that the last one is unused:
airbnb/lottie-web#2620 (comment)

The way I understand it is that while we are moving into position
described by next key frame, we still should be using `o` and `i`
parameters from the previous one.

After changing the `Time::frames_and_weight` to use the easing from
current key frame, positions seem to match pretty well:


![easing_compare_after](https://github.com/user-attachments/assets/d2a563d8-66b4-40d5-a49e-f67fd7dee529)

What do you think? Is there anything else missing to enable non-linear
easing?

Thanks for creating an amazing library!

---------

Co-authored-by: Spencer C. Imbleau <spencer@imbleau.com>

v0.3 (#24)

## 0.3.0

### Added

- Added `velato::Renderer::render`, which now returns a new vello scene.

### Changed

- Updated to vello 0.2
- Renamed `VelatoError` to `velato::Error`
- Renamed the existing `velato::Renderer::render` to
`velato::Renderer::append`

### Removed

- All code and related profiling (`wgpu_profiler`) used in examples.